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

2. OWASP testing guide
Security controls applied after a threat has been materialized
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
Covers the necessary procedures and tools to validate software assurance
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

3. Benefits of coding standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

4. ISO/IEC 9216
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

5. Risk management process
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

6. Integrity
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
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
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.

7. Operation Controls
Protection against unauthorized information disclosure. It helps maintaining privacy
Access request by a subject to an object is mediated each time and every time.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Predetermined number of user error allowed before recording it as a security violation

8. Authorization
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
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

9. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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 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

10. Core Security Concept
Risk remains after the implementation of mitigating security controls
Confidentiality - Integrity - Availability
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

11. OCTAVE
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

12. Least privilege
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
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
Security functionality is easy to use and transparent

13. Counter measures
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Security controls applied after a threat has been materialized
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

14. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Access request by a subject to an object is mediated each time and every time.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

15. ISO /IEC 27000:2009
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

16. Least common mechanism
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
Authentication
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

17. Authentication
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
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Security controls applied after a threat has been materialized

18. Develop hack resilient software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Authentication
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

19. Accountability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
OWASP - ITIL
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

20. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

21. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Protection against unauthorized information disclosure. It helps maintaining privacy
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
The likelihood that a threat can result into an incident. This is the overall risk of a system

22. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
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

23. Security design principles
Protection against unauthorized information disclosure. It helps maintaining privacy
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

24. OWASP Top 10
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

25. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Technical - Management - Operational

26. OWASP development guide
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

27. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Support for accreditation and certification bodies that audit and certify ISMS

28. Auditing
Number of incidents that can be expected in a year
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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

29. OWASP Code Review Guide
Confidentiality - Integrity - Availability
Risk remains after the implementation of mitigating security controls
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

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

31. Security Risk Management Discipline
Support for accreditation and certification bodies that audit and certify ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

32. STRIDE
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

33. Flaw Hypothesis Method (FHM)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Security controls applied to mitigate a threat before it materializes
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

34. After identification step is...
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Authentication

35. ISO/IEC 27001:2005
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
Predetermined number of user error allowed before recording it as a security violation
Security functionality is easy to use and transparent

36. Single point failure
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Design to mitigate any single source of complete compromise

37. Software security risk management methodologies
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

38. Error and exception management
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

39. Access Matrix model

40. General security concept
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Support for accreditation and certification bodies that audit and certify ISMS

41. Implementation challenges
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

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

43. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Secure applicatios running on secure hosts (systems) in a secure network

44. Residual Risk
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
Support policies at a granular and specific level - Can be characterized as internal and external
Risk remains after the implementation of mitigating security controls

45. EALs levels
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
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

46. Security profile of a software
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 functionality is easy to use and transparent
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

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

48. PCI DSS
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

49. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Risk remains after the implementation of mitigating security controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

50. Security Controls
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Predetermined number of user error allowed before recording it as a security violation
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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