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

2. ISO /IEC 27000:2009
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Development guide - Code Review Guide - Testing Guide
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 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

3. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Predetermined number of user error allowed before recording it as a security violation
Support for accreditation and certification bodies that audit and certify ISMS
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

4. Single point failure
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
Access request by a subject to an object is mediated each time and every time.
Design to mitigate any single source of complete compromise

5. OWASP testing guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Confidentiality - Integrity - Availability
Covers the necessary procedures and tools to validate software assurance
Secure applicatios running on secure hosts (systems) in a secure network

6. Exposure factor (EF)
Still under development - aimsto address ISMS implementation guidance
Predetermined number of user error allowed before recording it as a security violation
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

7. Accountability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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 functionality is easy to use and transparent
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

8. Integrity
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
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
Number of incidents that can be expected in a year

9. 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Security controls applied to mitigate a threat before it materializes
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

10. Risk management process
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Access request by a subject to an object is mediated each time and every time.

11. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Still under development - aimsto address ISMS implementation guidance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

12. NIST standards related to software security
Protection against unauthorized information disclosure. It helps maintaining privacy
Secure applicatios running on secure hosts (systems) in a secure network
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 controls applied after a threat has been materialized

13. ISO/IEC 27005:2008
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security controls applied to mitigate a threat before it materializes
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

14. 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
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
Authentication
Number of incidents that can be expected in a year

15. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
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

16. Examples of Security Standards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Security controls applied after a threat has been materialized
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

17. Least privilege
Technical - Management - Operational
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Indicator of magnitude risk in a year ALE = SLE * ARO
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

18. ISO/IEC 15408
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
OWASP - ITIL
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
Provides Common Criteria to evaluate IT security product

19. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
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

20. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
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.
Development guide - Code Review Guide - Testing Guide
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

21. Vulnerabilities repositories
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

22. Access Matrix model

23. Categories of controls
Technical - Management - Operational
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

24. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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.
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

25. Economy of mechanism
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Technical - Management - Operational

26. OWASP Top 10
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Covers the necessary procedures and tools to validate software assurance
Periodic publication by OWASP for top 10 Web application security vulnerabilites

27. Security Policies

28. ISO/IEC 21827:2008
Protection against unauthorized information disclosure. It helps maintaining privacy
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Indicator of magnitude risk in a year ALE = SLE * ARO
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

29. Properties of secure software
Confidentiality - Integrity - Availability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

30. Confidentiality
Confidentiality - Integrity - Availability
Access request by a subject to an object is mediated each time and every time.
Protection against unauthorized information disclosure. It helps maintaining privacy
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

31. Complete mediation
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied after a threat has been materialized
Access request by a subject to an object is mediated each time and every time.

32. Compartmentalization
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Support policies at a granular and specific level - Can be characterized as internal and external

33. Popular guides developed by OWASP
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Development guide - Code Review Guide - Testing Guide

34. Phsychological acceptability
Design to mitigate any single source of complete compromise
Secure applicatios running on secure hosts (systems) in a secure network
Security functionality is easy to use and transparent
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

35. FIPS 201
Development guide - Code Review Guide - Testing Guide
Provides Common Criteria to evaluate IT security product
Number of incidents that can be expected in a year
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

36. Residual Risk
Risk remains after the implementation of mitigating security controls
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Covers the necessary procedures and tools to validate software assurance

37. Annual Loss Expectancy (ALE)
Confidentiality - Integrity - Availability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Indicator of magnitude risk in a year ALE = SLE * ARO

38. Safeguards
Security controls applied to mitigate a threat before it materializes
Technical - Management - Operational
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Still under development - aimsto address ISMS implementation guidance

39. Single Loss Expectancy (SLE)
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security functionality is easy to use and transparent

40. Non Repudiation
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

41. Software security risk management methodologies
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Still under development - aimsto address ISMS implementation guidance
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

42. Multifactor authentication
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

43. Session Management
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

44. Operation Controls
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
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
Secure applicatios running on secure hosts (systems) in a secure network
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

45. Common best practices significant to Sofware Security
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Covers the necessary procedures and tools to validate software assurance
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
OWASP - ITIL

46. 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
Authentication
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Technical - Management - Operational

47. Counter measures
Security controls applied after a threat has been materialized
Covers the necessary procedures and tools to validate software assurance
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

48. Total Risk
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
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
OWASP - ITIL

49. Threat
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Access request by a subject to an object is mediated each time and every time.
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

50. PCI DSS
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
Security controls applied to mitigate a threat before it materializes
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
Still under development - aimsto address ISMS implementation guidance