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. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

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

3. Examples of Security Standards
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

4. PCI DSS
Support policies at a granular and specific level - Can be characterized as internal and external
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
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.
Still under development - aimsto address ISMS implementation guidance

5. ISO/IEC 21827:2008
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

6. Annual Rate of Occurence (ARO)
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Number of incidents that can be expected in a year
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

7. Counter measures
Security controls applied to mitigate a threat before it materializes
Support policies at a granular and specific level - Can be characterized as internal and external
Security controls applied after a threat has been materialized
Access request by a subject to an object is mediated each time and every time.

8. Auditing
Confidentiality - Integrity - Availability
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
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

9. Security profile of a software
Development guide - Code Review Guide - Testing Guide
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
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

10. Risk management process
OWASP - ITIL
The likelihood that a threat can result into an incident. This is the overall risk of a system
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

11. Operation Controls
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

12. Error and exception management
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Development guide - Code Review Guide - Testing Guide
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

13. Phsychological acceptability
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
Security functionality is easy to use and transparent
OWASP - ITIL
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

14. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Covers the necessary procedures and tools to validate software assurance

15. Multifactor authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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)

16. ISO/IEC 27005:2008
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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:
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

17. Integrity
Development guide - Code Review Guide - Testing Guide
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
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

18. Information Security Models
Security functionality is easy to use and transparent
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

19. 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Development guide - Code Review Guide - Testing Guide

20. Benefits of coding standards
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

21. Security Risk Management Discipline
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
OWASP - ITIL
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

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

23. Economy of mechanism
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

24. OWASP Top 10
Authentication
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Periodic publication by OWASP for top 10 Web application security vulnerabilites
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

25. Complete mediation
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Indicator of magnitude risk in a year ALE = SLE * ARO

26. Availability
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.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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. Popular guides developed by OWASP
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Development guide - Code Review Guide - Testing Guide
Risk remains after the implementation of mitigating security 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

28. Clipping level
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Predetermined number of user error allowed before recording it as a security violation
Development guide - Code Review Guide - Testing Guide
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

29. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

30. OWASP testing guide
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Covers the necessary procedures and tools to validate software assurance
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

31. Annual Loss Expectancy (ALE)
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.
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Indicator of magnitude risk in a year ALE = SLE * ARO

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

33. Management Controls
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

34. ISO/IEC 15408
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Provides Common Criteria to evaluate IT security product
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

35. Implementation challenges
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Provides Common Criteria to evaluate IT security product
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

36. Categories of controls
Technical - Management - Operational
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
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
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

37. Access Matrix model

38. Configurations Parameters Management
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Support policies at a granular and specific level - Can be characterized as internal and external
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Access 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

39. ISO/IEC 9216
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
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
Development guide - Code Review Guide - Testing Guide

40. Single point failure
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Technical - Management - Operational
Design to mitigate any single source of complete compromise

41. NIST standards related to software 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
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)
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

42. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

43. FIPS 201
Design to mitigate any single source of complete compromise
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

44. Common best practices significant to Sofware Security
Development guide - Code Review Guide - Testing Guide
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
Access request by a subject to an object is mediated each time and every time.
OWASP - ITIL

45. After identification step is...
Indicator of magnitude risk in a year ALE = SLE * ARO
Authentication
Support policies at a granular and specific level - Can be characterized as internal and external
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

46. 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
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

47. Properties of secure software
Support policies at a granular and specific level - Can be characterized as internal and external
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
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

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

49. Security Policies

50. Single Loss Expectancy (SLE)
OWASP - ITIL
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
estimate potential loss of a single incident: SLE = Asset value * EF(%)