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

2. Categories of controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Technical - Management - Operational
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
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

3. Non Repudiation
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Confidentiality - Integrity - Availability

4. Single Loss Expectancy (SLE)
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
estimate potential loss of a single incident: SLE = Asset value * EF(%)
OWASP - ITIL

5. Counter measures
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
OWASP - ITIL
Security controls applied after a threat has been materialized

6. Exposure factor (EF)
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

7. Access Matrix model

8. FIPS140-2 (Security requirement for cryptographic modules)
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

9. Economy of mechanism
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
OWASP - ITIL
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

10. ISO /IEC 27000:2009
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Risk 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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

11. Implementation challenges
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support policies at a granular and specific level - Can be characterized as internal and external

12. Session Management
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
Access request by a subject to an object is mediated each time and every time.
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
Confidentiality - Integrity - Availability

13. Software security risk management methodologies
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

14. Configurations Parameters Management
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

15. Clipping level
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Predetermined number of user error allowed before recording it as a security violation

16. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
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

17. Open design
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.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

18. 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
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

19. Auditing
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

20. Popular guides developed by OWASP
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Support policies at a granular and specific level - Can be characterized as internal and external
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
Development guide - Code Review Guide - Testing Guide

21. Safeguards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security controls applied to mitigate a threat before it materializes

22. ISO/IEC 27005:2008
Technical - Management - Operational
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

23. Complete mediation
Design to mitigate any single source of complete compromise
Covers the necessary procedures and tools to validate software assurance
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Access request by a subject to an object is mediated each time and every time.

24. Error and exception management
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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
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

25. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

26. Security Policies

27. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

28. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

29. After identification step is...
Authentication
Support for accreditation and certification bodies that audit and certify 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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

30. Examples of Security Standards
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Support policies at a granular and specific level - Can be characterized as internal and external
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

31. ISO/IEC 21827:2008
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

32. Operation Controls
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

33. Challenges in implementing auditing/logging
Predetermined number of user error allowed before recording it as a security violation
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

34. Information Security Models
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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

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

36. Holistic Security in software
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network

37. Security Standards
Covers the necessary procedures and tools to validate software assurance
Support policies at a granular and specific level - Can be characterized as internal and external
Technical - Management - Operational
Risk remains after the implementation of mitigating security controls

38. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Predetermined number of user error allowed before recording it as a security violation
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

39. OWASP Code Review Guide
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Predetermined number of user error allowed before recording it as a security violation
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk remains after the implementation of mitigating security controls

40. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

41. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Confidentiality - Integrity - Availability
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

42. NIST standards related to software security
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
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
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

43. General security concept
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

44. Risk management process
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Predetermined number of user error allowed before recording it as a security violation
Covers the necessary procedures and tools to validate software assurance
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

45. Technical Controls
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

46. OWASP Top 10
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
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
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

47. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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

48. ISO/IEC 27003
Number of incidents that can be expected in a year
Still under development - aimsto address ISMS implementation guidance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

49. ISO/IEC 27001:2005
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Support policies at a granular and specific level - Can be characterized as internal and external

50. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support for accreditation and certification bodies that audit and certify ISMS