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. ISO/IEC 27005:2008
Secure applicatios running on secure hosts (systems) in a secure network
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

2. Vulnerabilities repositories
Protection against unauthorized information disclosure. It helps maintaining privacy
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Design to mitigate any single source of complete compromise
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

3. Accountability
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)
Provides Common Criteria to evaluate IT security product
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

4. Single point failure
Design to mitigate any single source of complete compromise
Indicator of magnitude risk in a year ALE = SLE * ARO
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

5. Security design principles
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security controls applied after a threat has been materialized
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

6. Common best practices significant to Sofware Security
OWASP - ITIL
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

7. ISO/IEC 9216
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

8. Single Loss Expectancy (SLE)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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

9. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Authentication
Security functionality is easy to use and transparent
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

10. Security Policies

11. Phsychological acceptability
Security functionality is easy to use and transparent
Still under development - aimsto address ISMS implementation guidance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

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

13. Authentication
Predetermined number of user error allowed before recording it as a security violation
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

14. Counter measures
Security controls applied after a threat has been materialized
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Authentication
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

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

16. Holistic Security in software
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Secure applicatios running on secure hosts (systems) in a secure network
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering 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

17. OWASP development guide
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
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
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

18. OWASP Top 10
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
Design to mitigate any single source of complete compromise
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

19. Access Matrix model

20. EALs levels
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

21. Integrity
Access request by a subject to an object is mediated each time and every time.
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
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
OWASP - ITIL

22. Popular guides developed by OWASP
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Development guide - Code Review Guide - Testing Guide
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

23. Categories of controls
Technical - Management - Operational
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

24. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

25. Least privilege
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

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

27. Security Controls
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Design to mitigate any single source of complete compromise

28. Threat
Security controls applied after a threat has been materialized
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

29. Security profile of a software
Covers the necessary procedures and tools to validate software assurance
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
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
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

30. ISO/IEC 27001:2005
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
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
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

31. Flaw Hypothesis Method (FHM)
Still under development - aimsto address ISMS implementation guidance
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

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

33. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Indicator of magnitude risk in a year ALE = SLE * ARO
Provides Common Criteria to evaluate IT security product
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

34. Total Risk
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

35. 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
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Periodic publication by OWASP for top 10 Web application security vulnerabilites

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

37. Challenges in implementing auditing/logging
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Number of incidents that can be expected in a year

38. Technical Controls
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.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Protection against unauthorized information disclosure. It helps maintaining privacy
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

39. Confidentiality
Provides Common Criteria to evaluate IT security product
Protection against unauthorized information disclosure. It helps maintaining privacy
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Access request by a subject to an object is mediated each time and every time.

40. Auditing
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Security functionality is easy to use and transparent
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

41. OCTAVE
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

42. PCI DSS
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 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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security controls applied to mitigate a threat before it materializes

43. Compartmentalization
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

44. Operation Controls
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

45. OWASP testing guide
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Covers the necessary procedures and tools to validate software assurance

46. DREAD
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Confidentiality - Integrity - Availability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

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

48. Examples of Security Standards
Predetermined number of user error allowed before recording it as a security violation
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
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

49. ISO/IEC 21827:2008
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
Predetermined number of user error allowed before recording it as a security violation
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

50. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities