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. Annual Rate of Occurence (ARO)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Number of incidents that can be expected in a year
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

2. Security Standards
Security controls applied after a threat has been materialized
Support policies at a granular and specific level - Can be characterized as internal and external
Number of incidents that can be expected in a year
Provides Common Criteria to evaluate IT security product

3. Vulnerabilities repositories
Security controls applied after a threat has been materialized
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

4. Error and exception management
Access request by a subject to an object is mediated each time and every time.
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
Protection against unauthorized information disclosure. It helps maintaining privacy

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

6. Safeguards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Authentication
Security controls applied to mitigate a threat before it materializes
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

7. Open design
Security functionality is easy to use and transparent
Secure applicatios running on secure hosts (systems) in a secure network
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

8. PCI DSS
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

9. Access Matrix model

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
Technical - Management - Operational
Still under development - aimsto address ISMS implementation guidance
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

11. Counter measures
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security controls applied after a threat has been materialized
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
Number of incidents that can be expected in a year

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

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

14. 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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Authentication
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

15. ISO/IEC 27006:2007
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
Support for accreditation and certification bodies that audit and certify 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

16. Multifactor authentication
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

17. Accountability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Protection against unauthorized information disclosure. It helps maintaining privacy
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

18. Least common mechanism
Confidentiality - Integrity - Availability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

19. STRIDE
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Number of incidents that can be expected in a year
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
Access request by a subject to an object is mediated each time and every time.

20. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

21. OWASP development guide
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

22. Flaw Hypothesis Method (FHM)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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.

23. Auditing
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Confidentiality - Integrity - Availability
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

24. Benefits of coding standards
Risk remains after the implementation of mitigating security controls
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

25. 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
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Security controls applied after a threat has been materialized

26. General security concept
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
OWASP - ITIL
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

27. Economy of mechanism
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

28. EALs levels
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

29. Threat
Indicator of magnitude risk in a year ALE = SLE * ARO
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Access request by a subject to an object is mediated each time and every time.

30. Operation Controls
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

31. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security functionality is easy to use and transparent
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

32. Properties of secure software
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Periodic publication by OWASP for top 10 Web application security vulnerabilites

33. OWASP Code Review Guide
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
The likelihood that a threat can result into an incident. This is the overall risk of a system

34. Complete mediation
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Confidentiality - Integrity - Availability
Predetermined number of user error allowed before recording it as a security violation
Access request by a subject to an object is mediated each time and every time.

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

36. Develop hack resilient software
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

37. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Covers the necessary procedures and tools to validate software assurance
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

38. Configurations Parameters Management
OWASP - ITIL
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
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

39. Challenges in implementing auditing/logging
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

40. Implementation challenges
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

41. Single point failure
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
Design to mitigate any single source of complete compromise
Covers the necessary procedures and tools to validate software assurance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

42. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Design to mitigate any single source of complete compromise

43. FIPS 197 (Advance Cryptographic standards - AES)
Covers the necessary procedures and tools to validate software assurance
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
Security controls applied to mitigate a threat before it materializes

44. Examples of Security Standards
Still under development - aimsto address ISMS implementation guidance
Security controls applied after a threat has been materialized
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Technical - Management - Operational

45. Confidentiality
Support policies at a granular and specific level - Can be characterized as internal and external
Protection against unauthorized information disclosure. It helps maintaining privacy
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
OWASP - ITIL

46. Residual Risk
Risk remains after the implementation of mitigating security 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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Number of incidents that can be expected in a year

47. Security Policies

48. Core Security Concept
Development guide - Code Review Guide - Testing Guide
Confidentiality - Integrity - Availability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

49. ISO/IEC 15408
Support for accreditation and certification bodies that audit and certify ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Provides Common Criteria to evaluate IT security product
estimate potential loss of a single incident: SLE = Asset value * EF(%)

50. ISO/IEC 27002:2005
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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