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. Take-Grant Model
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Protection against unauthorized information disclosure. It helps maintaining privacy
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)


2. Security Policies


3. Auditing
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Support for accreditation and certification bodies that audit and certify ISMS
Security functionality is easy to use and transparent
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


4. Annual Loss Expectancy (ALE)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Indicator of magnitude risk in a year ALE = SLE * ARO


5. Annual Rate of Occurence (ARO)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Number of incidents that can be expected in a year
Secure applicatios running on secure hosts (systems) in a secure network


6. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks


7. Single Loss Expectancy (SLE)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Provides Common Criteria to evaluate IT security product


8. Session Management
Indicator of magnitude risk in a year ALE = SLE * ARO
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)


9. ISO/IEC 15408
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Provides Common Criteria to evaluate IT security product
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection


10. ISO/IEC 27006:2007
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Covers the necessary procedures and tools to validate software assurance
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Support for accreditation and certification bodies that audit and certify ISMS


11. Availability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
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 controls applied to mitigate a threat before it materializes


12. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Still under development - aimsto address ISMS implementation guidance
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.


13. Threat
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
estimate potential loss of a single incident: SLE = Asset value * EF(%)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.


14. Integrity
Security controls applied to mitigate a threat before it materializes
Indicator of magnitude risk in a year ALE = SLE * ARO
Security controls applied after a threat has been materialized
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


15. EALs levels
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
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
Access request by a subject to an object is mediated each time and every time.


16. Multifactor authentication
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Covers the necessary procedures and tools to validate software assurance
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)


17. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.


18. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Secure applicatios running on secure hosts (systems) in a secure network
The likelihood that a threat can result into an incident. This is the overall risk of a system
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible


19. ISO/IEC 21827:2008
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Periodic publication by OWASP for top 10 Web application security vulnerabilites


20. Clipping level
Development guide - Code Review Guide - Testing Guide
Number of incidents that can be expected in a year
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Predetermined number of user error allowed before recording it as a security violation


21. Safeguards
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Security controls applied to mitigate a threat before it materializes
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Design to mitigate any single source of complete compromise


22. STRIDE
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
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
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)


23. Risk management process
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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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


24. Popular guides developed by OWASP
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Support for accreditation and certification bodies that audit and certify ISMS
Development guide - Code Review Guide - Testing Guide
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)


25. Single point failure
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
Development guide - Code Review Guide - Testing Guide
Support policies at a granular and specific level - Can be characterized as internal and external
Design to mitigate any single source of complete compromise


26. Configurations Parameters Management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Support policies at a granular and specific level - Can be characterized as internal and external


27. Authentication
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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


28. Implementation challenges
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk remains after the implementation of mitigating security controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability


29. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
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


30. Accountability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual


31. Phsychological acceptability
Security functionality is easy to use and transparent
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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


32. Authorization
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
Number of incidents that can be expected in a year
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them


33. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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


34. Non Repudiation
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
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management


35. Vulnerability
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
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability


36. Properties of secure software
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Support policies at a granular and specific level - Can be characterized as internal and external


37. Security Risk Management Discipline
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks


38. ISO/IEC 27003
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
Authentication
Still under development - aimsto address ISMS implementation guidance


39. Common best practices significant to Sofware Security
OWASP - ITIL
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
Authentication
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods


40. Challenges in implementing auditing/logging
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Access request by a subject to an object is mediated each time and every time.


41. Residual Risk
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Risk remains after the implementation of mitigating security controls


42. Security design principles
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
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 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


43. Exposure factor (EF)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development


44. ISO/IEC 27005:2008
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
Development guide - Code Review Guide - Testing Guide
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management


45. Least privilege
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Covers the necessary procedures and tools to validate software assurance


46. Flaw Hypothesis Method (FHM)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Indicator of magnitude risk in a year ALE = SLE * ARO
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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


47. Security profile of a software
Security controls applied to mitigate a threat before it materializes
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
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
Number of incidents that can be expected in a year


48. Information Security Models
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
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


49. Core Security Concept
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Confidentiality - Integrity - Availability


50. ISO /IEC 27000:2009
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
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
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run