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. Take-Grant Model
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

2. 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
Covers the necessary procedures and tools to validate software assurance
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security functionality is easy to use and transparent

3. Economy of mechanism
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.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Indicator of magnitude risk in a year ALE = SLE * ARO
Support for accreditation and certification bodies that audit and certify ISMS

4. Complete mediation
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
Access request by a subject to an object is mediated each time and every time.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

5. Security Policies

6. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
OWASP - ITIL
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

7. Open design
The likelihood that a threat can result into an incident. This is the overall risk of a system
Authentication
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
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

8. Management Controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Development guide - Code Review Guide - Testing Guide
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

9. Implementation challenges
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system
Design to mitigate any single source of complete compromise
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

10. FIPS 201
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
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
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.

11. Least privilege
The likelihood that a threat can result into an incident. This is the overall risk of a system
Number of incidents that can be expected in a year
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

12. STRIDE
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
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
Confidentiality - Integrity - Availability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

13. Categories of 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
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
Technical - Management - Operational

14. Common best practices significant to Sofware Security
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
OWASP - ITIL
Technical - Management - Operational
Indicator of magnitude risk in a year ALE = SLE * ARO

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

16. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

17. FIPS 197 (Advance Cryptographic standards - AES)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Secure applicatios running on secure hosts (systems) in a secure network

18. Counter measures
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Predetermined number of user error allowed before recording it as a security violation
Security controls applied after a threat has been materialized

19. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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.

20. Configurations Parameters Management
Confidentiality - Integrity - Availability
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

21. Properties of secure software
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Secure applicatios running on secure hosts (systems) in a secure network

22. Holistic Security in software
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Secure applicatios running on secure hosts (systems) in a secure network
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security functionality is easy to use and transparent

23. ISO/IEC 27006:2007
Development guide - Code Review Guide - Testing Guide
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

24. PCI DSS
Predetermined number of user error allowed before recording it as a security violation
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Provides Common Criteria to evaluate IT security product
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

25. Access Matrix model

26. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

27. Safeguards
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Security controls applied to mitigate a threat before it materializes
Periodic publication by OWASP for top 10 Web application security vulnerabilites

28. Least common mechanism
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Security controls applied after a threat has been materialized
Support for accreditation and certification bodies that audit and certify ISMS

29. Session Management
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
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
Predetermined number of user error allowed before recording it as a security violation

30. Non Repudiation
Security functionality is easy to use and transparent
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
The likelihood that a threat can result into an incident. This is the overall risk of a 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

31. 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.
Confidentiality - Integrity - Availability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Secure applicatios running on secure hosts (systems) in a secure network

32. 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
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

33. ISO/IEC 27001:2005
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

34. OWASP Top 10
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 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

35. Phsychological acceptability
Security functionality is easy to use and transparent
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

36. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Security controls applied to mitigate a threat before it materializes
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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 27000:2009
Provides Common Criteria to evaluate IT security product
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

38. Auditing
Predetermined number of user error allowed before recording it as a security violation
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 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

39. Security profile of a software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

40. ISO/IEC 15408
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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 Common Criteria to evaluate IT security product
estimate potential loss of a single incident: SLE = Asset value * EF(%)

41. Annual Loss Expectancy (ALE)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk remains after the implementation of mitigating security controls

42. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
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
Support for accreditation and certification bodies that audit and certify ISMS

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

44. Exposure factor (EF)
Security controls applied to mitigate a threat before it materializes
Number of incidents that can be expected in a year
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Authentication

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

46. Security Controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

47. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk 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
Security functionality is easy to use and transparent
Indicator of magnitude risk in a year ALE = SLE * ARO

48. Error and exception management
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Authentication
Support for accreditation and certification bodies that audit and certify ISMS

49. After identification step is...
Authentication
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

50. 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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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