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. Popular guides developed by OWASP
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Development guide - Code Review Guide - Testing Guide
Design to mitigate any single source of complete compromise
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

2. Flaw Hypothesis Method (FHM)
Indicator of magnitude risk in a year ALE = SLE * ARO
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

3. Annual Loss Expectancy (ALE)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

4. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Authentication
Security controls applied after a threat has been materialized

5. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Confidentiality - Integrity - Availability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

6. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Support for accreditation and certification bodies that audit and certify ISMS

7. 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
Technical - Management - Operational
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

8. OCTAVE
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

9. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

10. DREAD
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

11. Safeguards
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security controls applied to mitigate a threat before it materializes
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
Confidentiality - Integrity - Availability

12. Management Controls
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data

13. Security profile of a software
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
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 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
Provides Common Criteria to evaluate IT security product

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

15. Annual Rate of Occurence (ARO)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Number of incidents that can be expected in a year
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

16. Single point failure
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
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

17. Error and exception management
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
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
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
Design to mitigate any single source of complete compromise

18. FIPS 197 (Advance Cryptographic standards - AES)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

19. Security 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
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
Support for accreditation and certification bodies that audit and certify ISMS
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

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

21. ISO/IEC 27006:2007
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Technical - Management - Operational

22. Implementation challenges
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Access request by a subject to an object is mediated each time and every time.

23. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
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

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

25. Complete mediation
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Support for accreditation and certification bodies that audit and certify ISMS
Access request by a subject to an object is mediated each time and every time.

26. Economy of mechanism
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
Authentication
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

27. Availability
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
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
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
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.

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

29. ISO /IEC 27000:2009
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

30. Counter measures
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Security controls applied after a threat has been materialized

31. Least privilege
Confidentiality - Integrity - Availability
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

32. 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
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
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

33. PCI DSS
Support policies at a granular and specific level - Can be characterized as internal and external
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

34. Technical Controls
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

35. EALs levels
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Authentication
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
Protection against unauthorized information disclosure. It helps maintaining privacy

36. FIPS 201
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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

37. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

38. Benefits of coding standards
Security controls applied to mitigate a threat before it materializes
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

39. Common best practices significant to Sofware Security
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
OWASP - ITIL
Support for accreditation and certification bodies that audit and certify ISMS
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

40. Phsychological acceptability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security functionality is easy to use and transparent

41. Non Repudiation
Predetermined number of user error allowed before recording it as a security violation
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

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
Technical - Management - Operational
Confidentiality - Integrity - Availability
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

43. Authentication
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

44. Accountability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Risk remains after the implementation of mitigating security controls
OWASP - ITIL
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

45. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

46. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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

47. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

48. Residual Risk
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Risk remains after the implementation of mitigating security controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

49. FIPS140-2 (Security requirement for cryptographic modules)
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

50. Security Policies