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. Access Matrix model

2. Integrity
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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
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
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

3. DREAD
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
OWASP - ITIL

4. OWASP Code Review Guide
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
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

5. 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

6. Single point failure
Design to mitigate any single source of complete compromise
Confidentiality - Integrity - Availability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

7. STRIDE
Design to mitigate any single source of complete compromise
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

8. Examples of Security Standards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

9. Multifactor authentication
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

10. Least privilege
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
Access request by a subject to an object is mediated each time and every time.
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

11. Clipping level
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Predetermined number of user error allowed before recording it as a security violation

12. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

13. ISO/IEC 27003
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Still under development - aimsto address ISMS implementation guidance

14. Counter measures
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Number of incidents that can be expected in a year
Security controls applied after a threat has been materialized
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

15. 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
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
Development guide - Code Review Guide - Testing Guide
Security controls applied after a threat has been materialized

16. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Indicator of magnitude risk in a year ALE = SLE * ARO
Security controls applied after a threat has been materialized
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

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

18. Develop hack resilient software
Access request by a subject to an object is mediated each time and every time.
Support policies at a granular and specific level - Can be characterized as internal and external
Risk remains after the implementation of mitigating security controls
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

19. Common best practices significant to Sofware Security
OWASP - ITIL
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

20. FIPS 197 (Advance Cryptographic standards - AES)
Support for accreditation and certification bodies that audit and certify ISMS
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support policies at a granular and specific level - Can be characterized as internal and external
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

21. After identification step is...
Authentication
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Risk remains after the implementation of mitigating security controls

22. Single Loss Expectancy (SLE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

23. Core Security Concept
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
Design to mitigate any single source of complete compromise
Confidentiality - Integrity - Availability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

24. Popular guides developed by OWASP
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Development guide - Code Review Guide - Testing Guide
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
Confidentiality - Integrity - Availability

25. 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
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
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.

26. ISO/IEC 21827:2008
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

27. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Secure applicatios running on secure hosts (systems) in a secure network
Development guide - Code Review Guide - Testing Guide

28. Complete mediation
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Access request by a subject to an object is mediated each time and every time.
Security controls applied after a threat has been materialized

29. 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
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
Provides Common Criteria to evaluate IT security product
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

30. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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 Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Periodic publication by OWASP for top 10 Web application security vulnerabilites

31. Security profile of a software
Covers the necessary procedures and tools to validate software assurance
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
Technical - Management - Operational
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

32. ISO /IEC 27000:2009
Access request by a subject to an object is mediated each time and every time.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

33. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

34. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
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

35. ISO/IEC 27006:2007
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Support for accreditation and certification bodies that audit and certify ISMS
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
Confidentiality - Integrity - Availability

36. Residual Risk
Risk remains after the implementation of mitigating security 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
OWASP - ITIL
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

37. Implementation challenges
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Security functionality is easy to use and transparent
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

38. Configurations Parameters Management
Support for accreditation and certification bodies that audit and certify ISMS
Risk remains after the implementation of mitigating security controls
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

39. Properties of secure software
Access request by a subject to an object is mediated each time and every time.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Still under development - aimsto address ISMS implementation guidance
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

40. PCI DSS
Risk remains after the implementation of mitigating security controls
Predetermined number of user error allowed before recording it as a security violation
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

41. ISO/IEC 9216
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
OWASP - ITIL
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

42. Error and exception management
Security controls applied after a threat has been materialized
Design to mitigate any single source of complete compromise
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 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

43. FIPS 201
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Support for accreditation and certification bodies that audit and certify ISMS

44. OWASP testing guide
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
Risk remains after the implementation of mitigating security controls
Covers the necessary procedures and tools to validate software assurance
Security functionality is easy to use and transparent

45. Software security risk management methodologies
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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

46. Compartmentalization
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

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

48. Session Management
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
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Specifies 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
Provides Common Criteria to evaluate IT security product

49. Availability
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
Security controls applied after a threat has been materialized
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.

50. Economy of mechanism
Access request by a subject to an object is mediated each time and every time.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment