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. NIST standards related to software security
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

2. Threat
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Predetermined number of user error allowed before recording it as a security violation
Protection against unauthorized information disclosure. It helps maintaining privacy

3. Core Security Concept
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
Number of incidents that can be expected in a year
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

4. Counter measures
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Security functionality is easy to use and transparent
Security controls applied after a threat has been materialized
Protection against unauthorized information disclosure. It helps maintaining privacy

5. Holistic Security in software
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Secure applicatios running on secure hosts (systems) in a secure network
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

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

7. Phsychological acceptability
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Security functionality is easy to use and transparent
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

8. After identification step is...
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Authentication
Access request by a subject to an object is mediated each time and every time.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

9. Develop hack resilient software
Security functionality is easy to use and transparent
Confidentiality - Integrity - Availability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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 27001:2005
Security functionality is easy to use and transparent
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Periodic publication by OWASP for top 10 Web application security vulnerabilites

11. Popular guides developed by OWASP
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Development guide - Code Review Guide - Testing Guide

12. OCTAVE
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Covers the necessary procedures and tools to validate software assurance
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

13. Examples of Security 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
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

14. Security Controls
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking

15. OWASP testing guide
OWASP - ITIL
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
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
Covers the necessary procedures and tools to validate software assurance

16. Security Risk Management Discipline
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:
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

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

18. Complete mediation
Support for accreditation and certification bodies that audit and certify ISMS
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
Access request by a subject to an object is mediated each time and every time.
Periodic publication by OWASP for top 10 Web application security vulnerabilites

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

20. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

21. Exposure factor (EF)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

22. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Secure applicatios running on secure hosts (systems) in a secure network
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

23. ISO/IEC 9216
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

24. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
The likelihood that a threat can result into an incident. This is the overall risk of a system
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

25. Total Risk
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
The likelihood that a threat can result into an incident. This is the overall risk of a system
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

26. Information Security Models
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
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
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

27. Residual Risk
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

28. Accountability
Security controls applied after a threat has been materialized
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

29. Security 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
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
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

30. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Development guide - Code Review Guide - Testing Guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

31. Compartmentalization
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

32. Challenges in implementing auditing/logging
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Development guide - Code Review Guide - Testing Guide
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

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

34. Technical Controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

35. Categories of controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Support for accreditation and certification bodies that audit and certify ISMS
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

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

37. PCI DSS
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
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
Provides Common Criteria to evaluate IT security product
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

38. Security Policies

39. 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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

40. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Technical - Management - Operational

41. ISO/IEC 21827:2008
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Development guide - Code Review Guide - Testing Guide
Secure applicatios running on secure hosts (systems) in a secure network

42. Clipping level
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
Predetermined number of user error allowed before recording it as a security violation
Security controls applied to mitigate a threat before it materializes
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

43. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

44. Confidentiality
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
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

45. Risk management process
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

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

47. ISO/IEC 27002:2005
Technical - Management - Operational
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
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

48. Vulnerabilities repositories
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

49. Access Matrix model

50. ISO /IEC 27000:2009
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Development guide - Code Review Guide - Testing Guide