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. Least privilege
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
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
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

2. Single Loss Expectancy (SLE)
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

3. Availability
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
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:
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

4. Software security risk management methodologies
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied

5. FIPS 201
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

6. Phsychological acceptability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security functionality is easy to use and transparent

7. OCTAVE
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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 request by a subject to an object is mediated each time and every time.
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

8. Authentication
Support policies at a granular and specific level - Can be characterized as internal and external
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
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

9. Flaw Hypothesis Method (FHM)
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Access request by a subject to an object is mediated each time and every time.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

10. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

11. Security design principles
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
Still under development - aimsto address ISMS implementation guidance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Confidentiality - Integrity - Availability

12. After identification step is...
Authentication
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

13. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

14. FIPS140-2 (Security requirement for cryptographic modules)
Technical - Management - Operational
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

15. Single point failure
Design to mitigate any single source of complete compromise
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
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied to mitigate a threat before it materializes

16. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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

17. OWASP development guide
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Confidentiality - Integrity - Availability
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
The likelihood that a threat can result into an incident. This is the overall risk of a system

18. Properties of secure software
The likelihood that a threat can result into an incident. This is the overall risk of a system
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

19. NIST standards related to software security
Number of incidents that can be expected in a year
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

20. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

21. Safeguards
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
Design to mitigate any single source of complete compromise
Security controls applied to mitigate a threat before it materializes

22. Core Security Concept
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.
Confidentiality - Integrity - Availability
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

23. Common best practices significant to Sofware Security
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
OWASP - ITIL
Access request by a subject to an object is mediated each time and every time.
Authentication

24. Benefits of coding standards
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
Support policies at a granular and specific level - Can be characterized as internal and external
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

25. STRIDE
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
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Support policies at a granular and specific level - Can be characterized as internal and external
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. FIPS 197 (Advance Cryptographic standards - AES)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

27. Holistic Security in software
Security controls applied after a threat has been materialized
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Secure applicatios running on secure hosts (systems) in a secure network

28. ISO/IEC 27005:2008
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

29. Security Policies

30. Annual Loss Expectancy (ALE)
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
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
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

31. DREAD
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

32. General security concept
Still under development - aimsto address ISMS implementation guidance
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Risk remains after the implementation of mitigating security controls
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

33. Security profile of a software
Confidentiality - Integrity - Availability
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
Indicator of magnitude risk in a year ALE = SLE * ARO
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

34. Management Controls
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

35. Popular guides developed by OWASP
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Development guide - Code Review Guide - Testing Guide
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

36. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security functionality is easy to use and transparent
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Design to mitigate any single source of complete compromise

37. ISO/IEC 15408
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
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
Provides Common Criteria to evaluate IT security product
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

38. Authorization
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 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

39. Open design
Risk remains after the implementation of mitigating security controls
Security functionality is easy to use and transparent
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

40. ISO/IEC 27002:2005
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

41. Exposure factor (EF)
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
Design to mitigate any single source of complete compromise
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.

42. Counter measures
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security controls applied after a threat has been materialized
Authentication
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

43. Session Management
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
Authentication
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

44. Compartmentalization
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

45. ISO/IEC 21827:2008
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

46. Integrity
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
Support for accreditation and certification bodies that audit and certify ISMS
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

47. Multifactor authentication
Covers the necessary procedures and tools to validate software assurance
Support for accreditation and certification bodies that audit and certify ISMS
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

48. Configurations Parameters Management
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

49. Complete mediation
Security functionality is easy to use and transparent
Access request by a subject to an object is mediated each time and every time.
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

50. Error and exception management
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability