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. Counter measures
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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 controls applied after a threat has been materialized

2. Non Repudiation
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
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 remains after the implementation of mitigating security controls

3. Complete mediation
Design to mitigate any single source of complete compromise
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
Access request by a subject to an object is mediated each time and every time.

4. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Risk remains after the implementation of mitigating security controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites

5. Compartmentalization
Support for accreditation and certification bodies that audit and certify ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Periodic publication by OWASP for top 10 Web application security vulnerabilites

6. Properties of secure software
Secure applicatios running on secure hosts (systems) in a secure network
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Protection against unauthorized information disclosure. It helps maintaining privacy

7. Common best practices significant to Sofware Security
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Authentication
OWASP - ITIL
Access request by a subject to an object is mediated each time and every time.

8. ISO /IEC 27000:2009
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

9. 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
Still under development - aimsto address ISMS implementation guidance
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

10. Safeguards
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
Security controls applied to mitigate a threat before it materializes
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

11. Information Security Models
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

12. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security controls applied after a threat has been materialized
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

13. Least common mechanism
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)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

14. Annual Loss Expectancy (ALE)
Support for accreditation and certification bodies that audit and certify ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Indicator of magnitude risk in a year ALE = SLE * ARO
OWASP - ITIL

15. ISO/IEC 27002:2005
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
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
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

16. OWASP development guide
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Protection against unauthorized information disclosure. It helps maintaining privacy
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

17. ISO/IEC 27005:2008
Security functionality is easy to use and transparent
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Authentication

18. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Number of incidents that can be expected in a year
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Support policies at a granular and specific level - Can be characterized as internal and external

19. Economy of mechanism
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Authentication
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

20. Vulnerability
Security controls applied after a threat has been materialized
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
Protection against unauthorized information disclosure. It helps maintaining privacy
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

21. ISO/IEC 9216
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

22. General security concept
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

23. ISO/IEC 15408
Authentication
Provides Common Criteria to evaluate IT security product
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

24. Take-Grant Model
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
OWASP - ITIL

25. Security profile of a software
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

26. Examples of Security Standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
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

27. Security Standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Support policies at a granular and specific level - Can be characterized as internal and external

28. 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

29. ISO/IEC 27003
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Still under development - aimsto address ISMS implementation guidance

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

31. FIPS140-2 (Security requirement for cryptographic modules)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Authentication
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

32. Technical Controls
Security controls applied after a threat has been materialized
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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:

33. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

34. 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
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
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
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.

35. ISO/IEC 21827:2008
Security controls applied after a threat has been materialized
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

36. Confidentiality
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Protection against unauthorized information disclosure. It helps maintaining privacy
Provides Common Criteria to evaluate IT security product
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

37. Phsychological acceptability
Provides Common Criteria to evaluate IT security product
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
Security functionality is easy to use and transparent

38. Open design
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

39. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Support policies at a granular and specific level - Can be characterized as internal and external
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
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

40. OWASP Code Review Guide
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Number of incidents that can be expected in a year
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Still under development - aimsto address ISMS implementation guidance

41. Categories of controls
Technical - Management - Operational
Indicator of magnitude risk in a year ALE = SLE * ARO
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.
Confidentiality - Integrity - Availability

42. Core Security Concept
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Support policies at a granular and specific level - Can be characterized as internal and external
Confidentiality - Integrity - Availability

43. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

44. Operation Controls
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

45. Risk management process
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:
Covers the necessary procedures and tools to validate software assurance
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c

46. Session Management
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Number of incidents that can be expected in a year
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

47. Availability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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.
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

48. Management Controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

49. Security design principles
Indicator of magnitude risk in a year ALE = SLE * ARO
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

50. FIPS 197 (Advance Cryptographic standards - AES)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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