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. ISO/IEC 27006:2007
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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 policies at a granular and specific level - Can be characterized as internal and external
Support for accreditation and certification bodies that audit and certify ISMS

2. Software security risk management methodologies
Provides Common Criteria to evaluate IT security product
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

3. Popular guides developed by OWASP
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Development guide - Code Review Guide - Testing Guide
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

4. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Design to mitigate any single source of complete compromise
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

5. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Indicator of magnitude risk in a year ALE = SLE * ARO
Provides Common Criteria to evaluate IT security product
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

6. ISO /IEC 27000:2009
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
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
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

7. ISO/IEC 9216
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

8. STRIDE
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
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
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Security functionality is easy to use and transparent

9. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Risk remains after the implementation of mitigating security controls
Security controls applied after a threat has been materialized

10. Benefits of coding standards
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

11. Total Risk
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
The likelihood that a threat can result into an incident. This is the overall risk of a system
Secure applicatios running on secure hosts (systems) in a secure network

12. Properties of secure software
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

13. Challenges in implementing auditing/logging
Support policies at a granular and specific level - Can be characterized as internal and external
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Number of incidents that can be expected in a year

14. OWASP Top 10
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
Risk remains after the implementation of mitigating security controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

15. Information Security Models
Still under development - aimsto address ISMS implementation guidance
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Indicator of magnitude risk in a year ALE = SLE * ARO

16. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

17. FIPS140-2 (Security requirement for cryptographic modules)
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
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

18. ISO/IEC 27005:2008
Protection against unauthorized information disclosure. It helps maintaining privacy
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

19. Develop hack resilient software
Technical - Management - Operational
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

20. NIST standards related to software security
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
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
Development guide - Code Review Guide - Testing Guide
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

21. Session Management
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Authentication
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
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

22. OCTAVE
Security controls applied to mitigate a threat before it materializes
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
OWASP - ITIL
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

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

25. ISO/IEC 21827:2008
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Support for accreditation and certification bodies that audit and certify ISMS

26. 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Secure applicatios running on secure hosts (systems) in a secure network

27. Economy of mechanism
The likelihood that a threat can result into an incident. This is the overall risk of a system
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Predetermined number of user error allowed before recording it as a security violation

28. Examples of Security Standards
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
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

29. Safeguards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
Security controls applied to mitigate a threat before it materializes

30. Error and exception management
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

31. ISO/IEC 27003
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
The likelihood that a threat can result into an incident. This is the overall risk of a system
Still under development - aimsto address ISMS implementation guidance
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

32. Annual Rate of Occurence (ARO)
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
Covers the necessary procedures and tools to validate software assurance
Number of incidents that can be expected in a year
Support policies at a granular and specific level - Can be characterized as internal and external

33. Take-Grant Model
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

34. Threat
Security functionality is easy to use and transparent
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Risk remains after the implementation of mitigating security controls
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

35. Auditing
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Development guide - Code Review Guide - Testing Guide
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

36. Multifactor authentication
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

37. Technical Controls
Support policies at a granular and specific level - Can be characterized as internal and external
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

38. After identification step is...
Security controls applied after a threat has been materialized
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Authentication

39. Phsychological acceptability
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
Security functionality is easy to use and transparent
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

40. 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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Covers the necessary procedures and tools to validate software assurance

41. Implementation challenges
Development guide - Code Review Guide - Testing Guide
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Secure applicatios running on secure hosts (systems) in a secure network
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

42. Categories of controls
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Technical - Management - Operational
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
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

43. Security design principles
Number of incidents that can be expected in a year
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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

44. ISO/IEC 27002:2005
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Provides Common Criteria to evaluate IT security product
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

45. Counter measures
Security controls applied after a threat has been materialized
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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. Single Loss Expectancy (SLE)
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
Support for accreditation and certification bodies that audit and certify 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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

47. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

48. Open design
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

49. Authentication
Provides Common Criteria to evaluate IT security product
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Security 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

50. Core Security Concept
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Confidentiality - Integrity - Availability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject