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

2. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Technical - Management - Operational

3. After identification step is...
Authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Security controls applied after a threat has been materialized
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

4. Implementation challenges
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
OWASP - ITIL
Support policies at a granular and specific level - Can be characterized as internal and external

5. Safeguards
Security controls applied to mitigate a threat before it materializes
OWASP - ITIL
Periodic publication by OWASP for top 10 Web application security vulnerabilites
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

6. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

7. Develop hack resilient 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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

8. Vulnerability
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
Access request by a subject to an object is mediated each time and every time.
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

9. OWASP Code Review Guide
Security controls applied after a threat has been materialized
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Confidentiality - Integrity - Availability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

10. Common best practices significant to Sofware Security
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
OWASP - ITIL
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

11. Categories of controls
Provides Common Criteria to evaluate IT security product
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Technical - Management - Operational

12. Session Management
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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

13. Properties of secure software
Confidentiality - Integrity - Availability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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

14. Security profile of a software
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Technical - Management - Operational
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

15. Open design
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Authentication

16. Security design principles
OWASP - ITIL
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

17. Annual Rate of Occurence (ARO)
The likelihood that a threat can result into an incident. This is the overall risk of a system
Number of incidents that can be expected in a year
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

18. OWASP Top 10
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Design to mitigate any single source of complete compromise

19. Economy of mechanism
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

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

21. Information Security Models
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Support policies at a granular and specific level - Can be characterized as internal and external

22. PCI DSS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Confidentiality - Integrity - Availability
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

23. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

24. Least privilege
Security controls applied after a threat has been materialized
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

25. ISO/IEC 27002:2005
Indicator of magnitude risk in a year ALE = SLE * ARO
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

26. Security Standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support policies at a granular and specific level - Can be characterized as internal and external

27. Non Repudiation
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
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.
Number of incidents that can be expected in a year
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

28. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

29. ISO /IEC 27000:2009
Number of incidents that can be expected in a year
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 requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

30. ISO/IEC 21827:2008
Development guide - Code Review Guide - Testing Guide
Predetermined number of user error allowed before recording it as a security violation
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

31. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Predetermined number of user error allowed before recording it as a security violation

32. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

33. Clipping level
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
Predetermined number of user error allowed before recording it as a security violation
Security controls applied to mitigate a threat before it materializes
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

34. FIPS140-2 (Security requirement for cryptographic modules)
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 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
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
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

35. Popular guides developed by OWASP
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Development guide - Code Review Guide - Testing Guide

36. Multifactor authentication
Technical - Management - Operational
Predetermined number of user error allowed before recording it as a security violation
Number of incidents that can be expected in a year
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

37. Access Matrix model

38. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

39. Auditing
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Risk remains after the implementation of mitigating security controls
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
Indicator of magnitude risk in a year ALE = SLE * ARO

40. OCTAVE
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

41. Challenges in implementing auditing/logging
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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. Residual Risk
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
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 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
Risk remains after the implementation of mitigating security controls

43. ISO/IEC 9216
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Provides Common Criteria to evaluate IT security product
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

44. Phsychological acceptability
Security functionality is easy to use and transparent
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Predetermined number of user error allowed before recording it as a security violation
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

45. Examples of Security Standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

46. Total Risk
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Access request by a subject to an object is mediated each time and every time.
The likelihood that a threat can result into an incident. This is the overall risk of a system

47. Integrity
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

48. Benefits of coding standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

49. Error and exception management
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

50. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Periodic publication by OWASP for top 10 Web application security vulnerabilites
The likelihood that a threat can result into an incident. This is the overall risk of a system
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA