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. STRIDE
Confidentiality - Integrity - Availability
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 policies at a granular and specific level - Can be characterized as internal and external
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

2. OWASP testing guide
Development guide - Code Review Guide - Testing Guide
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
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.
Covers the necessary procedures and tools to validate software assurance

3. Authorization
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Risk 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

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

5. Counter measures
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied after a threat has been materialized
Security controls applied to mitigate a threat before it materializes
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

6. Residual Risk
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
Risk remains after the implementation of mitigating security controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

7. 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security controls applied to mitigate a threat before it materializes

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

9. Least common mechanism
OWASP - ITIL
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

10. Security Standards
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
Support policies at a granular and specific level - Can be characterized as internal and external
Still under development - aimsto address ISMS implementation guidance

11. 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:
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
The likelihood that a threat can result into an incident. This is the overall risk of a system

12. Flaw Hypothesis Method (FHM)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

13. Single Loss Expectancy (SLE)
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
Risk remains after the implementation of mitigating security controls
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Periodic publication by OWASP for top 10 Web application security vulnerabilites

14. 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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

15. Availability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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.

16. Least privilege
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)

17. After identification step is...
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Authentication
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

18. Software security risk management methodologies
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
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

19. Common best practices significant to Sofware Security
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Confidentiality - Integrity - Availability
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
OWASP - ITIL

20. Develop hack resilient software
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

21. Economy of mechanism
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

22. ISO/IEC 27006:2007
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
Access request by a subject to an object is mediated each time and every time.
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied after a threat has been materialized

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

24. Threat
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
Security controls applied after a threat has been materialized
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

25. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Still under development - aimsto address ISMS implementation guidance

26. Properties of secure software
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
Still under development - aimsto address ISMS implementation guidance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

27. Integrity
Security controls applied to mitigate a threat before it materializes
Provides Common Criteria to evaluate IT security product
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
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

28. 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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Number of incidents that can be expected in a year

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

30. Challenges in implementing auditing/logging
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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. Multifactor authentication
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

32. Confidentiality
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Protection against unauthorized information disclosure. It helps maintaining privacy
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

33. FIPS 201
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security controls applied to mitigate a threat before it materializes
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

34. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

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

36. Management Controls
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:
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

37. EALs levels
OWASP - ITIL
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

38. Phsychological acceptability
Security functionality is easy to use and transparent
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
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

39. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Number of incidents that can be expected in a year
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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

40. Security profile of a software
Predetermined number of user error allowed before recording it as a security violation
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

41. Annual Rate of Occurence (ARO)
Risk remains after the implementation of mitigating security controls
Number of incidents that can be expected in a year
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
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

42. OWASP Top 10
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

43. Core Security Concept
Indicator of magnitude risk in a year ALE = SLE * ARO
Confidentiality - Integrity - Availability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

44. ISO /IEC 27000:2009
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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

45. FIPS 197 (Advance Cryptographic standards - AES)
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
Support for accreditation and certification bodies that audit and certify ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

46. Take-Grant Model
Development guide - Code Review Guide - Testing Guide
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

47. Safeguards
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Security controls applied to mitigate a threat before it materializes
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

48. Security Controls
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security controls applied after a threat has been materialized
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
Number of incidents that can be expected in a year

49. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
The likelihood that a threat can result into an incident. This is the overall risk of a system
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

50. Error and exception management
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them