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. General security concept
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

2. Security design principles
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
Access request by a subject to an object is mediated each time and every time.
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

3. ISO/IEC 27001:2005
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

4. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

5. ISO/IEC 9216
Predetermined number of user error allowed before recording it as a security violation
Security functionality is easy to use and transparent
Number of incidents that can be expected in a year
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

6. Properties of secure software
Number of incidents that can be expected in a year
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 controls applied after a threat has been materialized
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

7. Take-Grant Model
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

8. ISO/IEC 21827:2008
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

9. Auditing
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

10. Annual Loss Expectancy (ALE)
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Indicator of magnitude risk in a year ALE = SLE * ARO

11. FIPS 197 (Advance Cryptographic standards - AES)
Provides Common Criteria to evaluate IT security product
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Number of incidents that can be expected in a year

12. Integrity
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Technical - Management - Operational
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

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

14. Complete mediation
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Development guide - Code Review Guide - Testing Guide
Access request by a subject to an object is mediated each time and every time.

15. Residual Risk
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Protection against unauthorized information disclosure. It helps maintaining privacy
Risk remains after the implementation of mitigating security controls

16. Compartmentalization
Security controls applied after a threat has been materialized
Predetermined number of user error allowed before recording it as a security violation
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

17. Non Repudiation
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Still under development - aimsto address ISMS implementation guidance
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

18. Operation Controls
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

19. Benefits of coding standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Number of incidents that can be expected in a year
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

20. Threat
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

21. Counter measures
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Security controls applied after a threat has been materialized
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

22. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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

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

24. Core Security Concept
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
Confidentiality - Integrity - Availability
Number of incidents that can be expected in a year
Security controls applied after a threat has been materialized

25. Access Matrix model

26. ISO/IEC 27003
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Still under development - aimsto address ISMS implementation guidance

27. Single point failure
Design to mitigate any single source of complete compromise
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Technical - Management - Operational
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. 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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Provides Common Criteria to evaluate IT security product

29. After identification step is...
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

30. Develop hack resilient software
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

31. Security Policies

32. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Provides Common Criteria to evaluate IT security product
Security controls applied to mitigate a threat before it materializes
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

33. Confidentiality
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
Protection against unauthorized information disclosure. It helps maintaining privacy
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

34. Least common mechanism
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
The likelihood that a threat can result into an incident. This is the overall risk of a system
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

35. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

36. Annual Rate of Occurence (ARO)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Number of incidents that can be expected in a year
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

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

38. Safeguards
Security controls applied to mitigate a threat before it materializes
OWASP - ITIL
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

39. Authorization
Design to mitigate any single source of complete compromise
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Aims at 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
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

40. 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Predetermined number of user error allowed before recording it as a security violation
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

41. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
The likelihood that a threat can result into an incident. This is the overall risk of a system

42. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
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
Design to mitigate any single source of complete compromise

43. OCTAVE
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Security functionality is easy to use and transparent

44. Vulnerability
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

45. Software security risk management methodologies
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

46. Availability
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
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.
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

47. 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

48. ISO /IEC 27000:2009
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Still under development - aimsto address ISMS implementation guidance
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

49. 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:
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Security 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
Predetermined number of user error allowed before recording it as a security violation

50. Categories of controls
Predetermined number of user error allowed before recording it as a security violation
Periodic publication by OWASP for top 10 Web application security vulnerabilites
The likelihood that a threat can result into an incident. This is the overall risk of a system
Technical - Management - Operational