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. Flaw Hypothesis Method (FHM)
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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. Total Risk
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

3. Holistic Security in software
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
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
Secure applicatios running on secure hosts (systems) in a secure network

4. NIST standards related to software security
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
Covers the necessary procedures and tools to validate software assurance
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
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

5. Security Controls
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
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
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

6. Error and exception management
Authentication
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

7. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

8. Annual Loss Expectancy (ALE)
Design to mitigate any single source of complete compromise
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

9. Availability
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.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Periodic publication by OWASP for top 10 Web application security vulnerabilites

10. Security design principles
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

11. General security concept
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Number of incidents that can be expected in a year

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

13. Integrity
Still under development - aimsto address ISMS implementation guidance
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

14. 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
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 remains after the implementation of mitigating security controls
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

15. After identification step is...
Design to mitigate any single source of complete compromise
Indicator of magnitude risk in a year ALE = SLE * ARO
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

16. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network

17. OWASP testing guide
Security controls applied to mitigate a threat before it materializes
Covers the necessary procedures and tools to validate software assurance
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

18. Exposure factor (EF)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

19. Authentication
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

20. Management Controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Number of incidents that can be expected in a year
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

21. FIPS140-2 (Security requirement for cryptographic modules)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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 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
Support for accreditation and certification bodies that audit and certify ISMS

22. OWASP development guide
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

23. ISO/IEC 27005:2008
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

24. Technical Controls
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

25. Security Policies

26. Security Risk Management Discipline
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 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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Development guide - Code Review Guide - Testing Guide

27. Challenges in implementing auditing/logging
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

28. Safeguards
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
Development guide - Code Review Guide - Testing Guide
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

29. Software security risk management methodologies
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
Covers the necessary procedures and tools to validate software assurance
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

30. Operation Controls
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

31. Complete mediation
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
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
Access request by a subject to an object is mediated each time and every time.
OWASP - ITIL

32. OCTAVE
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Security controls applied after a threat has been materialized
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

33. ISO/IEC 15408
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Provides Common Criteria to evaluate IT security product
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

34. OWASP Code Review Guide
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

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

36. Categories of controls
Technical - Management - Operational
OWASP - ITIL
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

37. Least common mechanism
Access request by a subject to an object is mediated each time and every time.
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
Security controls applied after a threat has been materialized

38. PCI DSS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Indicator of magnitude risk in a year ALE = SLE * ARO
Technical - Management - Operational
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

39. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

40. Single point failure
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
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

41. Least privilege
Risk remains after the implementation of mitigating security controls
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
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
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

42. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

43. Information Security Models
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

44. Phsychological acceptability
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Security functionality is easy to use and transparent

45. ISO/IEC 21827:2008
Number of incidents that can be expected in a year
Technical - Management - Operational
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

46. Common best practices significant to Sofware 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
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.
OWASP - ITIL
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

47. Vulnerability
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

48. EALs levels
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

49. Configurations Parameters Management
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
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.
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

50. Threat
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Support policies at a granular and specific level - Can be characterized as internal and external