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. 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

2. DREAD
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

3. 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
Security functionality is easy to use and transparent
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

4. ISO/IEC 21827:2008
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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

5. Least common mechanism
Secure applicatios running on secure hosts (systems) in a secure network
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Protection against unauthorized information disclosure. It helps maintaining privacy

6. Integrity
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Security functionality is easy to use and transparent

7. OWASP Code Review Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security controls applied to mitigate a threat before it materializes
Covers the necessary procedures and tools to validate software assurance
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. Safeguards
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Security controls applied to mitigate a threat before it materializes
Confidentiality - Integrity - Availability
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

9. Authorization
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

10. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

11. Popular guides developed by OWASP
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Development guide - Code Review Guide - Testing Guide
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

12. Flaw Hypothesis Method (FHM)
Risk remains after the implementation of mitigating security 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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

13. OWASP development guide
Protection against unauthorized information disclosure. It helps maintaining privacy
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
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

14. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Indicator of magnitude risk in a year ALE = SLE * ARO

15. Common best practices significant to Sofware Security
Security controls applied after a threat has been materialized
Authentication
OWASP - ITIL
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

16. Annual Rate of Occurence (ARO)
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

17. Categories of controls
Technical - Management - Operational
Risk remains after the implementation of mitigating security controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

18. Security design principles
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
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Security 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
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

19. Security Policies

20. Risk management process
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Predetermined number of user error allowed before recording it as a security violation
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

21. FIPS 197 (Advance Cryptographic standards - AES)
Secure applicatios running on secure hosts (systems) in a secure network
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

22. Clipping level
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
OWASP - ITIL
Predetermined number of user error allowed before recording it as a security violation

23. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

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

25. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Covers the necessary procedures and tools to validate software assurance

26. OCTAVE
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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 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
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

27. Phsychological acceptability
Security functionality is easy to use and transparent
Design to mitigate any single source of complete compromise
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk remains after the implementation of mitigating security controls

28. Least privilege
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

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

30. After identification step is...
OWASP - ITIL
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Security controls applied after a threat has been materialized
Authentication

31. ISO/IEC 9216
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

32. Residual Risk
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
Risk remains after the implementation of mitigating security controls
Provides Common Criteria to evaluate IT security product
Access request by a subject to an object is mediated each time and every time.

33. Security profile of a software
OWASP - ITIL
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

34. Multifactor authentication
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Number of incidents that can be expected in a year
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

35. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Development guide - Code Review Guide - Testing Guide
Confidentiality - Integrity - Availability

36. Configurations Parameters Management
Security controls applied to mitigate a threat before it materializes
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

37. 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Development guide - Code Review Guide - Testing Guide

38. Exposure factor (EF)
Provides Common Criteria to evaluate IT security product
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Confidentiality - Integrity - Availability
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

39. Total Risk
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Security controls applied to mitigate a threat before it materializes
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

40. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

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

42. Compartmentalization
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

43. Complete mediation
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Access request by a subject to an object is mediated each time and every time.

44. Threat
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security controls applied after a threat has been materialized

45. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

46. Properties of secure software
Indicator of magnitude risk in a year ALE = SLE * ARO
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

47. ISO/IEC 27005:2008
Number of incidents that can be expected in a year
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

48. Software security risk management methodologies
Development guide - Code Review Guide - Testing Guide
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Support policies at a granular and specific level - Can be characterized as internal and external
Technical - Management - Operational

49. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Authentication

50. Holistic Security in software
Confidentiality - Integrity - Availability
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Secure applicatios running on secure hosts (systems) in a secure network