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 27003
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Authentication
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

2. Security profile of a software
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security controls applied after a threat has been materialized
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

3. Non Repudiation
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
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
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 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

4. 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.
The likelihood that a threat can result into an incident. This is the overall risk of a system
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

5. Session Management
Security functionality is easy to use and transparent
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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

6. DREAD
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

7. Security Risk Management Discipline
Confidentiality - Integrity - Availability
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

8. Core Security Concept
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)
Confidentiality - Integrity - Availability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

9. Security Controls
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
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
Authentication

10. OCTAVE
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

11. ISO/IEC 15408
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
Provides Common Criteria to evaluate IT security product
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

12. Security Policies

13. 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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Risk remains after the implementation of mitigating security controls
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

14. Access Matrix model

15. Common best practices significant to Sofware Security
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
OWASP - ITIL
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

16. Take-Grant Model
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

17. ISO/IEC 27005:2008
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Support policies at a granular and specific level - Can be characterized as internal and external
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

18. Holistic Security in software
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

19. Properties of secure software
Support for accreditation and certification bodies that audit and certify ISMS
Access request by a subject to an object is mediated each time and every time.
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

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

21. Phsychological acceptability
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
Authentication
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

22. ISO/IEC 21827:2008
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Still under development - aimsto address ISMS implementation guidance
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

23. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Access request by a subject to an object is mediated each time and every time.
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

24. Confidentiality
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Confidentiality - Integrity - Availability
Protection against unauthorized information disclosure. It helps maintaining privacy
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

25. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

26. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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

27. Compartmentalization
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

28. Economy of mechanism
Security functionality is easy to use and transparent
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

29. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Security controls applied to mitigate a threat before it materializes
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
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

30. Management 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

31. Safeguards
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Security controls applied to mitigate a threat before it materializes
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
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.

32. 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Protection against unauthorized information disclosure. It helps maintaining privacy

33. Categories of controls
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Technical - Management - Operational
Covers the necessary procedures and tools to validate software assurance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

34. Popular guides developed by OWASP
The likelihood that a threat can result into an incident. This is the overall risk of a system
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Development guide - Code Review Guide - Testing Guide

35. EALs levels
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
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
Confidentiality - Integrity - Availability

36. Open design
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
Security functionality is easy to use and transparent
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
Protection against unauthorized information disclosure. It helps maintaining privacy

37. Least privilege
Number of incidents that can be expected in a year
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

38. ISO/IEC 27001:2005
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 requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
OWASP - ITIL

39. Single point failure
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
Design to mitigate any single source of complete compromise
Access request by a subject to an object is mediated each time and every time.
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

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

41. Configurations Parameters 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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

42. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

43. ISO/IEC 9216
Technical - Management - Operational
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

44. 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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

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

46. Security design principles
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

47. Annual Rate of Occurence (ARO)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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.
Number of incidents that can be expected in a year

48. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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:

49. 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
Confidentiality - Integrity - Availability
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

50. Annual Loss Expectancy (ALE)
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 likelihood that a threat can result into an incident. This is the overall risk of a system
Indicator of magnitude risk in a year ALE = SLE * ARO