Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Subjects : certifications, csslp, it-skills

Instructions:

Answer 50 questions in 30 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. Non Repudiation
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Indicator of magnitude risk in a year ALE = SLE * ARO
Secure applicatios running on secure hosts (systems) in a secure network
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

2. Single point failure
OWASP - ITIL
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Design to mitigate any single source of complete compromise
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

3. Auditing
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

4. Phsychological acceptability
Indicator of magnitude risk in a year ALE = SLE * ARO
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Security functionality is easy to use and transparent
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

5. Core Security Concept
Security controls applied after a threat has been materialized
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Confidentiality - Integrity - Availability
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

6. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Still under development - aimsto address ISMS implementation guidance

7. Vulnerabilities repositories
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

8. Safeguards
Access request by a subject to an object is mediated each time and every time.
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Security controls applied to mitigate a threat before it materializes

9. Properties of secure software
Secure applicatios running on secure hosts (systems) in a secure network
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

10. Security profile of a software
estimate potential loss of a single incident: SLE = Asset value * EF(%)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

11. Single Loss Expectancy (SLE)
Access request by a subject to an object is mediated each time and every time.
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.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

12. FIPS 197 (Advance Cryptographic standards - AES)
Development guide - Code Review Guide - Testing Guide
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

13. ISO/IEC 9216
Provides Common Criteria to evaluate IT security product
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

14. Clipping level
Predetermined number of user error allowed before recording it as a security violation
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
Indicator of magnitude risk in a year ALE = SLE * ARO

15. Complete mediation
Still under development - aimsto address ISMS implementation guidance
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Access request by a subject to an object is mediated each time and every time.
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

16. Benefits of coding standards
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

17. ISO /IEC 27000:2009
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

18. Accountability
Security controls applied after a threat has been materialized
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

19. NIST standards related to software security
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Number of incidents that can be expected in a year
Security functionality is easy to use and transparent

20. Access Matrix model

21. OWASP Top 10
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

22. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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
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

23. ISO/IEC 27005:2008
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Protection against 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

24. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Technical - Management - Operational
The likelihood that a threat can result into an incident. This is the overall risk of a system

25. 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
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
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.

26. 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Number of incidents that can be expected in a year
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

27. Flaw Hypothesis Method (FHM)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

28. Security Controls
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Predetermined number of user error allowed before recording it as a security violation
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

29. ISO/IEC 27001:2005
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

30. OCTAVE
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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
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

31. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Secure applicatios running on secure hosts (systems) in a secure network
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

32. Total Risk
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
The likelihood that a threat can result into an incident. This is the overall risk of a system

33. Authentication
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Covers the necessary procedures and tools to validate software assurance
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

34. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Confidentiality - Integrity - Availability
Number of incidents that can be expected in a year

35. Common best practices significant to Sofware Security
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.
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
OWASP - ITIL

36. Take-Grant Model
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of 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
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

37. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Protection against unauthorized information disclosure. It helps maintaining privacy
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

38. ISO/IEC 15408
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Indicator of magnitude risk in a year ALE = SLE * ARO
Provides Common Criteria to evaluate IT security product

39. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
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
Confidentiality - Integrity - Availability
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

40. Holistic Security in software
Support for accreditation and certification bodies that audit and certify ISMS
Protection against unauthorized information disclosure. It helps maintaining privacy
Secure applicatios running on secure hosts (systems) in a secure network
Indicator of magnitude risk in a year ALE = SLE * ARO

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

42. Compartmentalization
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Development guide - Code Review Guide - 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

43. Security Policies

44. Information Security Models
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

45. Integrity
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Authentication
Number of incidents that can be expected in a year

46. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
OWASP - ITIL
Security functionality is easy to use and transparent

47. Session Management
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
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
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

48. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Risk remains after the implementation of mitigating security controls
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.

49. Categories of controls
Technical - Management - Operational
Authentication
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Still under development - aimsto address ISMS implementation guidance

50. Counter measures
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security controls applied after a threat has been materialized
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods