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. PCI DSS
Security functionality is easy to use and transparent
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

2. Management Controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

3. Threat
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

4. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

5. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

6. Vulnerabilities repositories
Confidentiality - Integrity - Availability
Predetermined number of user error allowed before recording it as a security violation
Covers the necessary procedures and tools to validate software assurance
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

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

8. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

9. Annual Rate of Occurence (ARO)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Number of incidents that can be expected in a year
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Authentication

10. Vulnerability
Confidentiality - Integrity - Availability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

11. Availability
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

12. Multifactor authentication
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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.

13. Access Matrix model

14. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
Protection against unauthorized information disclosure. It helps maintaining privacy
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
OWASP - ITIL

15. Information Security Models
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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 functionality is easy to use and transparent
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

16. Single Loss Expectancy (SLE)
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
Still under development - aimsto address ISMS implementation guidance
estimate potential loss of a single incident: SLE = Asset value * EF(%)

17. Authorization
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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 controls applied to mitigate a threat before it materializes
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

18. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
OWASP - ITIL
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

19. Take-Grant Model
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
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

20. Residual Risk
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
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 remains after the implementation of mitigating security 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

21. Core Security Concept
Development guide - Code Review Guide - Testing Guide
Confidentiality - Integrity - Availability
Support policies at a granular and specific level - Can be characterized as internal and external
The likelihood that a threat can result into an incident. This is the overall risk of a system

22. Security Standards
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Access request by a subject to an object is mediated each time and every time.

23. Counter measures
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Security controls applied after a threat has been materialized

24. Compartmentalization
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security controls applied after a threat has been materialized
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

25. Flaw Hypothesis Method (FHM)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

26. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

27. Configurations Parameters Management
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

28. OWASP development guide
Confidentiality - Integrity - Availability
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

29. Security Risk Management Discipline
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
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

30. Authentication
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Secure applicatios running on secure hosts (systems) in a secure network
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

31. Security Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

32. ISO/IEC 27001:2005
Risk remains after the implementation of mitigating security controls
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

33. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

34. Holistic Security in software
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Secure applicatios running on secure hosts (systems) in a secure network
Number of incidents that can be expected in a year
Risk remains after the implementation of mitigating security controls

35. Operation Controls
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

36. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

37. ISO /IEC 27000:2009
Risk remains after the implementation of mitigating security 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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

38. Risk management process
Protection against unauthorized information disclosure. It helps maintaining privacy
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

39. Properties of secure software
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

40. Technical Controls
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

41. Common best practices significant to Sofware Security
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
OWASP - ITIL
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Secure applicatios running on secure hosts (systems) in a secure network

42. Open design
Number of incidents that can be expected in a year
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 policies at a granular and specific level - Can be characterized as internal and external
Security controls applied to mitigate a threat before it materializes

43. Phsychological acceptability
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security functionality is easy to use and transparent
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

44. OCTAVE
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

45. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

46. Safeguards
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security controls applied to mitigate a threat before it materializes
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

47. FIPS140-2 (Security requirement for cryptographic modules)
Indicator of magnitude risk in a year ALE = SLE * ARO
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support policies at a granular and specific level - Can be characterized as internal and external
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

48. Session 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

49. STRIDE
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Authentication
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Indicator of magnitude risk in a year ALE = SLE * ARO

50. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Covers the necessary procedures and tools to validate software assurance
The likelihood that a threat can result into an incident. This is the overall risk of a system