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. Examples of Security Standards
Support for accreditation and certification bodies that audit and certify ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

2. Take-Grant 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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Risk remains after the implementation of mitigating security controls

3. General security concept
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

4. Annual Loss Expectancy (ALE)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Support policies at a granular and specific level - Can be characterized as internal and external
Number of incidents that can be expected in a year
Indicator of magnitude risk in a year ALE = SLE * ARO

5. Technical Controls
Security controls applied after a threat has been materialized
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
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.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

6. Holistic Security in software
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
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
Secure applicatios running on secure hosts (systems) in a secure network

7. Vulnerabilities repositories
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

8. Properties of secure software
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

9. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

10. Single point failure
Access request by a subject to an object is mediated each time and every time.
Design to mitigate any single source of complete compromise
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
Development guide - Code Review Guide - Testing Guide

11. Non Repudiation
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
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
Authentication
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

12. Threat
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
Design to mitigate any single source of complete compromise
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

13. Vulnerability
Predetermined number of user error allowed before recording it as a security violation
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

14. Confidentiality
Authentication
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Protection against unauthorized information disclosure. It helps maintaining privacy
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

15. Economy of mechanism
Security controls applied to mitigate a threat before it materializes
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

16. PCI DSS
Secure applicatios running on secure hosts (systems) in a secure network
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
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
Design to mitigate any single source of complete compromise

17. Benefits of coding standards
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Support policies at a granular and specific level - Can be characterized as internal and external

18. Integrity
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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. Categories of controls
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Technical - Management - Operational
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

20. Challenges in implementing auditing/logging
Technical - Management - Operational
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

21. Single Loss Expectancy (SLE)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The likelihood that a threat can result into an incident. This is the overall risk of a system
estimate potential loss of a single incident: SLE = Asset value * EF(%)

22. Security Risk Management Discipline
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

23. Configurations Parameters Management
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
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
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

24. Develop hack resilient software
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

25. Security profile of a software
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
The likelihood that a threat can result into an incident. This is the overall risk of a system
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

26. Complete mediation
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Secure applicatios running on secure hosts (systems) in a secure network
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 request by a subject to an object is mediated each time and every time.

27. Access Matrix model

28. ISO/IEC 9216
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Number of incidents that can be expected in a year
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

29. OWASP testing guide
Number of incidents that can be expected in a year
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Covers the necessary procedures and tools to validate software assurance
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

30. OWASP development guide
Security controls applied after a threat has been materialized
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.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

31. Residual Risk
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
Risk remains after the implementation of mitigating security 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

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

33. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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
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

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

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

36. Safeguards
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support policies at a granular and specific level - Can be characterized as internal and external
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Security controls applied to mitigate a threat before it materializes

37. Exposure factor (EF)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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.
Technical - Management - Operational

38. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security controls applied after a threat has been materialized

39. NIST standards related to software security
OWASP - ITIL
Authentication
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
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

40. Security design principles
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
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
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.
Periodic publication by OWASP for top 10 Web application security vulnerabilites

41. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

42. After identification step is...
Authentication
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
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

43. Total Risk
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support for accreditation and certification bodies that audit and certify ISMS
Secure applicatios running on secure hosts (systems) in a secure network
The likelihood that a threat can result into an incident. This is the overall risk of a system

44. Counter measures
Security controls applied after a threat has been materialized
Confidentiality - Integrity - Availability
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
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

45. Availability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

46. Information Security Models
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

47. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

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

49. Least privilege
OWASP - ITIL
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
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
Confidentiality - Integrity - Availability

50. Core Security Concept
Confidentiality - Integrity - Availability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites