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. Clipping level
Predetermined number of user error allowed before recording it as a security violation
OWASP - ITIL
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
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

2. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Security functionality is easy to use and transparent
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

3. Authorization
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Still under development - aimsto address ISMS implementation guidance
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

4. Residual Risk
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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 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
Risk remains after the implementation of mitigating security controls

5. NIST standards related to software security
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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

6. Least common mechanism
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

7. Counter measures
Security controls applied after a threat has been materialized
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
OWASP - ITIL
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

8. OWASP Code Review Guide
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security controls applied to mitigate a threat before it materializes
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.

9. DREAD
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Confidentiality - Integrity - Availability
Security functionality is easy to use and transparent

10. Vulnerability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Confidentiality - Integrity - Availability
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

11. ISO/IEC 27006:2007
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
Support for accreditation and certification bodies that audit and certify ISMS
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

12. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Support for accreditation and certification bodies that audit and certify ISMS
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy

13. Single point failure
Authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Design to mitigate any single source of complete compromise

14. Accountability
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

15. Vulnerabilities repositories
Authentication
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Number of incidents that can be expected in a year

16. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

17. Authentication
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

18. Challenges in implementing auditing/logging
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Development guide - Code Review Guide - Testing Guide

19. Single Loss Expectancy (SLE)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Authentication
Security functionality is easy to use and transparent
estimate potential loss of a single incident: SLE = Asset value * EF(%)

20. OCTAVE
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

21. Information Security Models
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Support policies at a granular and specific level - Can be characterized as internal and external

22. Annual Rate of Occurence (ARO)
OWASP - ITIL
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
Number of incidents that can be expected in a year

23. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Covers the necessary procedures and tools to validate software assurance
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

24. Economy of mechanism
Predetermined number of user error allowed before recording it as a security violation
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

25. Integrity
Provides Common Criteria to evaluate IT security product
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Confidentiality - Integrity - Availability

26. Error and exception management
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
Secure applicatios running on secure hosts (systems) in a secure network
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

27. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
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

28. OWASP Top 10
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 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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

29. Benefits of coding standards
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Number of incidents that can be expected in a year
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

30. Flaw Hypothesis Method (FHM)
Technical - Management - Operational
Support for accreditation and certification bodies that audit and certify ISMS
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

31. Security Standards
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
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
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

32. Phsychological acceptability
Technical - Management - Operational
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security functionality is easy to use and transparent

33. Security Policies

34. Access Matrix model

35. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

36. Safeguards
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.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security controls applied to mitigate a threat before it materializes
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

37. OWASP testing guide
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
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
Covers the necessary procedures and tools to validate software assurance
Number of incidents that can be expected in a year

38. Risk management process
Provides Common Criteria to evaluate IT security product
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Security controls applied after a threat has been materialized

39. ISO/IEC 9216
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

40. Session Management
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 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

41. Security profile of a software
Authentication
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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. Confidentiality
Security controls applied after a threat has been materialized
Protection against unauthorized information disclosure. It helps maintaining privacy
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

43. Complete mediation
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

44. Security design principles
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Access request by a subject to an object is mediated each time and every time.

45. Technical Controls
Design to mitigate any single source of complete compromise
Covers the necessary procedures and tools to validate software assurance
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

46. Popular guides developed by OWASP
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Development guide - Code Review Guide - Testing Guide

47. Non Repudiation
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

48. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Confidentiality - Integrity - Availability

49. ISO/IEC 15408
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:
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

50. OWASP development guide
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS