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
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.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security functionality is easy to use and transparent
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

2. ISO/IEC 27005:2008
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

3. ISO /IEC 27000:2009
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

4. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Support policies at a granular and specific level - Can be characterized as internal and external
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

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

6. Least common mechanism
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

7. STRIDE
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

8. Security design principles
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
Confidentiality - Integrity - Availability
OWASP - ITIL
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

9. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Confidentiality - Integrity - Availability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

10. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

11. Residual Risk
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
Risk remains after the implementation of mitigating security controls
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

12. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Confidentiality - Integrity - Availability
Number of incidents that can be expected in a year
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. Implementation challenges
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
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

14. Properties of secure software
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
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
The likelihood that a threat can result into an incident. This is the overall risk of a system
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

15. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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(%)

16. ISO/IEC 27002:2005
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

17. Availability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

18. After identification step is...
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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. Flaw Hypothesis Method (FHM)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
OWASP - ITIL
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

20. Security profile of a software
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

21. FIPS 197 (Advance Cryptographic standards - AES)
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.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

22. Least privilege
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
Access request by a subject to an object is mediated each time and every time.
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

23. Software security risk management methodologies
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Security 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

24. Session Management
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
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
Confidentiality - Integrity - Availability

25. OWASP Code Review Guide
Secure applicatios running on secure hosts (systems) in a secure network
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

26. Challenges in implementing auditing/logging
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

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

28. 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:
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

29. Economy of mechanism
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

30. DREAD
Development guide - Code Review Guide - Testing Guide
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied after a threat has been materialized

31. Vulnerability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Support policies at a granular and specific level - Can be characterized as internal and external

32. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Support for accreditation and certification bodies that audit and certify ISMS
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
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

33. Annual Rate of Occurence (ARO)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Number of incidents that can be expected in a year

34. Core Security Concept
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Confidentiality - Integrity - Availability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

35. Operation Controls
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

36. ISO/IEC 9216
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.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

37. Non Repudiation
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

38. Annual Loss Expectancy (ALE)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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

39. 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Indicator of magnitude risk in a year ALE = SLE * ARO
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

40. Clipping level
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Predetermined number of user error allowed before recording it as a security violation

41. Open design
Secure applicatios running on secure hosts (systems) in a secure network
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Access request by a subject to an object is mediated each time and every time.
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software

42. Benefits of coding standards
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security controls applied to mitigate a threat before it materializes

43. Error and exception management
Support policies at a granular and specific level - Can be characterized as internal and external
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

44. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

45. 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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

46. Security Standards
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
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
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.

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

48. Popular guides developed by OWASP
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Confidentiality - Integrity - Availability
Development guide - Code Review Guide - Testing Guide

49. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Technical - Management - Operational
Confidentiality - Integrity - Availability
Periodic publication by OWASP for top 10 Web application security vulnerabilites

50. Security Controls
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
Security controls applied after a threat has been materialized
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
Confidentiality - Integrity - Availability