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. Phsychological acceptability
Security functionality is easy to use and transparent
Predetermined number of user error allowed before recording it as a security violation
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
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

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

3. Non Repudiation
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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
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. Examples of Security Standards
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Design to mitigate any single source of complete compromise
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

5. Clipping level
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
Risk remains after the implementation of mitigating security controls
Design to mitigate any single source of complete compromise
Predetermined number of user error allowed before recording it as a security violation

6. Open design
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 after a threat has been materialized
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
Confidentiality - Integrity - Availability

7. Information Security Models
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

8. Integrity
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

9. ISO/IEC 21827:2008
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Security functionality is easy to use and transparent
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

10. ISO/IEC 27001:2005
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.
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Protection against unauthorized information disclosure. It helps maintaining privacy

11. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
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
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

12. Accountability
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
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Provides Common Criteria to evaluate IT security product

13. EALs levels
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: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

14. Operation Controls
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Technical - Management - Operational
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

15. 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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

16. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Predetermined number of user error allowed before recording it as a security violation
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

17. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
OWASP - ITIL
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
Still under development - aimsto address ISMS implementation guidance

18. Authorization
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
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
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

19. Least common mechanism
Support for accreditation and certification bodies that audit and certify ISMS
Support policies at a granular and specific level - Can be characterized as internal and external
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

20. STRIDE
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

21. Authentication
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

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

23. Economy of mechanism
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
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

24. ISO/IEC 9216
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network

25. Single point failure
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
Design to mitigate any single source of complete compromise
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

26. Vulnerability
Confidentiality - Integrity - Availability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

27. Common best practices significant to Sofware Security
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Indicator of magnitude risk in a year ALE = SLE * ARO
Development guide - Code Review Guide - Testing Guide
OWASP - ITIL

28. Counter measures
Security controls applied after a threat has been materialized
Development guide - Code Review Guide - Testing Guide
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

29. Security Controls
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

30. OWASP Code Review Guide
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

31. Single Loss Expectancy (SLE)
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(%)
Development guide - Code Review Guide - Testing Guide
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

32. 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
Number of incidents that can be expected in a year
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Protection against unauthorized information disclosure. It helps maintaining privacy

33. OWASP Top 10
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Support policies at a granular and specific level - Can be characterized as internal and external
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

34. FIPS 201
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

35. OCTAVE
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
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
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
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information

36. 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Predetermined number of user error allowed before recording it as a security violation

37. ISO/IEC 15408
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Still under development - aimsto address ISMS implementation guidance
Provides Common Criteria to evaluate IT security product
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

38. Security profile of a software
Security controls applied to mitigate a threat before it materializes
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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

39. Exposure factor (EF)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

40. Popular guides developed by OWASP
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.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Development guide - Code Review Guide - Testing Guide
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

41. Management Controls
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

42. Confidentiality
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

43. FIPS140-2 (Security requirement for cryptographic modules)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

44. Availability
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
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.
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

45. ISO /IEC 27000:2009
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

46. OWASP development guide
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
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

47. Implementation challenges
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Authentication

48. Core Security Concept
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Protection against unauthorized information disclosure. It helps maintaining privacy
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Confidentiality - Integrity - Availability

49. FIPS 197 (Advance Cryptographic standards - AES)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Technical - Management - Operational

50. Risk management process
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
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
Security controls applied to mitigate a threat before it materializes
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