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. Multifactor authentication
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
Confidentiality - Integrity - Availability
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

2. Clipping level
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Design to mitigate any single source of complete compromise
Protection against unauthorized information disclosure. It helps maintaining privacy
Predetermined number of user error allowed before recording it as a security violation

3. Error and exception management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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
Security functionality is easy to use and transparent

4. General security concept
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

5. Configurations Parameters Management
Support policies at a granular and specific level - Can be characterized as internal and external
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

6. Core Security Concept
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
Confidentiality - Integrity - Availability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Provides Common Criteria to evaluate IT security product

7. After identification step is...
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
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
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

8. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

9. Phsychological acceptability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Security functionality is easy to use and transparent
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

10. Security Risk Management Discipline
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

11. ISO/IEC 15408
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
Provides Common Criteria to evaluate IT security product
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

12. OCTAVE
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

13. ISO/IEC 27005:2008
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

14. Security design principles
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
Predetermined number of user error allowed before recording it as a security violation
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
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

15. PCI DSS
Development guide - Code Review Guide - Testing Guide
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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

16. 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
Development guide - Code Review Guide - Testing Guide
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

17. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Design to mitigate any single source of complete compromise
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

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

19. ISO /IEC 27000:2009
Still under development - aimsto address ISMS implementation guidance
Secure applicatios running on secure hosts (systems) in a secure network
Protection against unauthorized information disclosure. It helps maintaining privacy
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

20. 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Design to mitigate any single source of complete compromise
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

21. 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
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
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied after a threat has been materialized

22. Security Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
The likelihood that a threat can result into an incident. This is the overall risk of a system
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

23. 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
Provides Common Criteria to evaluate IT security product
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

24. Security Standards
Authentication
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

25. OWASP Code Review Guide
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

26. Operation Controls
OWASP - ITIL
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

27. Annual Rate of Occurence (ARO)
Design to mitigate any single source of complete compromise
Number of incidents that can be expected in a year
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Protection against unauthorized information disclosure. It helps maintaining privacy

28. Examples of Security Standards
Support for accreditation and certification bodies that audit and certify ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Provides Common Criteria to evaluate IT security product

29. Implementation challenges
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Protection against unauthorized information disclosure. It helps maintaining privacy
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

30. Confidentiality
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Protection against unauthorized information disclosure. It helps maintaining privacy
Secure applicatios running on secure hosts (systems) in a secure network
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

31. Exposure factor (EF)
Security controls applied to mitigate a threat before it materializes
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
OWASP - ITIL

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

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

34. Popular guides developed by OWASP
Security controls applied to mitigate a threat before it materializes
Authentication
Development guide - Code Review Guide - Testing Guide
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. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
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
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

36. Availability
Risk remains after the implementation of mitigating security controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.

37. ISO/IEC 9216
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

38. Vulnerabilities repositories
Covers the necessary procedures and tools to validate software assurance
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Risk remains after the implementation of mitigating security controls

39. FIPS 201
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
Covers the necessary procedures and tools to validate software assurance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

40. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

41. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

42. Access Matrix model

43. Safeguards
Number of incidents that can be expected in a year
Still under development - aimsto address ISMS implementation guidance
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Security controls applied to mitigate a threat before it materializes

44. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Covers the necessary procedures and tools to validate software assurance
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

45. Flaw Hypothesis Method (FHM)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Still under development - aimsto address ISMS implementation guidance
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

46. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Security functionality is easy to use and transparent
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

47. Common best practices significant to Sofware Security
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
OWASP - ITIL
The likelihood that a threat can result into an incident. This is the overall risk of a system
Authentication

48. Vulnerability
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Indicator of magnitude risk in a year ALE = SLE * ARO

49. NIST standards related to software security
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 Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

50. Least common mechanism
Predetermined number of user error allowed before recording it as a security violation
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege