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. Holistic Security in software
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Covers the necessary procedures and tools to validate software assurance
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Secure applicatios running on secure hosts (systems) in a secure network

2. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Predetermined number of user error allowed before recording it as a security violation
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

3. FIPS 201
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Number of incidents that can be expected in a year

4. Software security risk management methodologies
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
The likelihood that a threat can result into an incident. This is the overall risk of a system

5. Annual Rate of Occurence (ARO)
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Number of incidents that can be expected in a year

6. Vulnerabilities repositories
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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.

7. Economy of mechanism
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

8. 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
Number of incidents that can be expected in a year
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

9. Implementation challenges
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security controls applied to mitigate a threat before it materializes
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The likelihood that a threat can result into an incident. This is the overall risk of a system

10. Single Loss Expectancy (SLE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Development guide - Code Review Guide - Testing Guide
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Number of incidents that can be expected in a year

11. Examples of Security Standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

12. Error and exception management
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
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 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
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

13. OWASP testing guide
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Covers the necessary procedures and tools to validate software assurance
Design to mitigate any single source of complete compromise
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

14. ISO/IEC 27006:2007
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
Covers the necessary procedures and tools to validate software assurance
Support for accreditation and certification bodies that audit and certify ISMS
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

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

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

17. Single point failure
Security controls applied after a threat has been materialized
Still under development - aimsto address ISMS implementation guidance
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

18. Vulnerability
Covers the necessary procedures and tools to validate software assurance
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

19. ISO/IEC 15408
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Secure applicatios running on secure hosts (systems) in a secure network
Provides Common Criteria to evaluate IT security product

20. Authorization
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
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
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
Risk remains after the implementation of mitigating security controls

21. Properties of secure software
Security controls applied after a threat has been materialized
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

22. ISO/IEC 27003
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
The likelihood that a threat can result into an incident. This is the overall risk of a system
Still under development - aimsto address ISMS implementation guidance

23. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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.

24. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Risk remains after the implementation of mitigating security controls
Provides Common Criteria to evaluate IT security product
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

25. Access Matrix model

26. Security profile of a 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
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
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

27. STRIDE
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
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 mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Technical - Management - Operational

28. Least privilege
Risk remains after the implementation of mitigating security controls
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

29. 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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

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

31. ISO/IEC 27002:2005
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

32. Risk management process
Protection against unauthorized information disclosure. It helps maintaining privacy
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 for accreditation and certification bodies that audit and certify ISMS
Security functionality is easy to use and transparent

33. Session Management
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

34. 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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

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

36. Exposure factor (EF)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

37. NIST standards related to software security
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
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
Still under development - aimsto address ISMS implementation guidance
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

38. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

39. Counter measures
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
Risk remains after the implementation of mitigating security controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

40. OWASP development guide
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

41. Non Repudiation
Still under development - aimsto address ISMS implementation guidance
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
Technical - Management - Operational
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

42. Multifactor authentication
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS

43. Information Security Models
Design to mitigate any single source of complete compromise
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

44. Security Standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Predetermined number of user error allowed before recording it as a security violation
Support policies at a granular and specific level - Can be characterized as internal and external
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

45. Threat
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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.

46. Develop hack resilient software
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

47. Security Controls
Confidentiality - Integrity - Availability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Secure applicatios running on secure hosts (systems) in a secure network

48. OCTAVE
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Still under development - aimsto address ISMS implementation guidance
Secure applicatios running on secure hosts (systems) in a secure network
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

49. FIPS140-2 (Security requirement for cryptographic modules)
Still under development - aimsto address ISMS implementation guidance
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.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

50. Accountability
Still under development - aimsto address ISMS implementation guidance
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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