Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Subjects : certifications, csslp, it-skills

Instructions:

Answer 50 questions in 20 minutes. 2 minutes extra for reading the instructions.
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. FIPS140-2 (Security requirement for cryptographic modules)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Confidentiality - Integrity - Availability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

2. Threat
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

3. Single Loss Expectancy (SLE)
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

4. Counter measures
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Security controls applied after a threat has been materialized
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Confidentiality - Integrity - Availability

5. ISO/IEC 9216
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

6. Benefits of coding standards
Design to mitigate any single source of complete compromise
Still under development - aimsto address ISMS implementation guidance
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

7. OWASP Top 10
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Still under development - aimsto address ISMS implementation guidance
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

8. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Predetermined number of user error allowed before recording it as a security violation

9. Configurations Parameters 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
Support for accreditation and certification bodies that audit and certify ISMS
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

10. 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
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
Technical - Management - Operational
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. Annual Loss Expectancy (ALE)
Confidentiality - Integrity - Availability
Indicator of magnitude risk in a year ALE = SLE * ARO
Security controls applied to mitigate a threat before it materializes
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

12. Accountability
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security functionality is easy to use and transparent

13. Multifactor authentication
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

14. Technical Controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Support policies at a granular and specific level - Can be characterized as internal and external

15. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Authentication
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

16. 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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

17. Least privilege
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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
Predetermined number of user error allowed before recording it as a security violation

18. Flaw Hypothesis Method (FHM)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

19. Security profile of a software
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
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
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

20. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

21. Access Matrix model

22. Safeguards
Security controls applied to mitigate a threat before it materializes
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
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

23. ISO/IEC 27001:2005
Number of incidents that can be expected in a year
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
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

24. OWASP Code Review Guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

25. ISO/IEC 27006:2007
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Provides Common Criteria to evaluate IT security product

26. Annual Rate of Occurence (ARO)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Number of incidents that can be expected in a year

27. ISO /IEC 27000:2009
Secure applicatios running on secure hosts (systems) in a secure network
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
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
Design to mitigate any single source of complete compromise

28. ISO/IEC 27005:2008
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
OWASP - ITIL

29. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Secure applicatios running on secure hosts (systems) in a secure network
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

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

31. Integrity
Development guide - Code Review Guide - Testing Guide
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
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

32. ISO/IEC 15408
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Provides Common Criteria to evaluate IT security product
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
Security functionality is easy to use and transparent

33. Risk management process
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 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
Secure applicatios running on secure hosts (systems) in a secure network
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

34. Auditing
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
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

35. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

36. Phsychological acceptability
OWASP - ITIL
Security functionality is easy to use and transparent
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

37. Software security risk management methodologies
Number of incidents that can be expected in a year
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Authentication
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

38. NIST standards related to software security
Predetermined number of user error allowed before recording it as a security violation
Support for accreditation and certification bodies that audit and certify ISMS
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
Still under development - aimsto address ISMS implementation guidance

39. ISO/IEC 27003
Predetermined number of user error allowed before recording it as a security violation
Still under development - aimsto address ISMS implementation guidance
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.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

40. Categories of controls
The likelihood that a threat can result into an incident. This is the overall risk of a system
Security controls applied to mitigate a threat before it materializes
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
Technical - Management - Operational

41. Develop hack resilient software
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Secure applicatios running on secure hosts (systems) in a secure network
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

42. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

43. Information Security Models
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

44. OCTAVE
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

45. Vulnerability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

46. Vulnerabilities repositories
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Authentication
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

47. PCI DSS
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
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

48. Popular guides developed by OWASP
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Development guide - Code Review Guide - Testing Guide

49. Authorization
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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:

50. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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