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. Confidentiality
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Protection against unauthorized information disclosure. It helps maintaining privacy

2. FIPS140-2 (Security requirement for cryptographic modules)
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of 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

3. EALs levels
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

4. Auditing
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

5. Security Policies

6. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

7. Popular guides developed by OWASP
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
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
Development guide - Code Review Guide - Testing Guide
Support policies at a granular and specific level - Can be characterized as internal and external

8. OWASP testing guide
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Protection against unauthorized information disclosure. It helps maintaining privacy
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Covers the necessary procedures and tools to validate software assurance

9. Total Risk
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Support policies at a granular and specific level - Can be characterized as internal and external
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

10. ISO/IEC 27006:2007
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support for accreditation and certification bodies that audit and certify ISMS
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

11. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
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

12. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

13. Counter measures
Covers the necessary procedures and tools to validate software assurance
Security controls applied after a threat has been materialized
Number of incidents that can be expected in a year
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

14. 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
Indicator of magnitude risk in a year ALE = SLE * ARO
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

15. Holistic Security in software
Number of incidents that can be expected in a year
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
Secure applicatios running on secure hosts (systems) in a secure network
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

16. Information Security Models
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security controls applied after a threat has been materialized
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

17. Vulnerabilities repositories
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

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

19. After identification step is...
Authentication
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

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

21. ISO/IEC 27002:2005
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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 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

22. Categories of 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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Technical - Management - Operational
Confidentiality - Integrity - Availability

23. ISO/IEC 27005:2008
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

24. FIPS 201
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

25. Software security risk management methodologies
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a

26. Vulnerability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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 remains after the implementation of mitigating security 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

27. Phsychological acceptability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security functionality is easy to use and transparent
Indicator of magnitude risk in a year ALE = SLE * ARO
Access request by a subject to an object is mediated each time and every time.

28. Core Security Concept
Confidentiality - Integrity - Availability
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Still under development - aimsto address ISMS implementation guidance

29. Common best practices significant to Sofware Security
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
OWASP - ITIL
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 functionality is easy to use and transparent

30. ISO/IEC 27003
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Still under development - aimsto address ISMS implementation guidance
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

31. Annual Rate of Occurence (ARO)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Access request by a subject to an object is mediated each time and every time.
Number of incidents that can be expected in a year
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

32. Single Loss Expectancy (SLE)
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
estimate potential loss of a single incident: SLE = Asset value * EF(%)

33. ISO/IEC 21827:2008
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
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

34. Safeguards
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied to mitigate a threat before it materializes
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

35. Risk management process
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

36. Develop hack resilient software
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Security controls applied to mitigate a threat before it materializes

37. 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
Security controls applied to mitigate a threat before it materializes
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

38. Properties of secure software
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

39. PCI DSS
Predetermined number of user error allowed before recording it as a security violation
Authentication
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

40. NIST standards related to software security
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

41. Security Standards
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
Support policies at a granular and specific level - Can be characterized as internal and external
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

42. Security profile of a 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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Number of incidents that can be expected in a year

43. Economy of mechanism
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security functionality is easy to use and transparent
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

44. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

45. Authorization
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Authentication

46. ISO/IEC 15408
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 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
Number of incidents that can be expected in a year
Provides Common Criteria to evaluate IT security product

47. Authentication
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

48. Open design
Access request by a subject to an object is mediated each time and every time.
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

49. FIPS 197 (Advance Cryptographic standards - AES)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Secure applicatios running on secure hosts (systems) in a secure network
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

50. Compartmentalization
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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