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. Flaw Hypothesis Method (FHM)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Access request by a subject to an object is mediated each time and every time.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

2. Benefits of coding standards
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Development guide - Code Review Guide - Testing Guide
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

3. Examples of Security Standards
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

4. PCI DSS
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
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
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 functionality is easy to use and transparent

5. Security design principles
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
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
Number of incidents that can be expected in a year

6. Non Repudiation
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational
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
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

7. Categories of controls
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
Provides Common Criteria to evaluate IT security product
Support policies at a granular and specific level - Can be characterized as internal and external
Technical - Management - Operational

8. Take-Grant Model
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

9. Single point failure
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Design to mitigate any single source of complete compromise
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

10. 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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

11. Technical Controls
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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

12. OWASP Top 10
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

13. Risk management process
Development guide - Code Review Guide - Testing Guide
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

14. Access Matrix model

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

16. Implementation challenges
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
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

17. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
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
Security controls applied after a threat has been materialized
OWASP - ITIL

18. Integrity
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
Provides Common Criteria to evaluate IT security product
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

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

20. Safeguards
Security controls applied to mitigate a threat before it materializes
Provides Common Criteria to evaluate IT security product
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Periodic publication by OWASP for top 10 Web application security vulnerabilites

21. Security Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

22. Error and exception management
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Predetermined number of user error allowed before recording it as a security violation
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
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

23. Security profile of a software
Security controls applied to mitigate a threat before it materializes
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

24. Security Standards
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Support policies at a granular and specific level - Can be characterized as internal and external

25. Develop hack resilient 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
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

26. DREAD
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

27. Vulnerability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

28. Annual Rate of Occurence (ARO)
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
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

29. Management Controls
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

30. FIPS 197 (Advance Cryptographic standards - AES)
Access request by a subject to an object is mediated each time and every time.
Authentication
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

31. Accountability
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

32. Annual Loss Expectancy (ALE)
Technical - Management - Operational
Covers the necessary procedures and tools to validate software assurance
Still under development - aimsto address ISMS implementation guidance
Indicator of magnitude risk in a year ALE = SLE * ARO

33. Popular guides developed by OWASP
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Access request by a subject to an object is mediated each time and every time.
Development guide - Code Review Guide - Testing Guide

34. Open design
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Development guide - Code Review Guide - Testing Guide
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

35. Complete mediation
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Access request by a subject to an object is mediated each time and every time.
Design to mitigate any single source of complete compromise

36. Availability
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 remains after the implementation of mitigating security controls
Confidentiality - Integrity - Availability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

37. Core Security Concept
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
Still under development - aimsto address ISMS implementation guidance
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Confidentiality - Integrity - Availability

38. FIPS140-2 (Security requirement for cryptographic modules)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Access request by a subject to an object is mediated each time and every time.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Periodic publication by OWASP for top 10 Web application security vulnerabilites

39. Confidentiality
Security functionality is easy to use and transparent
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

40. 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
Secure applicatios running on secure hosts (systems) in a secure network
Still under development - aimsto address ISMS implementation guidance

41. Information Security Models
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 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk 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

42. Software security risk management methodologies
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

43. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Secure applicatios running on secure hosts (systems) in a secure network
Predetermined number of user error allowed before recording it as a security violation

44. ISO/IEC 27002:2005
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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.
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

45. Clipping level
Predetermined number of user error allowed before recording it as a security violation
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
Secure applicatios running on secure hosts (systems) in a secure network
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

46. ISO /IEC 27000:2009
Predetermined number of user error allowed before recording it as a security violation
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
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
Protection against unauthorized information disclosure. It helps maintaining privacy

47. Challenges in implementing auditing/logging
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Access request by a subject to an object is mediated each time and every time.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

48. Security Risk Management Discipline
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

49. 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
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

50. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Design to mitigate any single source of complete compromise
Support policies at a granular and specific level - Can be characterized as internal and external
Predetermined number of user error allowed before recording it as a security violation