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. Risk management process
Security functionality is easy to use and transparent
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
Security controls applied to mitigate a threat before it materializes
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

2. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

3. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

4. PCI DSS
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Design to mitigate any single source of complete compromise
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
Support policies at a granular and specific level - Can be characterized as internal and external

5. 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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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.

6. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Provides Common Criteria to evaluate IT security product
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

7. Counter measures
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied after a threat has been materialized
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

8. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
OWASP - ITIL
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Support policies at a granular and specific level - Can be characterized as internal and external

9. Develop hack resilient software
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Development guide - Code Review Guide - Testing Guide

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

11. 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
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.
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
Number of incidents that can be expected in a year

12. Security profile of a software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Covers the necessary procedures and tools to validate software assurance

13. Implementation challenges
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

14. Phsychological acceptability
Security functionality is easy to use and transparent
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

15. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system

16. Management 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
Confidentiality - Integrity - 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

17. Error and exception management
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Support for accreditation and certification bodies that audit and certify ISMS
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

18. Confidentiality
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Predetermined number of user error allowed before recording it as a security violation
Protection against unauthorized information disclosure. It helps maintaining privacy
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

19. OCTAVE
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
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
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

20. Properties of secure software
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security controls applied to mitigate a threat before it materializes
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

21. ISO/IEC 21827:2008
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
Risk remains after the implementation of mitigating security controls
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
estimate potential loss of a single incident: SLE = Asset value * EF(%)

22. Configurations Parameters Management
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 the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

23. OWASP Top 10
Confidentiality - Integrity - Availability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Periodic publication by OWASP for top 10 Web application security vulnerabilites

24. ISO/IEC 9216
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

25. Core Security Concept
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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
Confidentiality - Integrity - Availability

26. FIPS140-2 (Security requirement for cryptographic modules)
Technical - Management - Operational
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Number of incidents that can be expected in a year

27. Safeguards
Security controls applied to mitigate a threat before it materializes
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

28. Total Risk
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Predetermined number of user error allowed before recording it as a security violation
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
The likelihood that a threat can result into an incident. This is the overall risk of a system

29. Compartmentalization
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Access request by a subject to an object is mediated each time and every time.

30. 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

31. 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
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

32. EALs levels
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
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
Design to mitigate any single source of complete compromise
Confidentiality - Integrity - Availability

33. Single Loss Expectancy (SLE)
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
estimate potential loss of a single incident: SLE = Asset value * EF(%)

34. Auditing
estimate potential loss of a single incident: SLE = Asset value * EF(%)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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

35. Categories of controls
Security controls applied to mitigate a threat before it materializes
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
Technical - Management - Operational
Number of incidents that can be expected in a year

36. Challenges in implementing auditing/logging
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

37. After identification step is...
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
OWASP - ITIL
Authentication
Secure applicatios running on secure hosts (systems) in a secure network

38. Authorization
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

39. FIPS 201
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

40. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Indicator of magnitude risk in a year ALE = SLE * ARO

41. Popular guides developed by OWASP
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Development guide - Code Review Guide - Testing Guide
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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.

42. Accountability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Support policies at a granular and specific level - Can be characterized as internal and external
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

43. Benefits of coding standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

44. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
Development guide - Code Review Guide - Testing Guide
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

45. Open design
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

46. Holistic Security in software
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

47. Threat
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk remains after the implementation of mitigating security controls
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

48. ISO/IEC 27003
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
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
Still under development - aimsto address ISMS implementation guidance

49. ISO/IEC 15408
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 Common Criteria to evaluate IT security product
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security controls applied after a threat has been materialized

50. NIST standards related to software security
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of 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