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. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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.
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
Covers the necessary procedures and tools to validate software assurance

2. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
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
Access request by a subject to an object is mediated each time and every time.

3. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Still under development - aimsto address ISMS implementation guidance

4. ISO/IEC 9216
Technical - Management - Operational
Access request by a subject to an object is mediated each time and every time.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

5. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

6. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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
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. Annual Loss Expectancy (ALE)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Indicator of magnitude risk in a year ALE = SLE * ARO
Secure applicatios running on secure hosts (systems) in a secure network

8. Open design
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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

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

10. Single point failure
Design to mitigate any single source of complete compromise
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Development guide - Code Review Guide - Testing Guide

11. Take-Grant Model
The likelihood that a threat can result into an incident. This is the overall risk of a system
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

12. Phsychological acceptability
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
OWASP - ITIL
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
Security functionality is easy to use and transparent

13. Flaw Hypothesis Method (FHM)
OWASP - ITIL
Risk remains after the implementation of mitigating security controls
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

14. Access Matrix model

15. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

16. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
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
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

17. Compartmentalization
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Number of incidents that can be expected in a year

18. ISO/IEC 21827:2008
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

19. Risk management process
Authentication
Development guide - Code Review Guide - Testing 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
The likelihood that a threat can result into an incident. This is the overall risk of a system

20. Total Risk
Predetermined number of user error allowed before recording it as a security violation
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system

21. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

22. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Design to mitigate any single source of complete compromise

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

24. Categories of controls
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Technical - Management - Operational
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

25. Clipping level
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
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
Risk remains after the implementation of mitigating security controls
Predetermined number of user error allowed before recording it as a security violation

26. OCTAVE
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

27. Integrity
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Provides Common Criteria to evaluate IT security product

28. Confidentiality
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Covers the necessary procedures and tools to validate software assurance
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Protection against unauthorized information disclosure. It helps maintaining privacy

29. After identification step is...
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Authentication
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

30. ISO/IEC 27001:2005
Access request by a subject to an object is mediated each time and every time.
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)
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

31. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Support for accreditation and certification bodies that audit and certify ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

32. Properties of secure software
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 possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

33. ISO/IEC 27006:2007
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Support for accreditation and certification bodies that audit and certify ISMS

34. Authentication
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Predetermined number of user error allowed before recording it as a security violation
Provides Common Criteria to evaluate IT security product

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

36. Auditing
Security controls applied after a threat has been materialized
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

37. Configurations Parameters Management
Authentication
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

38. Safeguards
Security controls applied to mitigate a threat before it materializes
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Secure applicatios running on secure hosts (systems) in a secure network
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

39. ISO /IEC 27000:2009
Support policies at a granular and specific level - Can be characterized as internal and external
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

40. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Support policies at a granular and specific level - Can be characterized as internal and external
Risk remains after the implementation of mitigating security 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

41. 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
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
Secure applicatios running on secure hosts (systems) in a secure network

42. Benefits of coding standards
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Protection against unauthorized information disclosure. It helps maintaining privacy
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

43. PCI DSS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Confidentiality - Integrity - Availability
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
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

44. Common best practices significant to Sofware 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
OWASP - ITIL
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

45. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Authentication
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

46. Security Policies

47. Availability
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
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.
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

48. Multifactor authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

49. ISO/IEC 15408
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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 Common Criteria to evaluate IT security product

50. Complete mediation
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
Access request by a subject to an object is mediated each time and every time.
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS