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

2. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Predetermined number of user error allowed before recording it as a security violation

3. Security Risk Management Discipline
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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 controls applied after a threat has been materialized

4. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Protection against unauthorized information disclosure. It helps maintaining privacy
Technical - Management - Operational
Still under development - aimsto address ISMS implementation guidance

5. Access Matrix model

6. DREAD
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Predetermined number of user error allowed before recording it as a security violation

7. Safeguards
Protection against unauthorized information disclosure. It helps maintaining privacy
Security controls applied to mitigate a threat before it materializes
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

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

9. Session Management
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Provides Common Criteria to evaluate IT security product

10. ISO/IEC 21827:2008
Risk remains after the implementation of mitigating security controls
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

11. Take-Grant Model
OWASP - ITIL
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

12. Operation Controls
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
Risk remains after the implementation of mitigating security controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

13. Popular guides developed by OWASP
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Development guide - Code Review Guide - Testing Guide
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

14. ISO /IEC 27000:2009
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Access request by a subject to an object is mediated each time and every time.
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

15. 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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

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

17. Management Controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

18. Phsychological acceptability
Security functionality is easy to use and transparent
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested

19. OCTAVE
Predetermined number of user error allowed before recording it as a security violation
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

20. Risk management process
Support for accreditation and certification bodies that audit and certify ISMS
Design to mitigate any single source of complete compromise
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

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

22. ISO/IEC 9216
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
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.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

23. Multifactor authentication
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

24. Residual Risk
Provides Common Criteria to evaluate IT security product
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Risk remains after the implementation of mitigating security controls

25. Total Risk
Security controls applied after a threat has been materialized
The likelihood that a threat can result into an incident. This is the overall risk of a system
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

26. Categories of controls
Number of incidents that can be expected in a year
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Secure applicatios running on secure hosts (systems) in a secure network
Technical - Management - Operational

27. 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
OWASP - ITIL
Development guide - Code Review Guide - Testing Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

28. ISO/IEC 15408
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Authentication
Provides Common Criteria to evaluate IT security product
Still under development - aimsto address ISMS implementation guidance

29. Flaw Hypothesis Method (FHM)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Support policies at a granular and specific level - Can be characterized as internal and external
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

30. Availability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Support for accreditation and certification bodies that audit and certify ISMS
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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.

31. OWASP Top 10
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Development guide - Code Review Guide - Testing Guide

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

33. Configurations Parameters Management
Predetermined number of user error allowed before recording it as a security violation
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

34. Annual Loss Expectancy (ALE)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Predetermined number of user error allowed before recording it as a security violation
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Indicator of magnitude risk in a year ALE = SLE * ARO

35. ISO/IEC 27001:2005
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
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security functionality is easy to use and transparent

36. Accountability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

37. Security Standards
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Support policies at a granular and specific level - Can be characterized as internal and external
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

38. Properties of secure software
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

39. ISO/IEC 27006:2007
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Support for accreditation and certification bodies that audit and certify ISMS
Security functionality is easy to use and transparent
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

40. Vulnerabilities repositories
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.
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Technical - Management - Operational

41. Clipping level
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Predetermined number of user error allowed before recording it as a security violation
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
Indicator of magnitude risk in a year ALE = SLE * ARO

42. Auditing
Risk remains after the implementation of mitigating security controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Number of incidents that can be expected in a year
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

43. After identification step is...
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Design to mitigate any single source of complete compromise
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
Authentication

44. Single Loss Expectancy (SLE)
Authentication
Design to mitigate any single source of complete compromise
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

45. Integrity
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
OWASP - ITIL

46. Implementation challenges
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

47. Least privilege
Risk remains after the implementation of mitigating security controls
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Indicator of magnitude risk in a year ALE = SLE * ARO

48. Challenges in implementing auditing/logging
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

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

50. FIPS140-2 (Security requirement for cryptographic modules)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment