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. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Security controls applied after a threat has been materialized
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

2. Availability
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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.

3. Compartmentalization
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Secure applicatios running on secure hosts (systems) in a secure network
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

4. NIST standards related to software security
Predetermined number of user error allowed before recording it as a security violation
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Still under development - aimsto address ISMS implementation guidance
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

5. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Design to mitigate any single source of complete compromise
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

6. Open design
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Predetermined number of user error allowed before recording it as a security violation
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

7. 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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

8. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

9. Develop hack resilient software
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

10. Implementation challenges
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

11. Configurations Parameters Management
Risk remains after the implementation of mitigating security controls
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

12. Security profile of a software
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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 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
Technical - Management - Operational

13. Least privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
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

14. FIPS 197 (Advance Cryptographic standards - AES)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

15. After identification step is...
Authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied to mitigate a threat before it materializes
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

16. ISO/IEC 27005:2008
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

17. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
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
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

18. FIPS 201
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
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

19. 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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

20. DREAD
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

21. Vulnerabilities repositories
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

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

23. Multifactor authentication
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
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)
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

24. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

25. Risk management process
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
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
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

26. ISO/IEC 21827:2008
Security controls applied after a threat has been materialized
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

27. Session Management
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
Support for accreditation and certification bodies that audit and certify ISMS
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

28. Least common mechanism
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

29. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Confidentiality - Integrity - Availability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

30. ISO/IEC 27006:2007
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Support for accreditation and certification bodies that audit and certify ISMS
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

31. Core Security Concept
Confidentiality - Integrity - Availability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Secure applicatios running on secure hosts (systems) in a secure network
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

32. Total Risk
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
The likelihood that a threat can result into an incident. This is the overall risk of a system
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Support for accreditation and certification bodies that audit and certify ISMS

33. ISO/IEC 15408
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Provides Common Criteria to evaluate IT security product
OWASP - ITIL

34. Integrity
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
Technical - Management - Operational
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
OWASP - ITIL

35. OWASP Code Review Guide
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
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

36. Holistic Security in software
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Secure applicatios running on secure hosts (systems) in a secure network

37. Flaw Hypothesis Method (FHM)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

38. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

39. Single point failure
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Predetermined number of user error allowed before recording it as a security violation
Design to mitigate any single source of complete compromise
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

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

41. PCI DSS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Security controls applied to mitigate a threat before it materializes
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

42. Counter measures
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security controls applied after a threat has been materialized
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

43. 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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Number of incidents that can be expected in a year

44. Benefits of coding standards
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
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 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

45. STRIDE
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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.
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

46. Threat
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Protection against unauthorized information disclosure. It helps maintaining privacy

47. 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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

48. 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
Authentication
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

49. Residual Risk
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Development guide - Code Review Guide - Testing Guide
Risk remains after the implementation of mitigating security controls
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

50. OWASP development guide
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors