CSSLP: Certified Secure Software Lifecycle Professional

Instructions:

• Answer 50 questions in 15 minutes.
• If you are not ready to take this test, you can study here.
• Match each statement with the correct term.
• Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Session Management
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking


2. Counter measures
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security controls applied after a threat has been materialized
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main


3. Authentication
Authentication
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied


4. ISO/IEC 9216
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model


5. FIPS140-2 (Security requirement for cryptographic modules)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Confidentiality - Integrity - Availability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible


6. Confidentiality
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Protection against unauthorized information disclosure. It helps maintaining privacy
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS


7. Annual Rate of Occurence (ARO)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Number of incidents that can be expected in a year
Protection against unauthorized information disclosure. It helps maintaining privacy


8. ISO/IEC 27003
Predetermined number of user error allowed before recording it as a security violation
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Still under development - aimsto address ISMS implementation guidance


9. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security controls applied to mitigate a threat before it materializes
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Design to mitigate any single source of complete compromise


10. Management Controls
Protection against unauthorized information disclosure. It helps maintaining privacy
Confidentiality - Integrity - Availability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking


11. Multifactor authentication
Development guide - Code Review Guide - Testing Guide
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc


12. Accountability
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual


13. EALs levels
Secure applicatios running on secure hosts (systems) in a secure network
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Security controls applied to mitigate a threat before it materializes
Technical - Management - Operational


14. Configurations Parameters Management
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Protection against unauthorized information disclosure. It helps maintaining privacy
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network


15. ISO/IEC 27006:2007
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Support for accreditation and certification bodies that audit and certify ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Still under development - aimsto address ISMS implementation guidance


16. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software


17. Auditing
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested


18. Availability
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Access request by a subject to an object is mediated each time and every time.
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.


19. After identification step is...
Authentication
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Number of incidents that can be expected in a year
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system


20. Holistic Security in software
Support for accreditation and certification bodies that audit and certify ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Secure applicatios running on secure hosts (systems) in a secure network


21. Threat
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Secure applicatios running on secure hosts (systems) in a secure network
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.


22. Integrity
Technical - Management - Operational
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
estimate potential loss of a single incident: SLE = Asset value * EF(%)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer


23. Popular guides developed by OWASP
Still under development - aimsto address ISMS implementation guidance
Development guide - Code Review Guide - Testing Guide
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
OWASP - ITIL


24. Exposure factor (EF)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management


25. Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Development guide - Code Review Guide - Testing Guide
Support policies at a granular and specific level - Can be characterized as internal and external
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system


26. General security concept
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Development guide - Code Review Guide - Testing Guide
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.


27. Vulnerabilities repositories
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model


28. OWASP testing guide
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Covers the necessary procedures and tools to validate software assurance
Security controls applied to mitigate a threat before it materializes


29. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Security controls applied to mitigate a threat before it materializes


30. Non Repudiation
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC


31. Benefits of coding standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards


32. Risk management process
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
Security functionality is easy to use and transparent
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors


33. Software security risk management methodologies
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code


34. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors


35. OWASP Code Review Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk remains after the implementation of mitigating security controls
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management


36. Security design principles
Indicator of magnitude risk in a year ALE = SLE * ARO
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Design to mitigate any single source of complete compromise


37. Categories of controls
Technical - Management - Operational
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Support policies at a granular and specific level - Can be characterized as internal and external


38. Security Risk Management Discipline
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks


39. Properties of secure software
Development guide - Code Review Guide - Testing Guide
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy


40. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking


41. Security profile of a software
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Confidentiality - Integrity - Availability


42. Vulnerability
Secure applicatios running on secure hosts (systems) in a secure network
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Development guide - Code Review Guide - Testing Guide
Access request by a subject to an object is mediated each time and every time.


43. OCTAVE
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Protection against unauthorized information disclosure. It helps maintaining privacy
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability


44. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Authentication
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent


45. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Still under development - aimsto address ISMS implementation guidance
Security controls applied after a threat has been materialized
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy


46. Residual Risk
Risk remains after the implementation of mitigating security controls
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Provides Common Criteria to evaluate IT security product


47. PCI DSS
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
The likelihood that a threat can result into an incident. This is the overall risk of a system
Protection against unauthorized information disclosure. It helps maintaining privacy
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards


48. Complete mediation
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Access request by a subject to an object is mediated each time and every time.
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment


49. Phsychological acceptability
Risk remains after the implementation of mitigating security controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Security functionality is easy to use and transparent


50. Least privilege
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Covers the necessary procedures and tools to validate software assurance
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job