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. ISO/IEC 27006:2007
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

2. Management Controls
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Secure applicatios running on secure hosts (systems) in a secure network
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

3. DREAD
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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.

4. 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

5. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk 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

6. Availability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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 Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

7. Vulnerabilities repositories
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Access request by a subject to an object is mediated each time and every time.

8. Security Controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Authentication
Security functionality is easy to use and transparent
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

9. Counter measures
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
OWASP - ITIL
Security controls applied after a threat has been materialized
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

10. Security Risk Management Discipline
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

11. Challenges in implementing auditing/logging
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

12. Authentication
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
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

13. Economy of mechanism
Access request by a subject to an object is mediated each time and every time.
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

14. NIST standards related to software security
Support for accreditation and certification bodies that audit and certify 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
Support policies at a granular and specific level - Can be characterized as internal and external
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

15. ISO/IEC 15408
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
Number of incidents that can be expected in a year
estimate potential loss of a single incident: SLE = Asset value * EF(%)

16. Implementation challenges
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.
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

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

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

19. Complete mediation
Access request by a subject to an object is mediated each time and every time.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Development guide - Code Review Guide - Testing Guide

20. Safeguards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Support policies at a granular and specific level - Can be characterized as internal and external
Security controls applied to mitigate a threat before it materializes

21. ISO/IEC 27003
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
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.
Access request by a subject to an object is mediated each time and every time.
Still under development - aimsto address ISMS implementation guidance

22. ISO/IEC 27002:2005
Access request by a subject to an object is mediated each time and every time.
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

23. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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 functionality is easy to use and transparent
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

24. Configurations Parameters Management
Security controls applied after a threat has been materialized
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Provides Common Criteria to evaluate IT security product

25. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Security controls applied after a threat has been materialized
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

26. ISO/IEC 27001:2005
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 the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

27. Core Security Concept
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
Confidentiality - Integrity - Availability
Support for accreditation and certification bodies that audit and certify ISMS
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model

28. ISO/IEC 9216
Support for accreditation and certification bodies that audit and certify ISMS
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

29. OWASP Top 10
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Confidentiality - Integrity - Availability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Periodic publication by OWASP for top 10 Web application security vulnerabilites

30. ISO/IEC 27005:2008
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

31. 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Design to mitigate any single source of complete compromise
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

32. Phsychological acceptability
Number of incidents that can be expected in a year
Security functionality is easy to use and transparent
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

33. Access Matrix model

34. 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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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.
Authentication

35. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
OWASP - ITIL
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

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

37. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
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
Predetermined number of user error allowed before recording it as a security violation

38. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Technical - Management - Operational
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

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

40. Confidentiality
Predetermined number of user error allowed before recording it as a security violation
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Technical - Management - Operational

41. Clipping level
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Predetermined number of user error allowed before recording it as a security violation
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Support for accreditation and certification bodies that audit and certify ISMS

42. Open design
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

43. Integrity
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

44. FIPS140-2 (Security requirement for cryptographic modules)
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 request by a subject to an object is mediated each time and every time.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

45. 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
Access request by a subject to an object is mediated each time and every time.
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Confidentiality - Integrity - Availability

46. 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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

47. Single Loss Expectancy (SLE)
Access request by a subject to an object is mediated each time and every time.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

48. Software security risk management methodologies
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Design to mitigate any single source of complete compromise
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

49. OWASP Code Review Guide
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 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
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

50. OCTAVE
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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 after a threat has been materialized
Number of incidents that can be expected in a year