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. Counter measures
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
Security controls applied after a threat has been materialized
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

2. Security Standards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Support policies at a granular and specific level - Can be characterized as internal and external
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

3. 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
Technical - Management - Operational
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

4. Annual Rate of Occurence (ARO)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Number of incidents that can be expected in a year
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

5. ISO/IEC 15408
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
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
Provides Common Criteria to evaluate IT security product

6. Categories of controls
OWASP - ITIL
Technical - Management - Operational
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Design to mitigate any single source of complete compromise

7. Session Management
Access request by a subject to an object is mediated each time and every time.
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
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
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

8. ISO/IEC 27005:2008
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
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

9. Technical Controls
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 policies at a granular and specific level - Can be characterized as internal and external
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
OWASP - ITIL

10. Threat
Number of incidents that can be expected in a year
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

11. Authentication
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

12. Confidentiality
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Protection against unauthorized information disclosure. It helps maintaining privacy
Technical - Management - Operational
Provides Common Criteria to evaluate IT security product

13. ISO/IEC 27001:2005
Security controls applied to mitigate a threat before it materializes
Covers the necessary procedures and tools to validate software assurance
Authentication
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

14. Exposure factor (EF)
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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 remains after the implementation of mitigating security controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

15. Information Security Models
Support policies at a granular and specific level - Can be characterized as internal and external
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

16. Authorization
Access request by a subject to an object is mediated each time and every time.
OWASP - ITIL
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

17. Clipping level
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
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

18. 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.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

19. Flaw Hypothesis Method (FHM)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

20. Complete mediation
Indicator of magnitude risk in a year ALE = SLE * ARO
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Access request by a subject to an object is mediated each time and every time.
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

21. Security Risk Management Discipline
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Technical - Management - Operational

22. Access Matrix model

23. Implementation challenges
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Confidentiality - Integrity - Availability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

24. Single point failure
Design to mitigate any single source of complete compromise
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Development guide - Code Review Guide - Testing Guide

25. Management 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
Design to mitigate any single source of complete compromise
Support policies at a granular and specific level - Can be characterized as internal and external
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

26. NIST standards related to software security
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

27. Security Controls
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Access request by a subject to an object is mediated each time and every time.
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

28. Safeguards
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
Security controls applied to mitigate a threat before it materializes
Still under development - aimsto address ISMS implementation guidance
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

29. Properties of secure software
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Secure applicatios running on secure hosts (systems) in a secure network

30. Security design principles
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

31. Compartmentalization
Covers the necessary procedures and tools to validate software assurance
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Provides Common Criteria to evaluate IT security product

32. General 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

33. Develop hack resilient 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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

34. Total Risk
Support for accreditation and certification bodies that audit and certify ISMS
Covers the necessary procedures and tools to validate software assurance
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
The likelihood that a threat can result into an incident. This is the overall risk of a system

35. ISO/IEC 9216
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
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
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

36. Core Security Concept
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Confidentiality - Integrity - Availability

37. Multifactor authentication
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

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

39. ISO /IEC 27000:2009
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Number of incidents that can be expected in a year
Secure applicatios running on secure hosts (systems) in a secure network
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

40. Vulnerability
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

41. ISO/IEC 27002:2005
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Provides Common Criteria to evaluate IT security product

42. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

43. Vulnerabilities repositories
Still under development - aimsto address ISMS implementation guidance
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

44. ISO/IEC 27006:2007
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Support for accreditation and certification bodies that audit and certify ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

45. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Provides Common Criteria to evaluate IT security product
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

46. Integrity
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Development guide - Code Review Guide - Testing Guide
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

47. OWASP testing guide
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
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
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

48. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Security functionality is easy to use and transparent
Security controls applied after a threat has been materialized
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. Security Policies

50. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Covers the necessary procedures and tools to validate software assurance
Support for accreditation and certification bodies that audit and certify ISMS