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. Accountability
Risk remains after the implementation of mitigating security controls
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

2. Security Standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Support policies at a granular and specific level - Can be characterized as internal and external
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

3. Benefits of coding standards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

4. 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
Authentication
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

5. ISO/IEC 21827:2008
OWASP - ITIL
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

6. General security concept
Access request by a subject to an object is mediated each time and every time.
Number of incidents that can be expected in a year
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

7. STRIDE
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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

8. Counter measures
Security controls applied after a threat has been materialized
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

9. Clipping level
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Predetermined number of user error allowed before recording it as a security violation
Protection against unauthorized information disclosure. It helps maintaining privacy
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

10. Annual Loss Expectancy (ALE)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk remains after the implementation of mitigating security controls
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

11. Take-Grant 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
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

12. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Provides Common Criteria to evaluate IT security product

13. Risk management process
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
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

14. Authorization
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
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
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

15. ISO/IEC 27002:2005
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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 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

16. 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
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
Support for accreditation and certification bodies that audit and certify ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system

17. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Security controls applied to mitigate a threat before it materializes
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:

18. Single point failure
Design to mitigate any single source of complete compromise
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 request by a subject to an object is mediated each time and every time.

19. Security Risk Management Discipline
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Design to mitigate any single source of complete compromise
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

20. Integrity
Security controls applied after a threat has been materialized
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
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
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

21. Holistic Security in software
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Secure applicatios running on secure hosts (systems) in a secure network
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Design to mitigate any single source of complete compromise

22. Operation 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
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

23. ISO/IEC 9216
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

24. Implementation challenges
Security controls applied after a threat has been materialized
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Number of incidents that can be expected in a year
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

25. Confidentiality
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Protection against unauthorized information disclosure. It helps maintaining privacy
Technical - Management - Operational
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

26. Vulnerability
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

27. NIST standards related to software security
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
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 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

28. 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

29. PCI DSS
Risk remains after the implementation of mitigating security controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
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

30. Residual Risk
Risk remains after the implementation of mitigating security controls
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
Protection against unauthorized information disclosure. It helps maintaining privacy

31. 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
Design to mitigate any single source of complete compromise
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
The likelihood that a threat can result into an incident. This is the overall risk of a system

32. Security Controls
OWASP - ITIL
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Design to mitigate any single source of complete compromise

33. Availability
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
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.
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

34. Authentication
Number of incidents that can be expected in a year
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
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

35. Access Matrix model

36. Non Repudiation
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

37. Economy of mechanism
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Confidentiality - Integrity - Availability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

38. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Design to mitigate any single source of complete compromise

39. Categories of 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
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Technical - Management - Operational

40. OWASP testing guide
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

41. OWASP Code Review Guide
Provides Common Criteria to evaluate IT security product
Design to mitigate any single source of complete compromise
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

42. Security Policies

43. ISO /IEC 27000:2009
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 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
Risk remains after the implementation of mitigating security controls
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

44. Single Loss Expectancy (SLE)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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(%)
Secure applicatios running on secure hosts (systems) in a secure network

45. After identification step is...
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Authentication

46. Develop hack resilient software
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Indicator of magnitude risk in a year ALE = SLE * ARO

47. Multifactor authentication
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
Development guide - Code Review Guide - Testing Guide
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

48. Session Management
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
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
Predetermined number of user error allowed before recording it as a security violation
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

49. Challenges in implementing auditing/logging
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

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