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. Take-Grant Model
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 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
Number of incidents that can be expected in a year
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

2. OWASP development guide
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Number of incidents that can be expected in a year

3. Security Policies

4. After identification step is...
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Authentication
Covers the necessary procedures and tools to validate software assurance

5. ISO/IEC 27003
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
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Still under development - aimsto address ISMS implementation guidance

6. 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
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
Secure applicatios running on secure hosts (systems) in a secure network
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

7. Access Matrix model

8. Phsychological acceptability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Security functionality is easy to use and transparent

9. Annual Rate of Occurence (ARO)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Design to mitigate any single source of complete compromise
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

10. ISO/IEC 27006:2007
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
Support for accreditation and certification bodies that audit and certify ISMS
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

11. Security design principles
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
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
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

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

13. Popular guides developed by OWASP
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Development guide - Code Review Guide - Testing Guide
Number of incidents that can be expected in a year

14. Least privilege
Risk remains after the implementation of mitigating security controls
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
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

15. Residual Risk
Predetermined number of user error allowed before recording it as a security violation
Risk remains after the implementation of mitigating security controls
Number of incidents that can be expected in a year
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

16. ISO /IEC 27000:2009
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Technical - Management - Operational

17. ISO/IEC 21827:2008
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

18. Challenges in implementing auditing/logging
Risk remains after the implementation of mitigating security controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Predetermined number of user error allowed before recording it as a security violation
Periodic publication by OWASP for top 10 Web application security vulnerabilites

19. Examples of Security Standards
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Technical - Management - Operational
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

20. Risk management process
Development guide - Code Review Guide - Testing Guide
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

21. 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
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: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

22. Vulnerability
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
Provides Common Criteria to evaluate IT security product
Confidentiality - Integrity - Availability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

23. STRIDE
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Technical - Management - Operational
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

24. Counter measures
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Covers the necessary procedures and tools to validate software assurance
Risk remains after the implementation of mitigating security controls
Security controls applied after a threat has been materialized

25. Confidentiality
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Protection against unauthorized information disclosure. It helps maintaining privacy
Access request by a subject to an object is mediated each time and every time.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

26. Operation Controls
OWASP - ITIL
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
Support for accreditation and certification bodies that audit and certify ISMS

27. Single point failure
Confidentiality - Integrity - Availability
Design to mitigate any single source of complete compromise
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

28. Economy of mechanism
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

29. ISO/IEC 9216
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
Development guide - Code Review Guide - Testing Guide
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

30. Compartmentalization
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

31. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

32. Security profile of a software
Security controls applied to mitigate a threat before it materializes
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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. PCI DSS
Support policies at a granular and specific level - Can be characterized as internal and external
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
Provides Common Criteria to evaluate IT security product
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

34. General security concept
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Protection against unauthorized information disclosure. It helps maintaining privacy

35. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

36. Security Standards
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
Support policies at a granular and specific level - Can be characterized as internal and external
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
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

37. NIST standards related to software security
Authentication
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 controls applied to mitigate a threat before it materializes
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 27001:2005
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Confidentiality - Integrity - Availability
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

39. Auditing
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Covers the necessary procedures and tools to validate software assurance
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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. Integrity
Indicator of magnitude risk in a year ALE = SLE * ARO
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 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
Confidentiality - Integrity - Availability

41. 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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Support policies at a granular and specific level - Can be characterized as internal and external

42. 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
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational
Indicator of magnitude risk in a year ALE = SLE * ARO

43. Configurations Parameters Management
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

44. Properties of secure software
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Risk remains after the implementation of mitigating security controls
Design to mitigate any single source of complete compromise

45. Non Repudiation
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

46. Technical Controls
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:
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
Technical - Management - Operational

47. Multifactor authentication
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Confidentiality - Integrity - Availability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Security functionality is easy to use and transparent

48. Safeguards
Security controls applied to mitigate a threat before it materializes
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Protection against unauthorized information disclosure. It helps maintaining privacy
Secure applicatios running on secure hosts (systems) in a secure network

49. Complete mediation
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
Support for accreditation and certification bodies that audit and certify ISMS
Access request by a subject to an object is mediated each time and every time.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

50. Availability
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
Security functionality is easy to use and transparent
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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.