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. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Still under development - aimsto address ISMS implementation guidance
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

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

3. Complete mediation
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
Access request by a subject to an object is mediated each time and every time.
Security controls applied after a threat has been materialized
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

4. PCI DSS
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

5. OWASP Code Review Guide
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

6. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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

7. DREAD
Security functionality is easy to use and transparent
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

8. OWASP testing guide
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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.
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

9. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Protection against unauthorized information disclosure. It helps maintaining privacy
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

10. Compartmentalization
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Still under development - aimsto address ISMS implementation guidance
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

11. FIPS 197 (Advance Cryptographic standards - AES)
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

12. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

13. 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
Confidentiality - Integrity - Availability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

14. Annual Loss Expectancy (ALE)
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Indicator of magnitude risk in a year ALE = SLE * ARO

15. ISO/IEC 15408
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Provides Common Criteria to evaluate IT security product
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

16. Operation Controls
Security controls applied to mitigate a threat before it materializes
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

17. STRIDE
Covers the necessary procedures and tools to validate software assurance
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
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

18. Phsychological acceptability
Security functionality is easy to use and transparent
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

19. Exposure factor (EF)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Design to mitigate any single source of complete compromise
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

20. Software security risk management methodologies
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security controls applied to mitigate a threat before it materializes
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

21. Vulnerabilities repositories
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Predetermined number of user error allowed before recording it as a security violation

22. Technical Controls
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
Secure applicatios running on secure hosts (systems) in a secure network
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

23. Multifactor authentication
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

24. ISO/IEC 27003
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
Still under development - aimsto address ISMS implementation guidance
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Technical - Management - Operational

25. ISO/IEC 9216
Authentication
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

26. Security Controls
Secure applicatios running on secure hosts (systems) in a secure network
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

27. Error and exception 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
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

28. OCTAVE
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Risk remains after the implementation of mitigating security controls
Support policies at a granular and specific level - Can be characterized as internal and external

29. Total Risk
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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.
The likelihood that a threat can result into an incident. This is the overall risk of a system
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

30. ISO /IEC 27000:2009
Covers the necessary procedures and tools to validate software assurance
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

31. Confidentiality
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

32. OWASP Top 10
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
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

33. Authorization
Covers the necessary procedures and tools to validate software assurance
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

34. Annual Rate of Occurence (ARO)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Number of incidents that can be expected in a year
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

35. Categories of controls
Covers the necessary procedures and tools to validate software assurance
Confidentiality - Integrity - Availability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Technical - Management - Operational

36. Common best practices significant to Sofware Security
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
OWASP - ITIL

37. Popular guides developed by OWASP
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Development guide - Code Review Guide - Testing Guide
Provides Common Criteria to evaluate IT security product

38. Develop hack resilient software
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

39. Security profile of a software
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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. Security Policies

41. Risk management process
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

42. 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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

43. Clipping level
Access request by a subject to an object is mediated each time and every time.
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
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
Predetermined number of user error allowed before recording it as a security violation

44. Examples of Security Standards
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

45. Holistic Security in software
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Secure applicatios running on secure hosts (systems) in a secure network
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

46. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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 SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

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

48. Least privilege
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
Provides Common Criteria to evaluate IT security product
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Periodic publication by OWASP for top 10 Web application security vulnerabilites

49. ISO/IEC 27001:2005
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

50. FIPS 201
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Support for accreditation and certification bodies that audit and certify ISMS
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