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. Threat
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security functionality is easy to use and transparent
Support policies at a granular and specific level - Can be characterized as internal and external

2. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system

3. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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

4. Challenges in implementing auditing/logging
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Authentication
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

5. ISO/IEC 27003
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Still under development - aimsto address ISMS implementation guidance
Support for accreditation and certification bodies that audit and certify ISMS

6. Management Controls
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Design to mitigate any single source of complete compromise

7. 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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Access request by a subject to an object is mediated each time and every time.
The likelihood that a threat can result into an incident. This is the overall risk of a system

8. Security Risk Management Discipline
Authentication
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

9. Least privilege
Technical - Management - Operational
Indicator of magnitude risk in a year ALE = SLE * ARO
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job

10. Counter measures
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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 controls applied after a threat has been materialized

11. NIST standards related to software security
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Security functionality is easy to use and transparent
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

12. OWASP testing guide
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Covers the necessary procedures and tools to validate software assurance

13. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

14. Properties of secure software
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

15. Technical Controls
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

16. Develop hack resilient software
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

17. 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

18. Access Matrix model

19. ISO/IEC 21827:2008
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
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.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

20. OWASP development guide
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.
Provides Common Criteria to evaluate IT security product
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

21. Safeguards
Access request by a subject to an object is mediated each time and every time.
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
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
Security controls applied to mitigate a threat before it materializes

22. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
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
Still under development - aimsto address ISMS implementation guidance
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

23. Availability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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. Accountability
Secure applicatios running on secure hosts (systems) in a secure network
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

25. EALs levels
Confidentiality - Integrity - Availability
Development guide - Code Review Guide - Testing Guide
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

26. ISO/IEC 27006:2007
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Support for accreditation and certification bodies that audit and certify ISMS

27. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

28. Benefits of coding standards
OWASP - ITIL
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

29. Open design
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Indicator of magnitude risk in a year ALE = SLE * ARO
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

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

31. Error and exception management
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
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 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
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

32. Security profile of a software
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Protection against unauthorized information disclosure. It helps maintaining privacy
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

33. Risk management process
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

34. OWASP Top 10
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Risk remains after the implementation of mitigating security controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites

35. ISO/IEC 27001:2005
OWASP - ITIL
Risk remains after the implementation of mitigating security controls
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

36. 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
Authentication
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy

37. ISO/IEC 27005:2008
Support policies at a granular and specific level - Can be characterized as internal and external
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

38. FIPS140-2 (Security requirement for cryptographic modules)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

39. Economy of mechanism
Predetermined number of user error allowed before recording it as a security violation
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Protection against unauthorized information disclosure. It helps maintaining privacy
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

40. Take-Grant Model
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Development guide - Code Review Guide - Testing Guide
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

41. General security concept
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Secure applicatios running on secure hosts (systems) in a secure network
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

42. Popular guides developed by OWASP
Covers the necessary procedures and tools to validate software assurance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Development guide - Code Review Guide - Testing Guide

43. Configurations Parameters Management
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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 the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

44. Security design principles
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
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.
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

45. Annual Rate of Occurence (ARO)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Number of incidents that can be expected in a year
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

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

47. 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
Development guide - Code Review Guide - Testing Guide
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 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

48. Core Security Concept
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Technical - Management - Operational
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Confidentiality - Integrity - Availability

49. OCTAVE
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
Support policies at a granular and specific level - Can be characterized as internal and external
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

50. STRIDE
Authentication
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Development guide - Code Review Guide - Testing Guide
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