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. Economy of mechanism
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Development guide - Code Review Guide - Testing Guide
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

2. Configurations Parameters Management
Risk remains after the implementation of mitigating security controls
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Authentication

3. Session Management
Secure applicatios running on secure hosts (systems) in a secure network
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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 functionality is easy to use and transparent

4. Operation Controls
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Support for accreditation and certification bodies that audit and certify 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

5. After identification step is...
Authentication
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Risk remains after the implementation of mitigating security controls
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

6. Properties of secure 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 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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

7. Benefits of coding 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

8. ISO/IEC 21827:2008
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Predetermined number of user error allowed before recording it as a security violation
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

9. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Still under development - aimsto address ISMS implementation guidance
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

10. Popular guides developed by OWASP
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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
Development guide - Code Review Guide - Testing Guide

11. Multifactor authentication
Protection against unauthorized information disclosure. It helps maintaining privacy
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

12. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Still under development - aimsto address ISMS implementation guidance
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 after a threat has been materialized

13. Core Security Concept
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
Confidentiality - Integrity - Availability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

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

15. Counter measures
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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

16. Categories of controls
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
Still under development - aimsto address ISMS implementation guidance
Technical - Management - Operational
Security controls applied to mitigate a threat before it materializes

17. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

18. Error and exception management
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

19. Security Risk Management Discipline
Covers the necessary procedures and tools to validate software assurance
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Development guide - Code Review Guide - Testing Guide
Authentication

20. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

21. Develop hack resilient 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

22. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Number of incidents that can be expected in a year
Design to mitigate any single source of complete compromise
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

23. Phsychological acceptability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security functionality is easy to use and transparent
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
Predetermined number of user error allowed before recording it as a security violation

24. Information Security Models
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

25. Availability
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.
Number of incidents that can be expected in a year
Support policies at a granular and specific level - Can be characterized as internal and external
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

26. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Development guide - Code Review Guide - Testing Guide

27. Least privilege
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Access request by a subject to an object is mediated each time and every time.
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

28. Access Matrix model

29. STRIDE
Provides Common Criteria to evaluate IT security product
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
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
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

30. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Indicator of magnitude risk in a year ALE = SLE * ARO
The likelihood that a threat can result into an incident. This is the overall risk of a system

31. Accountability
Technical - Management - Operational
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

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

33. Exposure factor (EF)
Support for accreditation and certification bodies that audit and certify ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

34. OCTAVE
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

35. Non Repudiation
Provides Common Criteria to evaluate IT security product
Authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

36. Authorization
Risk remains after the implementation of mitigating security controls
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

37. 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
Security controls applied after a threat has been materialized
Development guide - Code Review Guide - Testing Guide
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

38. Complete mediation
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Access request by a subject to an object is mediated each time and every time.
Technical - Management - Operational
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

39. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
OWASP - ITIL

40. Technical Controls
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

41. EALs levels
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Technical - Management - Operational
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m

42. Security design principles
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

43. Risk management process
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Secure applicatios running on secure hosts (systems) in a secure network
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

44. General security concept
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

45. OWASP Code Review Guide
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

46. Least common mechanism
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

47. 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
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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

48. FIPS 197 (Advance Cryptographic standards - AES)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Confidentiality - Integrity - Availability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.

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

50. Security Policies