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. NIST standards related to software security
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
Development guide - Code Review Guide - Testing Guide
Authentication
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

2. OCTAVE
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 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
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

3. OWASP Code Review Guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Covers the necessary procedures and tools to validate software assurance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

4. Safeguards
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
Security controls applied to mitigate a threat before it materializes
Covers the necessary procedures and tools to validate software assurance

5. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

6. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

7. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

8. Accountability
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Secure applicatios running on secure hosts (systems) in a secure network
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

9. DREAD
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 calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

10. 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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Risk remains after the implementation of mitigating security controls

11. Risk management process
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
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

12. OWASP testing guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Covers the necessary procedures and tools to validate software assurance
Indicator of magnitude risk in a year ALE = SLE * ARO
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

13. Access Matrix model

14. Core Security Concept
Confidentiality - Integrity - Availability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

15. Economy of mechanism
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Still under development - aimsto address ISMS implementation guidance
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

16. ISO/IEC 27006:2007
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Support for accreditation and certification bodies that audit and certify ISMS
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 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

17. Security Policies

18. Least common mechanism
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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.
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

19. Challenges in implementing auditing/logging
OWASP - ITIL
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

20. Security Risk Management Discipline
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

21. Security Standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Support policies at a granular and specific level - Can be characterized as internal and external
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

22. Authentication
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
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
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
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

23. Configurations Parameters Management
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
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
Support for accreditation and certification bodies that audit and certify ISMS

24. Non Repudiation
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Provides Common Criteria to evaluate IT security product
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

25. 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
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
Development guide - Code Review Guide - Testing Guide
The likelihood that a threat can result into an incident. This is the overall risk of a system

26. ISO/IEC 27001:2005
Design to mitigate any single source of complete compromise
Access request by a subject to an object is mediated each time and every time.
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 the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

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

28. STRIDE
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

29. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Risk remains after the implementation of mitigating security controls
Support for accreditation and certification bodies that audit and certify ISMS
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

30. Single point failure
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
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
Design to mitigate any single source of complete compromise
Security controls applied to mitigate a threat before it materializes

31. Categories of controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
The likelihood that a threat can result into an incident. This is the overall risk of a system
Technical - Management - Operational
Provides Common Criteria to evaluate IT security product

32. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Protection against unauthorized information disclosure. It helps maintaining privacy
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
OWASP - ITIL

33. ISO/IEC 21827:2008
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Design to mitigate any single source of complete compromise

34. Flaw Hypothesis Method (FHM)
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
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

35. ISO /IEC 27000:2009
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
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
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

36. 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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

37. Counter measures
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Security controls applied after a threat has been materialized

38. After identification step is...
Authentication
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Support policies at a granular and specific level - Can be characterized as internal and external

39. Availability
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Security controls applied to mitigate a threat before it materializes
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

40. ISO/IEC 15408
Protection against unauthorized information disclosure. It helps maintaining privacy
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Indicator of magnitude risk in a year ALE = SLE * ARO
Provides Common Criteria to evaluate IT security product

41. Complete mediation
Access request by a subject to an object is mediated each time and every time.
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

42. Single Loss Expectancy (SLE)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Protection against unauthorized information disclosure. It helps maintaining privacy
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

43. Auditing
Security controls applied to mitigate a threat before it materializes
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
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
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

44. Residual Risk
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 remains after the implementation of mitigating security controls
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
Protection against unauthorized information disclosure. It helps maintaining privacy

45. FIPS 197 (Advance Cryptographic standards - AES)
Support policies at a granular and specific level - Can be characterized as internal and external
Provides Common Criteria to evaluate IT security product
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

46. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
estimate potential loss of a single incident: SLE = Asset value * EF(%)

47. ISO/IEC 27005:2008
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

48. ISO/IEC 9216
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Security controls applied to mitigate a threat before it materializes
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

49. FIPS140-2 (Security requirement for cryptographic modules)
Security functionality is easy to use and transparent
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
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

50. ISO/IEC 27002:2005
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards