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

2. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Risk remains after the implementation of mitigating security controls
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

3. 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
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
Design to mitigate any single source of complete compromise
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

4. OWASP Code Review Guide
OWASP - ITIL
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

5. ISO/IEC 27001:2005
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

6. Residual Risk
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Risk remains after the implementation of mitigating security controls
Protection against unauthorized information disclosure. It helps maintaining privacy

7. STRIDE
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Secure applicatios running on secure hosts (systems) in a secure network
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

8. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

9. Clipping level
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Predetermined number of user error allowed before recording it as a security violation
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

10. ISO/IEC 27005:2008
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

11. Single Loss Expectancy (SLE)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Indicator of magnitude risk in a year ALE = SLE * ARO

12. 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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

13. ISO/IEC 21827:2008
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
Number of incidents that can be expected in a year
Access request by a subject to an object is mediated each time and every time.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

14. Safeguards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Security controls applied to mitigate a threat before it materializes
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

15. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Authentication
Security controls applied after a threat has been materialized
Support policies at a granular and specific level - Can be characterized as internal and external

16. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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
Support for accreditation and certification bodies that audit and certify ISMS

17. Information Security Models
Design to mitigate any single source of complete compromise
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

18. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

19. Common best practices significant to Sofware Security
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
OWASP - ITIL
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

20. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

21. EALs levels
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
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.
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

22. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Design to mitigate any single source of complete compromise
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

23. Auditing
Still under development - aimsto address ISMS implementation guidance
OWASP - ITIL
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

24. Holistic Security in software
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Secure applicatios running on secure hosts (systems) in a secure network
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

25. Single point failure
Predetermined number of user error allowed before recording it as a security violation
Design to mitigate any single source of complete compromise
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
OWASP - ITIL

26. PCI DSS
Support for accreditation and certification bodies that audit and certify ISMS
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
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.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

27. OCTAVE
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Predetermined number of user error allowed before recording it as a security violation
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

28. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Development guide - Code Review Guide - Testing Guide

29. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

30. Complete mediation
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Still under development - aimsto address ISMS implementation guidance
Access request by a subject to an object is mediated each time and every time.
Technical - Management - Operational

31. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Secure applicatios running on secure hosts (systems) in a secure network
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

32. FIPS 201
Security functionality is easy to use and transparent
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
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

33. 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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 likelihood that a threat can result into an incident. This is the overall risk of a system

34. Technical Controls
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

35. Security design principles
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Secure applicatios running on secure hosts (systems) in a secure network

36. 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 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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Access request by a subject to an object is mediated each time and every time.

37. Configurations Parameters Management
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Number of incidents that can be expected in a year
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

38. DREAD
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

39. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Access request by a subject to an object is mediated each time and every time.
Support policies at a granular and specific level - Can be characterized as internal and external
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

40. Phsychological acceptability
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 functionality is easy to use and transparent
Support policies at a granular and specific level - Can be characterized as internal and external
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

41. After identification step is...
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Authentication
OWASP - ITIL
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

42. ISO/IEC 15408
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Provides Common Criteria to evaluate IT security product
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

43. Security Risk Management Discipline
Support policies at a granular and specific level - Can be characterized as internal and external
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.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

44. OWASP testing guide
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Covers the necessary procedures and tools to validate software assurance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

45. Non Repudiation
Authentication
Secure applicatios running on secure hosts (systems) in a secure network
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

46. Error and exception management
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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

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

48. Accountability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Number of incidents that can be expected in a year

49. Authorization
Secure applicatios running on secure hosts (systems) in a secure network
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

50. Compartmentalization
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Design to mitigate any single source of complete compromise
Successful completion of a critical task is dependent on 2 or more conditions that need to be met