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 27005:2008
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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. Popular guides developed by OWASP
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
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
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

3. FIPS140-2 (Security requirement for cryptographic modules)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

4. Annual Rate of Occurence (ARO)
Indicator of magnitude risk in a year ALE = SLE * ARO
Predetermined number of user error allowed before recording it as a security violation
Number of incidents that can be expected in a year
Covers the necessary procedures and tools to validate software assurance

5. ISO/IEC 15408
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational
Security functionality is easy to use and transparent

6. Phsychological acceptability
Security functionality is easy to use and transparent
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

7. OWASP testing guide
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
Covers the necessary procedures and tools to validate software assurance
Authentication
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

8. Risk management process
Provides Common Criteria to evaluate IT security product
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

9. ISO/IEC 27002:2005
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
Risk remains after the implementation of mitigating security controls
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

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

11. Flaw Hypothesis Method (FHM)
Security controls applied to mitigate a threat before it materializes
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

12. Core Security Concept
Confidentiality - Integrity - Availability
Security controls applied after a threat has been materialized
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

13. Implementation challenges
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Authentication
Support for accreditation and certification bodies that audit and certify ISMS

14. Vulnerability
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Covers the necessary procedures and tools to validate software assurance
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

15. Information Security Models
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Security controls applied to mitigate a threat before it materializes

16. ISO/IEC 27006:2007
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
Risk remains after the implementation of mitigating security controls
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Support for accreditation and certification bodies that audit and certify ISMS

17. Authorization
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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. Properties of secure software
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

19. Open design
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Confidentiality - Integrity - Availability

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

21. Management Controls
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

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

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

24. ISO/IEC 27003
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Still under development - aimsto address ISMS implementation guidance
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

25. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Authentication
Provides Common Criteria to evaluate IT security product
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

26. Technical Controls
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Design to mitigate any single source of complete compromise
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

27. 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
Authentication
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

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

29. Configurations Parameters Management
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Security controls applied to mitigate a threat before it materializes
Authentication

30. NIST standards related to software security
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
OWASP - ITIL
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

31. ISO /IEC 27000:2009
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Support policies at a granular and specific level - Can be characterized as internal and external

32. Software security risk management methodologies
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

33. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Security controls applied after a threat has been materialized
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

34. Security Risk Management Discipline
Provides Common Criteria to evaluate IT security product
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

35. Operation Controls
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Number of incidents that can be expected in a year
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

36. Confidentiality
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Protection against unauthorized information disclosure. It helps maintaining privacy

37. Economy of mechanism
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

38. Security profile of a software
Security functionality is easy to use and transparent
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

39. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Support policies at a granular and specific level - Can be characterized as internal and external
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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. Counter measures
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Security controls applied after a threat has been materialized
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

41. Complete mediation
Access request by a subject to an object is mediated each time and every time.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

42. Least common mechanism
Number of incidents that can be expected in a year
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
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

43. FIPS 197 (Advance Cryptographic standards - AES)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

44. OWASP development guide
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
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

45. Vulnerabilities repositories
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

46. Common best practices significant to Sofware Security
OWASP - ITIL
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Number of incidents that can be expected in a year

47. DREAD
Number of incidents that can be expected in a year
Security controls applied after a threat has been materialized
Authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

48. 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
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

49. Accountability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Access request by a subject to an object is mediated each time and every time.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

50. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security functionality is easy to use and transparent
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities