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. Phsychological acceptability
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security functionality is easy to use and transparent
Provides Common Criteria to evaluate IT security product

2. Security design principles
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
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
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
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

3. Open design
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

4. Annual Rate of Occurence (ARO)
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Number of incidents that can be expected in a year
Authentication
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

5. Benefits of coding standards
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

6. Security Standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Support policies at a granular and specific level - Can be characterized as internal and external
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

7. Single Loss Expectancy (SLE)
Number of incidents that can be expected in a year
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

8. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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

9. Complete mediation
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.
Security functionality is easy to use and transparent
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

10. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Provides Common Criteria to evaluate IT security product
Still under development - aimsto address ISMS implementation guidance
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

11. Authorization
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Technical - Management - Operational

12. Auditing
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
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

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

14. Single point failure
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
Confidentiality - Integrity - Availability
Design to mitigate any single source of complete compromise
Support for accreditation and certification bodies that audit and certify ISMS

15. NIST standards related to software security
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

16. Vulnerabilities repositories
Confidentiality - Integrity - Availability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Predetermined number of user error allowed before recording it as a security violation
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

17. Vulnerability
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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 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

18. After identification step is...
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
Authentication
Security functionality is easy to use and transparent
Still under development - aimsto address ISMS implementation guidance

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

20. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

21. STRIDE
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

22. Least privilege
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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

23. ISO /IEC 27000:2009
Covers the necessary procedures and tools to validate software assurance
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

24. Compartmentalization
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

25. Take-Grant Model
OWASP - ITIL
Technical - Management - Operational
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

26. OWASP Top 10
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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.

27. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

28. Security 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
Security controls applied after a threat has been materialized
Indicator of magnitude risk in a year ALE = SLE * ARO
Technical - Management - Operational

29. Integrity
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
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.
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

30. OWASP Code Review Guide
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

31. Security Risk Management Discipline
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.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

32. Properties of secure software
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

33. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Development guide - Code Review Guide - Testing Guide
Number of incidents that can be expected in a year
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

34. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Provides Common Criteria to evaluate IT security product

35. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

36. Holistic Security in software
Design to mitigate any single source of complete compromise
Development guide - Code Review Guide - Testing Guide
Secure applicatios running on secure hosts (systems) in a secure network
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

37. General security concept
Predetermined number of user error allowed before recording it as a security violation
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

38. OWASP development guide
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Development guide - Code Review Guide - Testing Guide
Covers the necessary procedures and tools to validate software assurance

39. 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
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
Access request by a subject to an object is mediated each time and every time.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

40. FIPS 197 (Advance Cryptographic standards - AES)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Technical - Management - Operational

41. Flaw Hypothesis Method (FHM)
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

42. Software security risk management methodologies
Risk remains after the implementation of mitigating security controls
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
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

43. Common best practices significant to Sofware 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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Technical - Management - Operational
OWASP - ITIL

44. Security profile of a software
Support for accreditation and certification bodies that audit and certify ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Secure applicatios running on secure hosts (systems) in a secure network
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

45. Develop hack resilient software
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Indicator of magnitude risk in a year ALE = SLE * ARO
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

46. Threat
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

47. ISO/IEC 9216
Covers the necessary procedures and tools to validate software assurance
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

48. Accountability
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Development guide - Code Review Guide - Testing Guide

49. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

50. Exposure factor (EF)
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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