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. Flaw Hypothesis Method (FHM)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

2. OWASP Top 10
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Periodic publication by OWASP for top 10 Web application security vulnerabilites

3. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Secure applicatios running on secure hosts (systems) in a secure network
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

4. Configurations Parameters Management
Protection against unauthorized information disclosure. It helps maintaining privacy
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

5. Least privilege
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
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

6. Phsychological acceptability
Covers the necessary procedures and tools to validate software assurance
Support for accreditation and certification bodies that audit and certify ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Security functionality is easy to use and transparent

7. Exposure factor (EF)
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
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

8. Confidentiality
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
Protection against unauthorized information disclosure. It helps maintaining privacy
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

9. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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.

10. OWASP testing guide
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Covers the necessary procedures and tools to validate software assurance
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.

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

12. DREAD
Security functionality is easy to use and transparent
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

13. EALs levels
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
Predetermined number of user error allowed before recording it as a security violation
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

14. Operation Controls
Authentication
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

15. ISO/IEC 27005:2008
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

16. After identification step is...
Risk remains after the implementation of mitigating security 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
Authentication

17. General security concept
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Covers the necessary procedures and tools to validate software assurance
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

18. Security profile of a software
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Security controls applied to mitigate a threat before it materializes

19. Error and exception management
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 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 functionality is easy to use and transparent
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. FIPS 197 (Advance Cryptographic standards - AES)
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
Confidentiality - Integrity - Availability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

21. Auditing
Number of incidents that can be expected in a year
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

22. Benefits of coding standards
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
Still under development - aimsto address ISMS implementation guidance
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

23. Threat
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
The likelihood that a threat can result into an incident. This is the overall risk of a system

24. OWASP development guide
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Indicator of magnitude risk in a year ALE = SLE * ARO
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

25. Open design
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Support for accreditation and certification bodies that audit and certify ISMS

26. STRIDE
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
OWASP - ITIL

27. 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
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

28. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Protection against unauthorized information disclosure. It helps maintaining privacy

29. ISO/IEC 15408
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

30. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Access request by a subject to an object is mediated each time and every time.

31. Accountability
Number of incidents that can be expected in a year
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
OWASP - ITIL

32. Compartmentalization
Authentication
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Still under development - aimsto address ISMS implementation guidance

33. Total Risk
Security controls applied to mitigate a threat before it materializes
The likelihood that a threat can result into an incident. This is the overall risk of a system
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Technical - Management - Operational

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

35. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

36. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Protection against unauthorized information disclosure. It helps maintaining privacy
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

37. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

38. Safeguards
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security controls applied to mitigate a threat before it materializes
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

39. Authorization
Still under development - aimsto address ISMS implementation guidance
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
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
Development guide - Code Review Guide - Testing Guide

40. Residual Risk
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
Technical - Management - Operational
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Risk remains after the implementation of mitigating security controls

41. Session Management
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Indicator of magnitude risk in a year ALE = SLE * ARO

42. NIST standards related to software security
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Secure applicatios running on secure hosts (systems) in a secure network
Number of incidents that can be expected in a year

43. Software security risk management methodologies
Protection against unauthorized information disclosure. It helps maintaining privacy
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Development guide - Code Review Guide - Testing Guide

44. Annual Rate of Occurence (ARO)
Technical - Management - Operational
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Number of incidents that can be expected in a year

45. OWASP Code Review Guide
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
Security controls applied to mitigate a threat before it materializes
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

46. Develop hack resilient software
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Development guide - Code Review Guide - Testing Guide

47. Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
OWASP - ITIL
Support policies at a granular and specific level - Can be characterized as internal and external
Support for accreditation and certification bodies that audit and certify ISMS

48. Core Security Concept
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Confidentiality - Integrity - Availability
Security controls applied after a threat has been materialized

49. Least common mechanism
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

50. Single point failure
Design to mitigate any single source of complete compromise
Security controls applied to mitigate a threat before it materializes
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls: