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. Security Policies

2. Operation Controls
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

3. EALs levels
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

4. Multifactor authentication
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Covers the necessary procedures and tools to validate software assurance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

5. Holistic Security in software
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Secure applicatios running on secure hosts (systems) in a secure network

6. 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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

7. Security Standards
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Authentication
Support policies at a granular and specific level - Can be characterized as internal and external
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

8. Popular guides developed by OWASP
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Development guide - Code Review Guide - Testing Guide

9. Single point failure
Design to mitigate any single source of complete compromise
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

10. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

11. 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: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

12. DREAD
Confidentiality - Integrity - Availability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

13. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Secure applicatios running on secure hosts (systems) in a secure network
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

14. Risk management process
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

15. Non Repudiation
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 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
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
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

16. Session 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

17. Counter measures
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
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
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

18. Safeguards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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 controls applied to mitigate a threat before it materializes
estimate potential loss of a single incident: SLE = Asset value * EF(%)

19. Auditing
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

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

21. Flaw Hypothesis Method (FHM)
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Covers the necessary procedures and tools to validate software assurance

22. ISO/IEC 27005:2008
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Security functionality is easy to use and transparent

23. Residual Risk
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
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
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.

24. Categories of controls
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Technical - Management - Operational

25. 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.
Support policies at a granular and specific level - Can be characterized as internal and external
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

26. Configurations Parameters Management
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Still under development - aimsto address ISMS implementation guidance
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

27. After identification step is...
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Authentication

28. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

29. FIPS 201
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Technical - Management - Operational

30. Availability
OWASP - ITIL
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.
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

31. Examples of Security Standards
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

32. FIPS 197 (Advance Cryptographic standards - AES)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

33. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc

34. 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
Confidentiality - Integrity - Availability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

35. General security concept
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Design to mitigate any single source of complete compromise

36. Vulnerabilities repositories
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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

37. OWASP Top 10
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

38. ISO /IEC 27000:2009
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
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
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

39. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

40. Information Security Models
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

41. Access Matrix model

42. Exposure factor (EF)
Technical - Management - Operational
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Design to mitigate any single source of complete compromise
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

43. OWASP 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Covers the necessary procedures and tools to validate software assurance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

44. 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
Access request by a subject to an object is mediated each time and every time.
Confidentiality - Integrity - Availability
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

45. OWASP development guide
Predetermined number of user error allowed before recording it as a security violation
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Protection against unauthorized information disclosure. It helps maintaining privacy
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

46. ISO/IEC 27006:2007
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support for accreditation and certification bodies that audit and certify ISMS

47. OWASP Code Review Guide
Secure applicatios running on secure hosts (systems) in a secure network
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

48. Benefits of coding standards
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Support for accreditation and certification bodies that audit and certify ISMS
Protection against unauthorized information disclosure. It helps maintaining privacy

49. Vulnerability
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Support policies at a granular and specific level - Can be characterized as internal and external
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

50. Open design
The likelihood that a threat can result into an incident. This is the overall risk of a system
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:
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