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 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

2. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Still under development - aimsto address ISMS implementation guidance
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
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

3. Auditing
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
Predetermined number of user error allowed before recording it as a security violation
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

4. 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
OWASP - ITIL
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
Protection against unauthorized information disclosure. It helps maintaining privacy

5. Software security risk management methodologies
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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

6. Threat
Development guide - Code Review Guide - Testing Guide
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

7. Information Security Models
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
OWASP - ITIL
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
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. Security 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
Support policies at a granular and specific level - Can be characterized as internal and external
Provides Common Criteria to evaluate IT security product
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

9. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

10. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
estimate potential loss of a single incident: SLE = Asset value * EF(%)

11. 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
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Security functionality is easy to use and transparent

12. 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
Design to mitigate any single source of complete compromise
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

13. Compartmentalization
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

14. Safeguards
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
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

15. 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
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
Number of incidents that can be expected in a year
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.

16. EALs levels
Development guide - Code Review Guide - Testing Guide
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

17. STRIDE
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Still under development - aimsto address ISMS implementation guidance
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
Design to mitigate any single source of complete compromise

18. Vulnerabilities repositories
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

19. Integrity
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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

20. Technical 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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

21. Develop hack resilient software
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Support for accreditation and certification bodies that audit and certify ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

22. Single Loss Expectancy (SLE)
Support policies at a granular and specific level - Can be characterized as internal and external
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
estimate potential loss of a single incident: SLE = Asset value * EF(%)

23. 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 controls applied after a threat has been materialized
Protection against unauthorized information disclosure. It helps maintaining privacy
Indicator of magnitude risk in a year ALE = SLE * ARO

24. Implementation challenges
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
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

25. FIPS140-2 (Security requirement for cryptographic modules)
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
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
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

26. After identification step is...
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Authentication

27. Multifactor authentication
Still under development - aimsto address ISMS implementation guidance
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

28. NIST standards related to software security
Development guide - Code Review Guide - Testing Guide
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

29. Core Security Concept
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Confidentiality - Integrity - Availability

30. Error and exception management
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

31. ISO/IEC 27001:2005
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Number of incidents that can be expected in a year
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Still under development - aimsto address ISMS implementation guidance

32. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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

33. Configurations Parameters Management
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Secure applicatios running on secure hosts (systems) in a secure network
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

34. Security profile of a software
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Covers the necessary procedures and tools to validate software assurance
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

35. Economy of mechanism
Security functionality is easy to use and transparent
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Covers the necessary procedures and tools to validate software assurance

36. Phsychological acceptability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Design to mitigate any single source of complete compromise
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
Security functionality is easy to use and transparent

37. Properties of secure software
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

38. FIPS 201
Predetermined number of user error allowed before recording it as a security violation
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

39. Access Matrix model

40. ISO /IEC 27000:2009
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

41. ISO/IEC 9216
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

42. ISO/IEC 27002:2005
Secure applicatios running on secure hosts (systems) in a secure network
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

43. Security Risk Management Discipline
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

44. Clipping level
Confidentiality - Integrity - Availability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Predetermined number of user error allowed before recording it as a security violation
Support policies at a granular and specific level - Can be characterized as internal and external

45. Categories of controls
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
Access request by a subject to an object is mediated each time and every time.
Technical - Management - Operational

46. Least common mechanism
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

47. OWASP Top 10
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Number of incidents that can be expected in a year
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

48. ISO/IEC 27005:2008
Technical - Management - Operational
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
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

49. Flaw Hypothesis Method (FHM)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

50. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
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
Design to mitigate any single source of complete compromise