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 27002:2005
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
Still under development - aimsto address ISMS implementation guidance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

2. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

3. Session Management
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Design to mitigate any single source of complete compromise
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

4. Security Controls
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Indicator of magnitude risk in a year ALE = SLE * ARO
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

5. Software security risk management methodologies
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

6. Complete mediation
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Access request by a subject to an object is mediated each time and every time.

7. 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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

8. Auditing
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

9. Compartmentalization
Still under development - aimsto address ISMS implementation guidance
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
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

10. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Security controls applied after a threat has been materialized
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

11. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

12. Single Loss Expectancy (SLE)
Protection against unauthorized information disclosure. It helps maintaining privacy
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
estimate potential loss of a single incident: SLE = Asset value * EF(%)

13. Configurations Parameters Management
Covers the necessary procedures and tools to validate software assurance
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
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

14. After identification step is...
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Authentication

15. Operation Controls
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

16. Common best practices significant to Sofware Security
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
OWASP - ITIL
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 functionality is easy to use and transparent

17. Open design
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

18. Accountability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
The likelihood that a threat can result into an incident. This is the overall risk of a system
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

19. Least privilege
Indicator of magnitude risk in a year ALE = SLE * ARO
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Risk remains after the implementation of mitigating security controls

20. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Covers the necessary procedures and tools to validate software assurance
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

21. Availability
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
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
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
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.

22. OWASP development guide
Authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

23. EALs levels
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

24. Multifactor authentication
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Authentication
Protection against unauthorized information disclosure. It helps maintaining privacy
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

25. Integrity
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
The likelihood that a threat can result into an incident. This is the overall risk of a system
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. 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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

27. Access Matrix model

28. FIPS 201
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security controls applied after a threat has been materialized

29. Vulnerabilities repositories
Protection against unauthorized information disclosure. It helps maintaining privacy
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

30. Phsychological acceptability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Security functionality is easy to use and transparent

31. FIPS140-2 (Security requirement for cryptographic modules)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Still under development - aimsto address ISMS implementation guidance
Predetermined number of user error allowed before recording it as a security violation

32. Counter measures
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
Risk remains after the implementation of mitigating security controls
Security controls applied after a threat has been materialized
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

33. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Covers the necessary procedures and tools to validate software assurance
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

34. Non Repudiation
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
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
Access request by a subject to an object is mediated each time and every time.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

35. ISO/IEC 21827:2008
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:
Security controls applied after a threat has been materialized
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

36. DREAD
Predetermined number of user error allowed before recording it as a security violation
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Covers the necessary procedures and tools to validate software assurance
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

37. 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
Support for accreditation and certification bodies that audit and certify ISMS
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
Still under development - aimsto address ISMS implementation guidance

38. Security Policies

39. Clipping level
Predetermined number of user error allowed before recording it as a security violation
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 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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

40. General security concept
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
Predetermined number of user error allowed before recording it as a security violation
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Protection against unauthorized information disclosure. It helps maintaining privacy

41. ISO /IEC 27000:2009
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

42. FIPS 197 (Advance Cryptographic standards - AES)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

43. Technical Controls
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

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

45. Information Security Models
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

46. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

47. OWASP Top 10
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
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Periodic publication by OWASP for top 10 Web application security vulnerabilites

48. Authentication
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

49. Risk management process
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

50. Exposure factor (EF)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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