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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Development guide - Code Review Guide - Testing Guide
Authentication

2. Configurations Parameters Management
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

3. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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 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
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

4. Single Loss Expectancy (SLE)
Confidentiality - Integrity - Availability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Technical - Management - Operational

5. NIST standards related to software security
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
Security controls applied after a threat has been materialized
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

6. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

7. ISO/IEC 27002:2005
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Number of incidents that can be expected in a year
Still under development - aimsto address ISMS implementation guidance
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

8. Session Management
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
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

9. Security Controls
Support policies at a granular and specific level - Can be characterized as internal and external
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

10. Error and exception management
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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. Common best practices significant to Sofware Security
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
OWASP - ITIL
Security controls applied after a threat has been materialized
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

12. Vulnerabilities repositories
Security controls applied to mitigate a threat before it materializes
Still under development - aimsto address ISMS implementation guidance
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

13. PCI DSS
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Covers the necessary procedures and tools to validate software assurance

14. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Support for accreditation and certification bodies that audit and certify 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

15. ISO/IEC 27003
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Still under development - aimsto address ISMS implementation guidance
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk remains after the implementation of mitigating security controls

16. Residual Risk
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Security functionality is easy to use and transparent
Risk remains after the implementation of mitigating security controls
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

17. Software security risk management methodologies
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
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

18. Annual Loss Expectancy (ALE)
Security controls applied after a threat has been materialized
Security controls applied to mitigate a threat before it materializes
Indicator of magnitude risk in a year ALE = SLE * ARO
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

19. Core Security Concept
Confidentiality - Integrity - Availability
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
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.

20. Examples of Security 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
Risk remains after the implementation of mitigating security controls
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

21. OWASP development guide
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Development guide - Code Review Guide - Testing Guide

22. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

23. Properties of secure software
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security controls applied to mitigate a threat before it materializes
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

24. Safeguards
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

25. Open design
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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
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

26. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

27. Develop hack resilient software
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

28. Exposure factor (EF)
Number of incidents that can be expected in a year
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

29. EALs levels
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

30. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
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
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

31. ISO/IEC 27006:2007
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Support for accreditation and certification bodies that audit and certify ISMS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

32. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

33. FIPS140-2 (Security requirement for cryptographic modules)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Technical - Management - Operational
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

34. OCTAVE
The likelihood that a threat can result into an incident. This is the overall risk of a system
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 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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

35. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Security controls applied after a threat has been materialized

36. Availability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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.
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
Security controls applied to mitigate a threat before it materializes

37. Annual Rate of Occurence (ARO)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Number of incidents that can be expected in a year
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

38. General security concept
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

39. Phsychological acceptability
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
Security functionality is easy to use and transparent
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

40. OWASP Top 10
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Covers the necessary procedures and tools to validate software assurance
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

41. ISO/IEC 21827:2008
Still under development - aimsto address ISMS implementation guidance
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

42. Management Controls
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Support policies at a granular and specific level - Can be characterized as internal and external
estimate potential loss of a single incident: SLE = Asset value * EF(%)

43. Counter measures
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Security controls applied after a threat has been materialized
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

44. Security design principles
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Risk remains after the implementation of mitigating security controls

45. ISO /IEC 27000:2009
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

46. After identification step is...
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support for accreditation and certification bodies that audit and certify ISMS
Authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

47. OWASP Code Review Guide
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Confidentiality - Integrity - Availability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk remains after the implementation of mitigating security controls

48. Security Risk Management Discipline
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

49. Challenges in implementing auditing/logging
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Indicator of magnitude risk in a year ALE = SLE * ARO
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Technical - Management - Operational

50. Threat
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual