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. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Security controls applied after a threat has been materialized

2. OWASP Code Review Guide
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

3. OCTAVE
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
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
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
Covers the necessary procedures and tools to validate software assurance

4. Clipping level
Indicator of magnitude risk in a year ALE = SLE * ARO
Predetermined number of user error allowed before recording it as a security violation
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

5. Common best practices significant to Sofware Security
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

6. FIPS 201
Technical - Management - Operational
Secure applicatios running on secure hosts (systems) in a secure network
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

7. Compartmentalization
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security functionality is easy to use and transparent
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Number of incidents that can be expected in a year

8. Accountability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
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

9. Configurations Parameters Management
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
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 controls applied after a threat has been materialized

10. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Number of incidents that can be expected in a year
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

11. Authentication
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

12. Holistic Security in software
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Secure applicatios running on secure hosts (systems) in a secure network

13. Total Risk
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system
Covers the necessary procedures and tools to validate software assurance
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

14. Popular guides developed by OWASP
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Development guide - Code Review Guide - Testing Guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

15. Core Security Concept
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Confidentiality - Integrity - Availability
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

16. Least privilege
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Predetermined number of user error allowed before recording it as a security violation

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

18. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Number of incidents that can be expected in a year
Development guide - Code Review Guide - Testing Guide
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

19. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Design to mitigate any single source of complete compromise
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

20. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
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
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. ISO/IEC 27002:2005
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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 to mitigate a threat before it materializes
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

22. EALs levels
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Support for accreditation and certification bodies that audit and certify ISMS

23. Phsychological acceptability
Security functionality is easy to use and transparent
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

24. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

25. Multifactor authentication
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

26. Residual Risk
Risk remains after the implementation of mitigating security controls
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

27. Technical Controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

28. Management Controls
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
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: 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

29. 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
Technical - Management - Operational
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

30. OWASP testing guide
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
Still under development - aimsto address ISMS implementation guidance
Covers the necessary procedures and tools to validate software assurance
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

31. Develop hack resilient 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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

32. Auditing
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
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
Covers the necessary procedures and tools to validate software assurance
Technical - Management - Operational

33. Vulnerability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
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

34. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Development guide - Code Review Guide - Testing Guide
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

35. Authorization
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Risk remains after the implementation of mitigating security controls

36. Access Matrix model

37. Security Controls
Security controls applied after a threat has been materialized
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 the architecture and technical requirements for a common identified standard for federal employee and contractors
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

38. Safeguards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Security controls applied to mitigate a threat before it materializes

39. Security Policies

40. Single point failure
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Development guide - Code Review Guide - Testing Guide
Design to mitigate any single source of complete compromise
Security controls applied after a threat has been materialized

41. Session Management
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

42. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Support policies at a granular and specific level - Can be characterized as internal and external
Still under development - aimsto address ISMS implementation guidance

43. Challenges in implementing auditing/logging
Security controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls
Secure applicatios running on secure hosts (systems) in a secure network
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

44. Exposure factor (EF)
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
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

45. ISO /IEC 27000:2009
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
Secure applicatios running on secure hosts (systems) in a secure network
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
Security functionality is easy to use and transparent

46. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Still under development - aimsto address ISMS implementation guidance
OWASP - ITIL

47. ISO/IEC 27001:2005
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 requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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.
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

48. FIPS140-2 (Security requirement for cryptographic modules)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Still under development - aimsto address ISMS implementation guidance

49. Integrity
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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

50. Error and exception management
Access request by a subject to an object is mediated each time and every time.
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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