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. After identification step is...
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

2. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
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
Provides Common Criteria to evaluate IT security product

3. Compartmentalization
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

4. ISO/IEC 27002:2005
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

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

6. Categories of controls
OWASP - ITIL
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Risk remains after the implementation of mitigating security controls
Technical - Management - Operational

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

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

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

10. Session Management
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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 policies at a granular and specific level - Can be characterized as internal and external

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

12. DREAD
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

13. 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
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)
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

14. Vulnerabilities repositories
Number of incidents that can be expected in a year
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

15. Core Security Concept
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Secure applicatios running on secure hosts (systems) in a secure network
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Confidentiality - Integrity - Availability

16. OCTAVE
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
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
Risk remains after the implementation of mitigating security controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

17. Common best practices significant to Sofware Security
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
OWASP - ITIL
Still under development - aimsto address ISMS implementation guidance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

18. FIPS140-2 (Security requirement for cryptographic modules)
Development guide - Code Review Guide - Testing Guide
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on 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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

19. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Periodic publication by OWASP for top 10 Web application security vulnerabilites

20. Technical Controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Indicator of magnitude risk in a year ALE = SLE * ARO
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

21. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

22. Security design principles
Technical - Management - Operational
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Provides Common Criteria to evaluate IT security product
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

23. Clipping level
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Predetermined number of user error allowed before recording it as a security violation

24. Access Matrix model

25. Confidentiality
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
estimate potential loss of a single incident: SLE = Asset value * EF(%)

26. OWASP Top 10
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Number of incidents that can be expected in a year
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

27. FIPS 197 (Advance Cryptographic standards - AES)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

28. Complete mediation
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Access request by a subject to an object is mediated each time and every time.

29. Risk management process
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

30. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

31. STRIDE
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
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
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

32. Single point failure
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
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
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
Design to mitigate any single source of complete compromise

33. Take-Grant Model
Development guide - Code Review Guide - Testing Guide
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

34. Benefits of coding standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Risk remains after the implementation of mitigating security controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

35. 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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system

36. General security concept
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
Design to mitigate any single source of complete compromise
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

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

38. Residual Risk
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Risk remains after the implementation of mitigating security controls

39. Authentication
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

40. Single Loss Expectancy (SLE)
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
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
Covers the necessary procedures and tools to validate software assurance
estimate potential loss of a single incident: SLE = Asset value * EF(%)

41. 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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

42. 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
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
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

43. Open design
Authentication
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
Access request by a subject to an object is mediated each time and every time.
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

44. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

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

46. Annual Loss Expectancy (ALE)
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Support for accreditation and certification bodies that audit and certify ISMS
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

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

48. Operation Controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

49. Vulnerability
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

50. Counter measures
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Security controls applied after a threat has been materialized