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

2. ISO /IEC 27000:2009
Protection against unauthorized information disclosure. It helps maintaining privacy
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

3. 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
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
Confidentiality - Integrity - Availability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

4. ISO/IEC 21827:2008
Still under development - aimsto address ISMS implementation guidance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

5. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

6. ISO/IEC 27005:2008
Predetermined number of user error allowed before recording it as a security violation
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

7. FIPS140-2 (Security requirement for cryptographic modules)
Development guide - Code Review Guide - Testing Guide
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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. Develop hack resilient software
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

9. Single point failure
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Design to mitigate any single source of complete compromise
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

10. Accountability
Provides Common Criteria to evaluate IT security product
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
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

11. Session Management
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

12. Counter measures
Support policies at a granular and specific level - Can be characterized as internal and external
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Security controls applied after a threat has been materialized
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

13. After identification step is...
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

14. Vulnerability
Security functionality is easy to use and transparent
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

15. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Support for accreditation and certification bodies that audit and certify ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Number of incidents that can be expected in a year

16. Management Controls
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

17. DREAD
Security controls applied after a threat has been materialized
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied to mitigate a threat before it materializes

18. Threat
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

19. Authentication
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
Support policies at a granular and specific level - Can be characterized as internal and external
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

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

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

22. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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.
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

23. Multifactor authentication
Security functionality is easy to use and transparent
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
The likelihood that a threat can result into an incident. This is the overall risk of a system
Development guide - Code Review Guide - Testing Guide

24. Security design principles
Confidentiality - Integrity - Availability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Support for accreditation and certification bodies that audit and certify ISMS

25. Exposure factor (EF)
Number of incidents that can be expected in a year
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

26. Properties of secure software
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

27. Residual Risk
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
Risk remains after the implementation of mitigating security 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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

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

29. Risk management process
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

30. Security Standards
Covers the necessary procedures and tools to validate software assurance
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
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
Support policies at a granular and specific level - Can be characterized as internal and external

31. Availability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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.
OWASP - ITIL

32. Take-Grant Model
Development guide - Code Review Guide - Testing Guide
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

33. Challenges in implementing auditing/logging
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Secure applicatios running on secure hosts (systems) in a secure network
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

34. Annual Rate of Occurence (ARO)
Security controls applied after a threat has been materialized
Number of incidents that can be expected in a year
Provides Common Criteria to evaluate IT security product
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

35. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

36. ISO/IEC 27001:2005
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

37. Access Matrix model

38. STRIDE
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Support policies at a granular and specific level - Can be characterized as internal and external

39. 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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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. EALs levels
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

41. Safeguards
Support for accreditation and certification bodies that audit and certify 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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security controls applied to mitigate a threat before it materializes

42. Phsychological acceptability
Security functionality is easy to use and transparent
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

43. Compartmentalization
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
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

44. Categories of controls
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Technical - Management - Operational
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

45. NIST standards related to software security
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
Design to mitigate any single source of complete compromise
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

46. Common best practices significant to Sofware Security
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
OWASP - ITIL
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
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

47. ISO/IEC 27003
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

48. FIPS 197 (Advance Cryptographic standards - AES)
Risk remains after the implementation of mitigating security controls
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
Access request by a subject to an object is mediated each time and every time.

49. Security Policies

50. Single Loss Expectancy (SLE)
Provides Common Criteria to evaluate IT security product
Confidentiality - Integrity - Availability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls: