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. Single point failure
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
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
Design to mitigate any single source of complete compromise
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability


2. Annual Rate of Occurence (ARO)
Secure applicatios running on secure hosts (systems) in a secure network
Number of incidents that can be expected in a year
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Periodic publication by OWASP for top 10 Web application security vulnerabilites


3. After identification step is...
Authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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


4. Core Security Concept
Confidentiality - Integrity - Availability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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)


5. Auditing
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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.
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


6. Operation Controls
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors


7. ISO/IEC 21827:2008
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Authentication
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer


8. OWASP testing guide
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Covers the necessary procedures and tools to validate software assurance


9. Open design
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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


10. Multifactor authentication
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS


11. Security Controls
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
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:


12. Security design principles
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors


13. Residual Risk
Risk remains after the implementation of mitigating security controls
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
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
Authentication


14. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security controls applied after a threat has been materialized
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


15. 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
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
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
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


16. STRIDE
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
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO


17. Threat
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Design to mitigate any single source of complete compromise


18. Safeguards
Security controls applied to mitigate a threat before it materializes
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
Predetermined number of user error allowed before recording it as a security violation
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


19. Clipping level
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Predetermined number of user error allowed before recording it as a security violation


20. ISO/IEC 9216
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
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.
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


21. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security controls applied after a threat has been materialized
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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


22. ISO /IEC 27000:2009
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors


23. OWASP Code Review Guide
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
OWASP - ITIL
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them


24. Flaw Hypothesis Method (FHM)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege


25. Error and exception management
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Number of incidents that can be expected in a year
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
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


26. Authorization
Support policies at a granular and specific level - Can be characterized as internal and external
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The likelihood that a threat can result into an incident. This is the overall risk of a system
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


27. Counter measures
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Security controls applied after a threat has been materialized
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors


28. EALs levels
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Indicator of magnitude risk in a year ALE = SLE * ARO
Predetermined number of user error allowed before recording it as a security violation


29. Popular guides developed by OWASP
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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.
Development guide - Code Review Guide - Testing Guide


30. Confidentiality
Confidentiality - Integrity - Availability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Protection against unauthorized information disclosure. It helps maintaining privacy


31. ISO/IEC 27003
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Support for accreditation and certification bodies that audit and certify ISMS
Still under development - aimsto address ISMS implementation guidance


32. Risk management process
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
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.
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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


33. Holistic Security in software
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Development guide - Code Review Guide - Testing Guide
Secure applicatios running on secure hosts (systems) in a secure network


34. FIPS 197 (Advance Cryptographic standards - AES)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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


35. Compartmentalization
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Access request by a subject to an object is mediated each time and every time.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Provides Common Criteria to evaluate IT security product


36. Annual Loss Expectancy (ALE)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Authentication
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
Indicator of magnitude risk in a year ALE = SLE * ARO


37. Categories of controls
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
Technical - Management - Operational
Security controls applied to mitigate a threat before it materializes
Successful completion of a critical task is dependent on 2 or more conditions that need to be met


38. 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
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 controls applied after a threat has been materialized
Secure applicatios running on secure hosts (systems) in a secure network


39. Complete mediation
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
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
Development guide - Code Review Guide - Testing Guide
Access request by a subject to an object is mediated each time and every time.


40. Develop hack resilient software
Covers the necessary procedures and tools to validate software assurance
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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


41. Session Management
Security functionality is easy to use and transparent
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
Security controls applied after a threat has been materialized
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer


42. Configurations Parameters Management
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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


44. Integrity
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege


45. Technical Controls
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Technical - Management - Operational
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment


46. Information Security Models
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
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
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
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


47. ISO/IEC 27001:2005
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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


48. ISO/IEC 27002:2005
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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


49. Accountability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
OWASP - ITIL


50. 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
Security controls applied to mitigate a threat before it materializes
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)