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. Compartmentalization
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

2. ISO/IEC 27006:2007
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Indicator of magnitude risk in a year ALE = SLE * ARO
Support for accreditation and certification bodies that audit and certify ISMS
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

3. PCI DSS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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

4. Benefits of coding standards
Security controls applied to mitigate a threat before it materializes
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Still under development - aimsto address ISMS implementation guidance
Periodic publication by OWASP for top 10 Web application security vulnerabilites

5. OWASP Code Review Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

6. NIST standards related to software security
Support for accreditation and certification bodies that audit and certify ISMS
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
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

7. OCTAVE
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

8. Software security risk management methodologies
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Indicator of magnitude risk in a year ALE = SLE * ARO
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

9. ISO/IEC 15408
Secure applicatios running on secure hosts (systems) in a secure network
Provides Common Criteria to evaluate IT security product
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
OWASP - ITIL

10. Common best practices significant to Sofware Security
Still under development - aimsto address ISMS implementation guidance
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
OWASP - ITIL
Support policies at a granular and specific level - Can be characterized as internal and external

11. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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

12. ISO /IEC 27000:2009
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

13. Single Loss Expectancy (SLE)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Support policies at a granular and specific level - Can be characterized as internal and external
Design to mitigate any single source of complete compromise

14. General security concept
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Design to mitigate any single source of complete compromise
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

15. Properties of secure 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Covers the necessary procedures and tools to validate software assurance

16. Flaw Hypothesis Method (FHM)
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
OWASP - ITIL
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

17. ISO/IEC 21827:2008
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Indicator of magnitude risk in a year ALE = SLE * ARO
Technical - Management - Operational
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

18. 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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS

19. ISO/IEC 27002:2005
Confidentiality - Integrity - Availability
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

20. FIPS 197 (Advance Cryptographic standards - AES)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Support policies at a granular and specific level - Can be characterized as internal and external
OWASP - ITIL
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

21. Exposure factor (EF)
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Access request by a subject to an object is mediated each time and every time.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

22. Least common mechanism
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied after a threat has been materialized
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

23. Phsychological acceptability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Security functionality is easy to use and transparent
Predetermined number of user error allowed before recording it as a security violation

24. Integrity
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Risk remains after the implementation of mitigating security controls
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

25. Categories of controls
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Technical - Management - Operational
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

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

27. Implementation challenges
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Technical - Management - Operational
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

28. EALs levels
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
Design to mitigate any single source of complete compromise
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

29. Core Security Concept
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Confidentiality - Integrity - Availability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Technical - Management - Operational

30. 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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

31. After identification step is...
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Authentication
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

32. Complete mediation
Design to mitigate any single source of complete compromise
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
Access request by a subject to an object is mediated each time and every time.

33. Information Security Models
Development guide - Code Review Guide - Testing Guide
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
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
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

34. OWASP development guide
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
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

35. STRIDE
Confidentiality - Integrity - Availability
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
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

36. Annual Loss Expectancy (ALE)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

37. ISO/IEC 9216
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

38. Security design principles
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

39. Threat
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
Technical - Management - Operational
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

40. ISO/IEC 27003
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Still under development - aimsto address ISMS implementation guidance
Authentication
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

41. Security Risk Management Discipline
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Still under development - aimsto address ISMS implementation guidance

42. Auditing
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Design to mitigate any single source of complete compromise

43. ISO/IEC 27001:2005
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Support for accreditation and certification bodies that audit and certify ISMS
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Protection against unauthorized information disclosure. It helps maintaining privacy
estimate potential loss of a single incident: SLE = Asset value * EF(%)

45. 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:
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.
Support policies at a granular and specific level - Can be characterized as internal and external
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

46. Holistic Security in software
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Secure applicatios running on secure hosts (systems) in a secure network
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

47. FIPS140-2 (Security requirement for cryptographic modules)
Technical - Management - Operational
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

48. Single point failure
Design to mitigate any single source of complete compromise
Periodic publication by OWASP for top 10 Web application security vulnerabilites
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
OWASP - ITIL

49. Total Risk
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
The likelihood that a threat can result into an incident. This is the overall risk of a system

50. FIPS 201
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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 the architecture and technical requirements for a common identified standard for federal employee and contractors