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. Core Security Concept
Development guide - Code Review Guide - Testing Guide
Technical - Management - Operational
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Confidentiality - Integrity - Availability

2. Availability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

3. Clipping level
Covers the necessary procedures and tools to validate software assurance
Predetermined number of user error allowed before recording it as a security violation
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Still under development - aimsto address ISMS implementation guidance

4. Security Risk Management Discipline
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

5. Implementation challenges
Provides Common Criteria to evaluate IT security product
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

6. Multifactor authentication
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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

7. Software security risk management methodologies
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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 after a threat has been materialized

8. Take-Grant Model
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
Provides Common Criteria to evaluate IT security product
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

9. After identification step is...
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Authentication
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

10. Annual Loss Expectancy (ALE)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Indicator of magnitude risk in a year ALE = SLE * ARO
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

11. Develop hack resilient software
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m

12. OWASP Top 10
Number of incidents that can be expected in a year
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

13. Authentication
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

14. DREAD
Covers the necessary procedures and tools to validate software assurance
OWASP - ITIL
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

15. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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 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

16. Vulnerability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

17. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Support policies at a granular and specific level - Can be characterized as internal and external
Confidentiality - Integrity - Availability

18. Residual Risk
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Risk remains after the implementation of mitigating security controls
Support policies at a granular and specific level - Can be characterized as internal and external

19. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Security functionality is easy to use and transparent

20. General security concept
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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.

21. Risk management process
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

22. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Authentication

23. Management Controls
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

24. FIPS 197 (Advance Cryptographic standards - AES)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

25. Security Controls
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
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
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 for accreditation and certification bodies that audit and certify ISMS

26. Annual Rate of Occurence (ARO)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Number of incidents that can be expected in a year
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. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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
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

28. Single point failure
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
Secure applicatios running on secure hosts (systems) in a secure network
Design to mitigate any single source of complete compromise
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

29. OWASP development guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

30. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

31. Security Standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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 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
Support policies at a granular and specific level - Can be characterized as internal and external

32. Session Management
Design to mitigate any single source of complete compromise
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

33. Least common mechanism
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

34. ISO /IEC 27000:2009
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

35. Least privilege
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 the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Support for accreditation and certification bodies that audit and certify ISMS

36. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Design to mitigate any single source of complete compromise
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

37. OCTAVE
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
Confidentiality - Integrity - Availability
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

38. ISO/IEC 27003
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
Access request by a subject to an object is mediated each time and every time.
Still under development - aimsto address ISMS implementation guidance
Support for accreditation and certification bodies that audit and certify ISMS

39. Security profile of a software
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Design to mitigate any single source of complete compromise

40. Security design principles
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Support policies at a granular and specific level - Can be characterized as internal and external
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

41. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Risk remains after the implementation of mitigating security controls

42. ISO/IEC 15408
Covers the necessary procedures and tools to validate software assurance
Provides Common Criteria to evaluate IT security product
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

43. Auditing
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
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
Predetermined number of user error allowed before recording it as a security violation
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

44. Phsychological acceptability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security functionality is easy to use and transparent
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Risk remains after the implementation of mitigating security controls

45. Common best practices significant to Sofware Security
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
OWASP - ITIL

46. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Confidentiality - Integrity - Availability

47. Safeguards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied to mitigate a threat before it materializes
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

48. Security Policies

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

50. PCI DSS
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors