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. Threat
Covers the necessary procedures and tools to validate software assurance
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

2. General security concept
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Support policies at a granular and specific level - Can be characterized as internal and external
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

3. OWASP Top 10
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Periodic publication by OWASP for top 10 Web application security vulnerabilites

4. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
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

5. After identification step is...
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
Authentication
OWASP - ITIL
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

6. Properties of secure software
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Risk remains after the implementation of mitigating security controls

7. ISO/IEC 27002:2005
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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

8. Categories of controls
Access request by a subject to an object is mediated each time and every time.
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
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
Technical - Management - Operational

9. Develop hack resilient software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

10. Authorization
Security controls applied after a threat has been materialized
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Risk remains after the implementation of mitigating security controls

11. Safeguards
Secure applicatios running on secure hosts (systems) in a secure network
Support policies at a granular and specific level - Can be characterized as internal and external
Security controls applied to mitigate a threat before it materializes
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

12. Configurations Parameters 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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

13. ISO/IEC 15408
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Provides Common Criteria to evaluate IT security product
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

14. Error and exception management
Development guide - Code Review Guide - Testing Guide
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

15. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Technical - Management - Operational
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

16. Operation Controls
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

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

18. Annual Loss Expectancy (ALE)
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Support policies at a granular and specific level - Can be characterized as internal and external
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

19. Availability
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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.
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
Security controls applied to mitigate a threat before it materializes

20. 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Support policies at a granular and specific level - Can be characterized as internal and external
Still under development - aimsto address ISMS implementation guidance

21. Risk management process
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

22. Take-Grant Model
Covers the necessary procedures and tools to validate software assurance
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Risk remains after the implementation of mitigating security controls
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

23. Complete mediation
Access request by a subject to an object is mediated each time and every time.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

24. Security design principles
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

25. Accountability
Provides Common Criteria to evaluate IT security product
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security controls applied to mitigate a threat before it materializes

26. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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

27. ISO/IEC 27005:2008
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Covers the necessary procedures and tools to validate software assurance

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

29. Open design
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
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied to mitigate a threat before it materializes
Support policies at a granular and specific level - Can be characterized as internal and external

30. OWASP testing guide
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Covers the necessary procedures and tools to validate software assurance
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

31. FIPS 197 (Advance Cryptographic standards - AES)
Predetermined number of user error allowed before recording it as a security violation
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

32. Counter measures
Security controls applied after a threat has been materialized
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

33. Access Matrix model

34. Benefits of coding standards
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Authentication
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

35. PCI DSS
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
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
Authentication

36. Security Policies

37. Single Loss Expectancy (SLE)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Provides Common Criteria to evaluate IT security product
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

38. Multifactor authentication
Confidentiality - Integrity - Availability
Covers the necessary procedures and tools to validate software assurance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

39. Security Standards
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
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Support policies at a granular and specific level - Can be characterized as internal and external
Authentication

40. Phsychological acceptability
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
Security functionality is easy to use and transparent
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Number of incidents that can be expected in a year

41. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
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
Still under development - aimsto address ISMS implementation guidance

42. Compartmentalization
Provides Common Criteria to evaluate IT security product
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

43. Information Security Models
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
OWASP - ITIL
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

44. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Development guide - Code Review Guide - Testing Guide
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

45. OCTAVE
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk remains after the implementation of mitigating security controls

46. Confidentiality
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Confidentiality - Integrity - Availability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Protection against unauthorized information disclosure. It helps maintaining privacy

47. Clipping level
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Predetermined number of user error allowed before recording it as a security violation
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

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

49. STRIDE
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Number of incidents that can be expected in a year

50. ISO/IEC 27006:2007
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Support for accreditation and certification bodies that audit and certify ISMS
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