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. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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

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

3. Annual Loss Expectancy (ALE)
Confidentiality - Integrity - Availability
Indicator of magnitude risk in a year ALE = SLE * ARO
Access request by a subject to an object is mediated each time and every time.
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

4. Availability
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
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.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

5. Auditing
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Support policies at a granular and specific level - Can be characterized as internal and external

6. Popular guides developed by OWASP
Security controls applied after a threat has been materialized
Development guide - Code Review Guide - Testing Guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
estimate potential loss of a single incident: SLE = Asset value * EF(%)

7. Holistic Security in software
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Secure applicatios running on secure hosts (systems) in a secure network

8. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

9. OWASP Code Review Guide
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

10. Accountability
Risk remains after the implementation of mitigating security 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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

11. Security Policies

12. Categories of controls
Security functionality is easy to use and transparent
Technical - Management - Operational
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

13. Error and exception management
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
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

14. ISO/IEC 27002:2005
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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

15. Residual Risk
Risk remains after the implementation of mitigating security controls
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Secure applicatios running on secure hosts (systems) in a secure network
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

16. 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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Predetermined number of user error allowed before recording it as a security violation

17. OWASP Top 10
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Covers the necessary procedures and tools to validate software assurance
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Periodic publication by OWASP for top 10 Web application security vulnerabilites

18. Least common mechanism
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

19. EALs levels
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Confidentiality - Integrity - Availability
Technical - Management - Operational
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

20. Integrity
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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

21. Economy of mechanism
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

22. ISO/IEC 27005:2008
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
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

23. Complete mediation
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.
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 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

24. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Confidentiality - Integrity - Availability
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

25. FIPS140-2 (Security requirement for cryptographic modules)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Risk remains after the implementation of mitigating security 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
Protection against unauthorized information disclosure. It helps maintaining privacy

26. Information Security Models
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Technical - Management - Operational

27. Compartmentalization
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

28. Configurations Parameters Management
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

29. Security Risk Management Discipline
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

30. Single Loss Expectancy (SLE)
Indicator of magnitude risk in a year ALE = SLE * ARO
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Authentication

31. ISO/IEC 15408
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Provides Common Criteria to evaluate IT security product

32. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Security controls applied to mitigate a threat before it materializes

33. Core Security Concept
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Still under development - aimsto address ISMS implementation guidance
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Confidentiality - Integrity - Availability

34. Examples of Security Standards
Design to mitigate any single source of complete compromise
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
OWASP - ITIL

35. 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
Security controls applied to mitigate a threat before it materializes
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
Development guide - Code Review Guide - Testing Guide

36. Authorization
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
Risk remains after the implementation of mitigating security controls
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
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

37. Single point failure
Security controls applied to mitigate a threat before it materializes
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Design to mitigate any single source of complete compromise

38. 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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

39. General security concept
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
Risk remains after the implementation of mitigating security controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

40. Vulnerability
Number of incidents that can be expected in a year
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
Still under development - aimsto address ISMS implementation guidance
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

41. Common best practices significant to Sofware Security
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Support for accreditation and certification bodies that audit and certify ISMS
OWASP - ITIL
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

42. Flaw Hypothesis Method (FHM)
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Number of incidents that can be expected in a year
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

44. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Risk remains after the implementation of mitigating security controls

45. ISO/IEC 21827:2008
Design to mitigate any single source of complete compromise
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

46. Security Controls
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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.

47. Security design principles
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Covers the necessary procedures and tools to validate software assurance

48. Risk management process
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
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
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

49. 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:
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Confidentiality - Integrity - Availability

50. Phsychological acceptability
Security functionality is easy to use and transparent
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
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