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. Availability
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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. Core Security Concept
Confidentiality - Integrity - Availability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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

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

4. 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

5. 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
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
Provides Common Criteria to evaluate IT security product
Covers the necessary procedures and tools to validate software assurance

6. Vulnerability
Indicator of magnitude risk in a year ALE = SLE * ARO
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Predetermined number of user error allowed before recording it as a security violation

7. FIPS 201
Risk remains after the implementation of mitigating security controls
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

8. Security Policies

9. Management 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:
OWASP - ITIL
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

10. 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
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.
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
estimate potential loss of a single incident: SLE = Asset value * EF(%)

11. OWASP development guide
Support for accreditation and certification bodies that audit and certify ISMS
Authentication
Support policies at a granular and specific level - Can be characterized as internal and external
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

12. Software security risk management methodologies
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

13. OWASP Top 10
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
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
Support for accreditation and certification bodies that audit and certify ISMS
Periodic publication by OWASP for top 10 Web application security vulnerabilites

14. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

15. Exposure factor (EF)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

16. After identification step is...
Access request by a subject to an object is mediated each time and every time.
Authentication
Covers the necessary procedures and tools to validate software assurance
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

17. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

18. Residual Risk
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
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

19. Security Controls
Indicator of magnitude risk in a year ALE = SLE * ARO
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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

20. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Covers the necessary procedures and tools to validate software assurance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

21. Security design principles
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

22. 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
Design to mitigate any single source of complete compromise
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

23. Auditing
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Still under development - aimsto address ISMS implementation guidance
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

24. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Confidentiality - Integrity - Availability

25. Total Risk
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
Confidentiality - Integrity - Availability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Indicator of magnitude risk in a year ALE = SLE * ARO

26. Security 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Support policies at a granular and specific level - Can be characterized as internal and external
Technical - Management - Operational

27. Vulnerabilities repositories
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
Technical - Management - Operational
Number of incidents that can be expected in a year
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

28. OWASP testing guide
Risk remains after the implementation of mitigating security controls
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Support policies at a granular and specific level - Can be characterized as internal and external
Covers the necessary procedures and tools to validate software assurance

29. Technical Controls
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Security functionality is easy to use and transparent

30. Authorization
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

31. 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
OWASP - ITIL
Development guide - Code Review Guide - Testing Guide
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

32. Non Repudiation
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

33. OWASP Code Review Guide
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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 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

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

35. 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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Access request by a subject to an object is mediated each time and every time.

36. Flaw Hypothesis Method (FHM)
Access request by a subject to an object is mediated each time and every time.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

37. Single point failure
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Protection against unauthorized information disclosure. It helps maintaining privacy
Design to mitigate any single source of complete compromise
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

38. Access Matrix model

39. STRIDE
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

40. Annual Loss Expectancy (ALE)
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Indicator of magnitude risk in a year ALE = SLE * ARO
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

41. Open design
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
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Security controls applied to mitigate a threat before it materializes
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

42. Confidentiality
Development guide - Code Review Guide - Testing Guide
Support for accreditation and certification bodies that audit and certify ISMS
Covers the necessary procedures and tools to validate software assurance
Protection against unauthorized information disclosure. It helps maintaining privacy

43. ISO/IEC 21827:2008
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

44. ISO/IEC 15408
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
Provides Common Criteria to evaluate IT security product
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

45. Least common mechanism
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Still under development - aimsto address ISMS implementation guidance
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

46. OCTAVE
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
The 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
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
Authentication

47. Security Risk Management Discipline
The likelihood that a threat can result into an incident. This is the overall risk of a system
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

48. Counter measures
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security controls applied after a threat has been materialized
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

49. Compartmentalization
Provides Common Criteria to evaluate IT security product
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Still under development - aimsto address ISMS implementation guidance
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. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Security controls applied to mitigate a threat before it materializes