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. Annual Loss Expectancy (ALE)
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

2. Core Security Concept
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
Still under development - aimsto address ISMS implementation guidance
Confidentiality - Integrity - Availability
Design to mitigate any single source of complete compromise

3. OWASP Code Review Guide
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Predetermined number of user error allowed before recording it as a security violation
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

4. Single point failure
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Design to mitigate any single source of complete compromise
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

5. 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
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
Secure applicatios running on secure hosts (systems) in a secure network
Security functionality is easy to use and transparent

6. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

7. Common best practices significant to Sofware Security
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
OWASP - ITIL
Technical - Management - Operational

8. Availability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

9. Phsychological acceptability
Security functionality is easy to use and transparent
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
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.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

10. FIPS 201
Risk remains after the implementation of mitigating security controls
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Secure applicatios running on secure hosts (systems) in a secure network

11. Configurations Parameters Management
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network

12. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Development guide - Code Review Guide - Testing Guide
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

13. Economy of mechanism
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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

14. OWASP Top 10
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security controls applied to mitigate a threat before it materializes
Access request by a subject to an object is mediated each time and every time.

15. Counter measures
Risk remains after the implementation of mitigating security controls
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
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
Security controls applied after a threat has been materialized

16. PCI DSS
Secure applicatios running on secure hosts (systems) in a secure network
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

17. Authorization
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security controls applied after a threat has been materialized
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

18. Threat
Security controls applied after a threat has been materialized
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

19. Vulnerability
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
OWASP - ITIL
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

20. Security Policies

21. ISO/IEC 15408
Security functionality is easy to use and transparent
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Provides Common Criteria to evaluate IT security product

22. Compartmentalization
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

23. Total Risk
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

24. Technical Controls
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Support for accreditation and certification bodies that audit and certify ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

25. Clipping level
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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 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
Predetermined number of user error allowed before recording it as a security violation

26. Develop hack resilient software
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

27. Integrity
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Confidentiality - Integrity - Availability
Predetermined number of user error allowed before recording it as a security violation
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

28. Information Security Models
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

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

30. EALs levels
Security controls applied to mitigate a threat before it materializes
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

31. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Risk remains after the implementation of mitigating security controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

32. Security profile of a software
Security controls applied to mitigate a threat before it materializes
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
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

33. Properties of secure software
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Support policies at a granular and specific level - Can be characterized as internal and external

34. General security concept
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

35. OCTAVE
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
Development guide - Code Review Guide - Testing Guide
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

36. Error and exception management
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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
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.

37. ISO/IEC 27003
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Still under development - aimsto address ISMS implementation guidance
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

38. Least privilege
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Number of incidents that can be expected in a year

39. Holistic Security in software
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Access request by a subject to an object is mediated each time and every time.
Secure applicatios running on secure hosts (systems) in a secure network
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

40. Least common mechanism
Provides Common Criteria to evaluate IT security product
Support for accreditation and certification bodies that audit and certify ISMS
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

41. Single Loss Expectancy (SLE)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
estimate potential loss of a single incident: SLE = Asset value * EF(%)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

42. Operation Controls
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

43. DREAD
Covers the necessary procedures and tools to validate software assurance
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
Support policies at a granular and specific level - Can be characterized as internal and external
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

44. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Design to mitigate any single source of complete compromise

45. Security Standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Support policies at a granular and specific level - Can be characterized as internal and external

46. ISO/IEC 27005:2008
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Provides Common Criteria to evaluate IT security product

47. Safeguards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security controls applied to mitigate a threat before it materializes
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
Technical - Management - Operational

48. Access Matrix model

49. Categories of controls
Technical - Management - Operational
Covers the necessary procedures and tools to validate software assurance
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
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

50. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Number of incidents that can be expected in a year
Indicator of magnitude risk in a year ALE = SLE * ARO
Still under development - aimsto address ISMS implementation guidance