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. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

2. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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

3. ISO/IEC 27002:2005
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

4. Single point failure
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Authentication
Design to mitigate any single source of complete compromise

5. Clipping level
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
Predetermined number of user error allowed before recording it as a security violation
Covers the necessary procedures and tools to validate software assurance
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

6. Information Security Models
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

7. Residual Risk
Risk remains after the implementation of mitigating security controls
Covers the necessary procedures and tools to validate software assurance
Still under development - aimsto address ISMS implementation guidance
Security controls applied after a threat has been materialized

8. Least privilege
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Security controls applied to mitigate a threat before it materializes
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

9. ISO/IEC 27006:2007
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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

10. Security design principles
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
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 Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

11. Compartmentalization
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

12. Security profile of a software
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
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 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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

13. Software security risk management methodologies
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

14. Implementation challenges
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

15. FIPS140-2 (Security requirement for cryptographic modules)
Security functionality is easy to use and transparent
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Secure applicatios running on secure hosts (systems) in a secure network
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

16. ISO/IEC 27003
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Still under development - aimsto address ISMS implementation guidance

17. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Confidentiality - Integrity - Availability
Periodic publication by OWASP for top 10 Web application security vulnerabilites

18. Security Risk Management Discipline
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
Development guide - Code Review Guide - Testing Guide
Predetermined number of user error allowed before recording it as a security violation
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

19. Core Security Concept
Confidentiality - Integrity - Availability
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

20. FIPS 197 (Advance Cryptographic standards - AES)
Predetermined number of user error allowed before recording it as a security violation
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

21. 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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
OWASP - ITIL
Access request by a subject to an object is mediated each time and every time.

22. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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

23. OCTAVE
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
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
OWASP - ITIL

24. PCI DSS
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied to mitigate a threat before it materializes

25. After identification step is...
Authentication
OWASP - ITIL
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. Multifactor authentication
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Number of incidents that can be expected in a year
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

27. EALs levels
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Provides Common Criteria to evaluate IT security product
Support for accreditation and certification bodies that audit and certify ISMS

28. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Security controls applied to mitigate a threat before it materializes

29. Annual Rate of Occurence (ARO)
Development guide - Code Review Guide - Testing Guide
Number of incidents that can be expected in a year
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

30. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

31. Single Loss Expectancy (SLE)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

32. Safeguards
Security controls applied to mitigate a threat before it materializes
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Authentication

33. Availability
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
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.
Protection against unauthorized information disclosure. It helps maintaining privacy
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

34. ISO /IEC 27000:2009
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

35. Security Policies

36. 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Provides Common Criteria to evaluate IT security product
Design to mitigate any single source of complete compromise

37. Total Risk
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

38. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Number of incidents that can be expected in a year
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
Provides Common Criteria to evaluate IT security product

39. Common best practices significant to Sofware Security
OWASP - ITIL
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

40. Counter measures
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.
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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 controls applied after a threat has been materialized

41. 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
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
Support policies at a granular and specific level - Can be characterized as internal and external

42. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

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

44. Flaw Hypothesis Method (FHM)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

45. Open design
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Still under development - aimsto address ISMS implementation guidance
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. Categories of controls
Security functionality is easy to use and transparent
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Still under development - aimsto address ISMS implementation guidance
Technical - Management - Operational

47. Phsychological acceptability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security functionality is easy to use and transparent
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Access request by a subject to an object is mediated each time and every time.

48. Session Management
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
Number of incidents that can be expected in a year
Authentication
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

49. Develop hack resilient software
Design to mitigate any single source of complete compromise
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Risk remains after the implementation of mitigating security controls
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

50. Risk management process
Authentication
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
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 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