Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Subjects : certifications, csslp, it-skills

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. Security Standards
Authentication
Support policies at a granular and specific level - Can be characterized as internal and external
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 the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

2. OCTAVE
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Support policies at a granular and specific level - Can be characterized as internal and external
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
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

3. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

4. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security controls applied to mitigate a threat before it materializes

5. Vulnerabilities repositories
Security controls applied to mitigate a threat before it materializes
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

6. FIPS 201
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
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

7. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Risk remains after the implementation of mitigating security controls
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

8. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

9. Take-Grant Model
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
Security functionality is easy to use and transparent
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

10. ISO/IEC 21827:2008
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Predetermined number of user error allowed before recording it as a security violation
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

11. Security profile of a software
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on 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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

12. Implementation challenges
Covers the necessary procedures and tools to validate software assurance
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

13. ISO/IEC 27001:2005
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.
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

14. ISO/IEC 27003
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Security functionality is easy to use and transparent

15. Phsychological acceptability
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Design to mitigate any single source of complete compromise
Security functionality is easy to use and transparent

16. Residual Risk
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Risk remains after the implementation of mitigating security controls
Protection against unauthorized information disclosure. It helps maintaining privacy
The likelihood that a threat can result into an incident. This is the overall risk of a system

17. Safeguards
Security controls applied to mitigate a threat before it materializes
Access request by a subject to an object is mediated each time and every time.
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 the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

18. EALs levels
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Support for accreditation and certification bodies that audit and certify ISMS
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

19. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
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

20. Least privilege
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

21. Clipping level
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Predetermined number of user error allowed before recording it as a security violation

22. STRIDE
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
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

23. Accountability
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
OWASP - ITIL
Indicator of magnitude risk in a year ALE = SLE * ARO

24. NIST standards related to software security
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

25. Annual Rate of Occurence (ARO)
Provides Common Criteria to evaluate IT security product
Number of incidents that can be expected in a year
Secure applicatios running on secure hosts (systems) in a secure network
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

26. FIPS140-2 (Security requirement for cryptographic modules)
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.
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

27. After identification step is...
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Authentication
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

28. Properties of secure software
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
OWASP - ITIL
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

29. Authentication
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
Support policies at a granular and specific level - Can be characterized as internal and external
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
Protection against unauthorized information disclosure. It helps maintaining privacy

30. Availability
Support for accreditation and certification bodies that audit and certify ISMS
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.
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

31. 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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Security controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls

32. Security design principles
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
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
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

33. Annual Loss Expectancy (ALE)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Indicator of magnitude risk in a year ALE = SLE * ARO
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

34. Software security risk management methodologies
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

35. Single point failure
Confidentiality - Integrity - Availability
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Support for accreditation and certification bodies that audit and certify ISMS
Design to mitigate any single source of complete compromise

36. Non Repudiation
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

37. Security Risk Management Discipline
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

38. Holistic Security in software
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Provides Common Criteria to evaluate IT security product
Secure applicatios running on secure hosts (systems) in a secure network
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

39. Common best practices significant to Sofware Security
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
OWASP - ITIL
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
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

40. ISO /IEC 27000:2009
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 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
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

41. Technical Controls
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.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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

42. OWASP Code Review Guide
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

43. Vulnerability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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
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. 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
Support policies at a granular and specific level - Can be characterized as internal and external
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

45. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
OWASP - ITIL

46. Multifactor authentication
The likelihood that a threat can result into an incident. This is the overall risk of a system
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Still under development - aimsto address ISMS implementation guidance
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

47. Least common mechanism
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

48. ISO/IEC 27006:2007
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support for accreditation and certification bodies that audit and certify ISMS

49. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
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

50. ISO/IEC 27002:2005
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS