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. PCI DSS
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
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 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

2. Security profile of a 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
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
Technical - Management - Operational
Access request by a subject to an object is mediated each time and every time.

3. Clipping level
Predetermined number of user error allowed before recording it as a security violation
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Design to mitigate any single source of complete compromise

4. Implementation challenges
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
Authentication
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

5. Vulnerabilities repositories
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
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
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

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

7. ISO/IEC 27005:2008
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

8. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

9. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Security functionality is easy to use and transparent
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

10. Management Controls
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Predetermined number of user error allowed before recording it as a security violation
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: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

11. ISO/IEC 15408
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
Provides Common Criteria to evaluate IT security product
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
OWASP - ITIL

12. Authentication
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Still under development - aimsto address ISMS implementation guidance

13. Auditing
Predetermined number of user error allowed before recording it as a security violation
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
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.

14. STRIDE
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

15. ISO/IEC 27001:2005
Confidentiality - Integrity - Availability
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
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

16. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

17. 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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Design to mitigate any single source of complete compromise
Authentication

18. Economy of mechanism
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
The likelihood that a threat can result into an incident. This is the overall risk of a system
Security controls applied after a threat has been materialized
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

19. 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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

20. Accountability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

21. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Security controls applied after a threat has been materialized

22. ISO/IEC 27006:2007
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
Support for accreditation and certification bodies that audit and certify ISMS
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied after a threat has been materialized

23. Least common mechanism
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

24. Core Security Concept
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
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Confidentiality - Integrity - Availability

25. Error and exception 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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Access request by a subject to an object is mediated each time and every time.

26. Security Standards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Support policies at a granular and specific level - Can be characterized as internal and external
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

27. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Development guide - Code Review Guide - Testing Guide
Design to mitigate any single source of complete compromise
Number of incidents that can be expected in a year

28. Configurations Parameters Management
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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 calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Predetermined number of user error allowed before recording it as a security violation

29. Benefits of coding 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
Development guide - Code Review Guide - Testing Guide
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

30. Authorization
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Security functionality is easy to use and transparent
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

31. OWASP Code Review Guide
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

32. Counter measures
Security controls applied after a threat has been materialized
Risk remains after the implementation of mitigating security controls
Provides Common Criteria to evaluate IT security product
Design to mitigate any single source of complete compromise

33. ISO/IEC 27003
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Still under development - aimsto address ISMS implementation guidance

34. Challenges in implementing auditing/logging
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

35. Popular guides developed by OWASP
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
Development guide - Code Review Guide - Testing Guide
Design to mitigate any single source of complete compromise
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

36. Safeguards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Security controls applied to mitigate a threat before it materializes
Provides Common Criteria to evaluate IT security product
Support for accreditation and certification bodies that audit and certify ISMS

37. Security Policies

38. Single point failure
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Design to mitigate any single source of complete compromise
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

39. Complete mediation
Security controls applied after a threat has been materialized
Access request by a subject to an object is mediated each time and every time.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

40. Residual Risk
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Risk remains after the implementation of mitigating security controls
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

41. DREAD
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.
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
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

42. FIPS140-2 (Security requirement for cryptographic modules)
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

43. 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
OWASP - ITIL
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
Protection against unauthorized information disclosure. It helps maintaining privacy

44. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
OWASP - ITIL
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

45. Properties of secure software
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security controls applied to mitigate a threat before it materializes
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

46. Open design
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
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)
Support for accreditation and certification bodies that audit and certify ISMS

47. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Technical - Management - Operational
Support for accreditation and certification bodies that audit and certify ISMS

48. OWASP development guide
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

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

50. Access Matrix model