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. Examples of Security Standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

2. Complete mediation
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Risk remains after the implementation of mitigating security controls
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Access request by a subject to an object is mediated each time and every time.

3. ISO/IEC 15408
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Provides Common Criteria to evaluate IT security product

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

5. Operation Controls
OWASP - ITIL
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

6. Core Security Concept
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Confidentiality - Integrity - Availability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

7. Availability
Access request by a subject to an object is mediated each time and every time.
Indicator of magnitude risk in a year ALE = SLE * ARO
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.
Still under development - aimsto address ISMS implementation guidance

8. ISO/IEC 27003
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Still under development - aimsto address ISMS implementation guidance
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

9. Threat
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security functionality is easy to use and transparent

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

11. Annual Loss Expectancy (ALE)
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

12. Integrity
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security functionality is easy to use and transparent
Access request by a subject to an object is mediated each time and every time.
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent

13. Security Policies

14. Security profile of a software
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

15. Risk management process
Still under development - aimsto address ISMS implementation guidance
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
Covers the necessary procedures and tools to validate software assurance
Access request by a subject to an object is mediated each time and every time.

16. Economy of mechanism
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Security controls applied after a threat has been materialized
Secure applicatios running on secure hosts (systems) in a secure network

17. ISO/IEC 9216
Secure applicatios running on secure hosts (systems) in a secure network
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

18. OWASP Code Review Guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

19. FIPS 197 (Advance Cryptographic standards - AES)
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

20. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Still under development - aimsto address ISMS implementation guidance
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

21. Popular guides developed by OWASP
Security functionality is easy to use and transparent
Development guide - Code Review Guide - Testing Guide
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

22. OWASP testing guide
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security controls applied after a threat has been materialized
Covers the necessary procedures and tools to validate software assurance

23. Challenges in implementing auditing/logging
Access request by a subject to an object is mediated each time and every time.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

24. EALs levels
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Number of incidents that can be expected in a year
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

25. Clipping level
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Predetermined number of user error allowed before recording it as a security violation

26. Common best practices significant to Sofware Security
OWASP - ITIL
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Covers the necessary procedures and tools to validate software assurance

27. OWASP Top 10
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
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

28. After identification step is...
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Access request by a subject to an object is mediated each time and every time.
Authentication

29. Least privilege
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

30. Multifactor authentication
OWASP - ITIL
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on 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 controls applied to mitigate a threat before it materializes

31. Security design principles
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
Design to mitigate any single source of complete compromise
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

32. STRIDE
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

33. FIPS 201
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Security functionality is easy to use and transparent
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

34. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Development guide - Code Review Guide - Testing Guide

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

36. Properties of secure software
Security controls applied after a threat has been materialized
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

37. Flaw Hypothesis Method (FHM)
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.
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

38. Security Risk Management Discipline
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security controls applied after a threat has been materialized
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

39. Security Standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Support policies at a granular and specific level - Can be characterized as internal and external
Protection against unauthorized information disclosure. It helps maintaining privacy
Security controls applied after a threat has been materialized

40. Error and exception management
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Indicator of magnitude risk in a year ALE = SLE * ARO
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

41. Residual Risk
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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.
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

42. Auditing
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
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
Support policies at a granular and specific level - Can be characterized as internal and external
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

43. Open design
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
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

44. Non Repudiation
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Provides Common Criteria to evaluate IT security product

45. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

46. FIPS140-2 (Security requirement for cryptographic modules)
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

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

48. Security Controls
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
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
Authentication

49. 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
Design to mitigate any single source of complete compromise
Secure applicatios running on secure hosts (systems) in a secure network

50. OCTAVE
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability