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. 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
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

2. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
Predetermined number of user error allowed before recording it as a security violation
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

3. Operation Controls
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: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

4. Compartmentalization
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
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
Security functionality is easy to use and transparent

5. After identification step is...
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Authentication
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

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

7. Security Standards
Still under development - aimsto address ISMS implementation guidance
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Support policies at a granular and specific level - Can be characterized as internal and external

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

9. Categories of controls
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
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
Technical - Management - Operational
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

10. DREAD
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
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Protection against unauthorized information disclosure. It helps maintaining privacy

11. Develop hack resilient software
Development guide - Code Review Guide - Testing Guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

12. FIPS 201
Confidentiality - Integrity - Availability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

13. Security Policies

14. Access Matrix model

15. ISO/IEC 27001:2005
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Technical - Management - Operational
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

16. Core Security Concept
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Access request by a subject to an object is mediated each time and every time.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Confidentiality - Integrity - Availability

17. Total Risk
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Secure applicatios running on secure hosts (systems) in a secure network
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

18. OWASP testing guide
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Covers the necessary procedures and tools to validate software assurance
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

19. Safeguards
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security controls applied to mitigate a threat before it materializes

20. Clipping level
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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

21. Availability
Still under development - aimsto address ISMS implementation guidance
Security functionality is easy to use and transparent
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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.

22. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Indicator of magnitude risk in a year ALE = SLE * ARO
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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. Residual Risk
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Risk remains after the implementation of mitigating security controls
Covers the necessary procedures and tools to validate software assurance

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

25. Security profile of a software
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
Risk remains after the implementation of mitigating security controls
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

26. Error and exception management
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

27. ISO/IEC 9216
Provides Common Criteria to evaluate IT security product
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

28. OWASP development 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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

29. ISO/IEC 21827:2008
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Authentication
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

30. Phsychological acceptability
Security functionality is easy to use and transparent
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Design to mitigate any single source of complete compromise
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Security functionality is easy to use and transparent

32. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Confidentiality - Integrity - Availability
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
Development guide - Code Review Guide - Testing Guide

33. Multifactor 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
Secure applicatios running on secure hosts (systems) in a secure network
Confidentiality - Integrity - Availability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

34. ISO/IEC 15408
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 Common Criteria to evaluate IT security product
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

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

36. OWASP Code Review Guide
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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

37. Security Risk Management Discipline
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

38. Complete mediation
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
The likelihood that a threat can result into an incident. This is the overall risk of a system
Access request by a subject to an object is mediated each time and every time.
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

39. Benefits of coding standards
Covers the necessary procedures and tools to validate software assurance
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

40. ISO/IEC 27005:2008
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Security controls applied to mitigate a threat before it materializes

41. 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
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

42. Non Repudiation
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.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
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

43. Counter measures
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Security controls applied after a threat has been materialized
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

44. ISO/IEC 27003
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Access request by a subject to an object is mediated each time and every time.
Still under development - aimsto address ISMS implementation guidance

45. PCI DSS
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
Provides Common Criteria to evaluate IT security product
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Still under development - aimsto address ISMS implementation guidance

46. Open design
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
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

47. Threat
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Confidentiality - Integrity - Availability
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.

48. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

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

50. OWASP Top 10
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Periodic publication by OWASP for top 10 Web application security vulnerabilites