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. ISO/IEC 27006:2007
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Support for accreditation and certification bodies that audit and certify ISMS
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Still under development - aimsto address ISMS implementation guidance

2. Accountability
Number of incidents that can be expected in a year
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
OWASP - ITIL
Security controls applied to mitigate a threat before it materializes

3. ISO/IEC 27005:2008
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
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Development guide - Code Review Guide - Testing Guide

5. Session Management
Support for accreditation and certification bodies that audit and certify ISMS
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of 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

6. FIPS 201
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Development guide - Code Review Guide - Testing Guide
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

7. Properties of secure software
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Technical - Management - Operational
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

8. Error and exception management
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Still under development - aimsto address ISMS implementation guidance
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

9. Risk management process
Technical - Management - Operational
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Indicator of magnitude risk in a year ALE = SLE * ARO

10. STRIDE
OWASP - ITIL
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

11. Security design principles
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Authentication

12. OWASP Top 10
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
Predetermined number of user error allowed before recording it as a security violation
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

13. Counter measures
Risk remains after the implementation of mitigating security controls
Protection against unauthorized information disclosure. It helps maintaining privacy
Authentication
Security controls applied after a threat has been materialized

14. Information Security Models
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

15. Security Policies

16. Access Matrix model

17. Examples of Security Standards
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
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

18. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Covers the necessary procedures and tools to validate software assurance

19. OCTAVE
Authentication
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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

20. Least common mechanism
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Design to mitigate any single source of complete compromise

21. After identification step is...
Authentication
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

22. Annual Rate of Occurence (ARO)
Covers the necessary procedures and tools to validate software assurance
Indicator of magnitude risk in a year ALE = SLE * ARO
Number of incidents that can be expected in a year
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. Clipping level
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Predetermined number of user error allowed before recording it as a security violation
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
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

24. Phsychological acceptability
Indicator of magnitude risk in a year ALE = SLE * ARO
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Security functionality is easy to use and transparent

25. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Development guide - Code Review Guide - Testing Guide
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

26. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Protection against unauthorized information disclosure. It helps maintaining privacy
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

27. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Protection against unauthorized information disclosure. It helps maintaining privacy

28. Single Loss Expectancy (SLE)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Covers the necessary procedures and tools to validate software assurance
estimate potential loss of a single incident: SLE = Asset value * EF(%)

29. Operation Controls
Confidentiality - Integrity - Availability
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

30. Popular guides developed by OWASP
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Development guide - Code Review Guide - Testing Guide
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

31. Security profile of a software
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

32. Integrity
Risk remains after the implementation of mitigating security controls
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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

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

34. Multifactor authentication
Development guide - Code Review Guide - Testing Guide
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security functionality is easy to use and transparent

35. 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
Development guide - Code Review Guide - Testing Guide
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

36. Technical Controls
Support policies at a granular and specific level - Can be characterized as internal and external
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

37. ISO/IEC 27003
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Still under development - aimsto address ISMS implementation guidance

38. Annual Loss Expectancy (ALE)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Access request by a subject to an object is mediated each time and every time.
Indicator of magnitude risk in a year ALE = SLE * ARO
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

39. Residual Risk
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
Risk remains after the implementation of mitigating security controls
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

40. OWASP development guide
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

41. OWASP Code Review Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
The likelihood that a threat can result into an incident. This is the overall risk of a system
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

42. Flaw Hypothesis Method (FHM)
Authentication
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

43. PCI DSS
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
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

44. Take-Grant Model
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

45. FIPS 197 (Advance Cryptographic standards - AES)
Security controls applied after a threat has been materialized
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

46. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security controls applied to mitigate a threat before it materializes
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
Development guide - Code Review Guide - Testing Guide

47. Total Risk
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Predetermined number of user error allowed before recording it as a security violation
Periodic publication by OWASP for top 10 Web application security vulnerabilites
The likelihood that a threat can result into an incident. This is the overall risk of a system

48. Exposure factor (EF)
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Security controls applied to mitigate a threat before it materializes
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

49. Single point failure
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Design to mitigate any single source of complete compromise
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

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