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...
Security functionality is easy to use and transparent
Authentication
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Development guide - Code Review Guide - Testing Guide

2. OWASP development guide
Support policies at a granular and specific level - Can be characterized as internal and external
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

3. OWASP Code Review Guide
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

4. Categories of controls
Technical - Management - Operational
Secure applicatios running on secure hosts (systems) in a secure network
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

5. ISO/IEC 21827:2008
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 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

6. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Risk remains after the implementation of mitigating security controls

7. Clipping level
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Covers the necessary procedures and tools to validate software assurance
Predetermined number of user error allowed before recording it as a security violation

8. Configurations Parameters Management
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

9. Safeguards
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied to mitigate a threat before it materializes

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

11. EALs levels
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Support for accreditation and certification bodies that audit and certify ISMS

12. Popular guides developed by OWASP
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
Development guide - Code Review Guide - Testing Guide
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

13. Benefits of coding standards
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Secure applicatios running on secure hosts (systems) in a secure network

14. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Predetermined number of user error allowed before recording it as a security violation

15. Authentication
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Design to mitigate any single source of complete compromise

16. Information Security Models
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

17. Single point failure
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Indicator of magnitude risk in a year ALE = SLE * ARO
Design to mitigate any single source of complete compromise
Periodic publication by OWASP for top 10 Web application security vulnerabilites

18. Implementation challenges
Authentication
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

19. ISO/IEC 27006:2007
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Support for accreditation and certification bodies that audit and certify ISMS

20. Annual Loss Expectancy (ALE)
Secure applicatios running on secure hosts (systems) in a secure network
Number of incidents that can be expected in a year
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Indicator of magnitude risk in a year ALE = SLE * ARO

21. Availability
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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.
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

22. Flaw Hypothesis Method (FHM)
Indicator of magnitude risk in a year ALE = SLE * ARO
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

23. ISO/IEC 27005:2008
Still under development - aimsto address ISMS implementation guidance
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
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

24. Common best practices significant to Sofware Security
Support for accreditation and certification bodies that audit and certify ISMS
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
OWASP - ITIL
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

25. Counter measures
Security controls applied after a threat has been materialized
The likelihood that a threat can result into an incident. This is the overall risk of a system
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security functionality is easy to use and transparent

26. Error and exception management
Design to mitigate any single source of complete compromise
Support for accreditation and certification bodies that audit and certify ISMS
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
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. ISO /IEC 27000:2009
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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
Confidentiality - Integrity - Availability

28. OWASP 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Covers the necessary procedures and tools to validate software assurance
OWASP - ITIL

29. Security profile of a software
Confidentiality - Integrity - Availability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

30. ISO/IEC 27003
Development guide - Code Review Guide - Testing Guide
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
Still under development - aimsto address ISMS implementation guidance
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

31. Software security risk management methodologies
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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 SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

32. ISO/IEC 15408
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

33. Examples of Security Standards
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Security controls applied to mitigate a threat before it materializes

34. Vulnerability
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
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

35. FIPS 201
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

36. Develop hack resilient software
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security controls applied after a threat has been materialized
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

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

38. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
The likelihood that a threat can result into an incident. This is the overall risk of a system
Security functionality is easy to use and transparent

39. Complete mediation
Secure applicatios running on secure hosts (systems) in a secure network
Access request by a subject to an object is mediated each time and every time.
Support for accreditation and certification bodies that audit and certify ISMS
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

40. Least privilege
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
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

41. Properties of secure 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
Still under development - aimsto address ISMS implementation guidance
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

42. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
The likelihood that a threat can result into an incident. This is the overall risk of a system
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

43. Authorization
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Security controls applied to mitigate a threat before it materializes
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
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.

44. STRIDE
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

45. OCTAVE
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Secure applicatios running on secure hosts (systems) in a secure network

46. Threat
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

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

48. Core Security Concept
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
Confidentiality - Integrity - Availability
Indicator of magnitude risk in a year ALE = SLE * ARO
Predetermined number of user error allowed before recording it as a security violation

49. Vulnerabilities repositories
Security functionality is easy to use and transparent
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

50. Accountability
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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