Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Subjects : certifications, csslp, it-skills

Instructions:

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

2. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Still under development - aimsto address ISMS implementation guidance
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
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

3. Complete mediation
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
OWASP - ITIL
Access request by a subject to an object is mediated each time and every time.
Confidentiality - Integrity - Availability

4. Integrity
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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 the architecture and technical requirements for a common identified standard for federal employee and contractors
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

5. ISO/IEC 21827:2008
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

6. ISO/IEC 27001:2005
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

7. 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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Indicator of magnitude risk in a year ALE = SLE * ARO
Periodic publication by OWASP for top 10 Web application security vulnerabilites

8. ISO/IEC 27005:2008
Security controls applied to mitigate a threat before it materializes
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

9. Accountability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
The likelihood that a threat can result into an incident. This is the overall risk of a system
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Authentication

10. ISO/IEC 27003
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Still under development - aimsto address ISMS implementation guidance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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

11. OWASP Code Review Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Still under development - aimsto address ISMS implementation guidance
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

12. FIPS 197 (Advance Cryptographic standards - AES)
Security controls applied to mitigate a threat before it materializes
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

13. Categories of controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Technical - Management - Operational
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

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

15. ISO/IEC 27006:2007
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
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:
Support for accreditation and certification bodies that audit and certify ISMS

16. 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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.

17. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Indicator of magnitude risk in a year ALE = SLE * ARO
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

18. Technical Controls
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
Support policies at a granular and specific level - Can be characterized as internal and external
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

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

20. Safeguards
Covers the necessary procedures and tools to validate software assurance
Security controls applied to mitigate a threat before it materializes
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Indicator of magnitude risk in a year ALE = SLE * ARO

21. Single Loss Expectancy (SLE)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

22. Least common mechanism
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

23. Software security risk management methodologies
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

24. OWASP development guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

25. Clipping level
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
Predetermined number of user error allowed before recording it as a security violation
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

26. STRIDE
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
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

27. Open design
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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

28. Phsychological acceptability
Security functionality is easy to use and transparent
Support policies at a granular and specific level - Can be characterized as internal and external
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 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

29. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

30. Economy of mechanism
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Access request by a subject to an object is mediated each time and every time.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

31. Flaw Hypothesis Method (FHM)
Security controls applied to mitigate a threat before it materializes
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

32. Non Repudiation
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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 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

33. Operation Controls
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
Number of incidents that can be expected in a year
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

34. Availability
Number of incidents that can be expected in a year
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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.

35. Security Policies

36. Access Matrix model

37. Properties of secure software
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
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

38. Develop hack resilient software
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Predetermined number of user error allowed before recording it as a security violation
Still under development - aimsto address ISMS implementation guidance

39. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
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

40. OCTAVE
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Support policies at a granular and specific level - Can be characterized as internal and external
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

41. Least privilege
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

42. ISO/IEC 27002:2005
The likelihood that a threat can result into an incident. This is the overall risk of a 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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

43. Residual Risk
Risk remains after the implementation of mitigating security 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.
Covers the necessary procedures and tools to validate software assurance
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

44. Take-Grant Model
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

45. Authentication
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Design to mitigate any single source of complete compromise
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

46. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

47. Auditing
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Covers the necessary procedures and tools to validate software assurance
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless

48. Benefits of coding 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
Support for accreditation and certification bodies that audit and certify ISMS
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

49. Management Controls
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

50. ISO /IEC 27000:2009
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Access request by a subject to an object is mediated each time and every time.
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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