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. Security profile of a software
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
Risk remains after the implementation of mitigating security controls
Support for accreditation and certification bodies that audit and certify ISMS

2. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
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 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

3. Session Management
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Development guide - Code Review Guide - Testing Guide
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
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

4. 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
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
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

5. ISO/IEC 27001:2005
Security controls applied after a threat has been materialized
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

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

7. Management Controls
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
OWASP - ITIL
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Authentication

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

9. Open design
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

10. 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied to mitigate a threat before it materializes

11. Flaw Hypothesis Method (FHM)
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Risk remains after the implementation of mitigating security controls

12. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
The likelihood that a threat can result into an incident. This is the overall risk of a system
Risk remains after the implementation of mitigating security controls
Support policies at a granular and specific level - Can be characterized as internal and external

13. Residual Risk
Risk remains after the implementation of mitigating security controls
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Protection against unauthorized information disclosure. It helps maintaining privacy

14. OWASP testing guide
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Authentication
Covers the necessary procedures and tools to validate software assurance

15. NIST standards related to software security
Security controls applied after a threat has been materialized
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
Security controls applied to mitigate a threat before it materializes
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

16. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

17. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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
Covers the necessary procedures and tools to validate software assurance

18. ISO/IEC 15408
Security controls applied to mitigate a threat before it materializes
Provides Common Criteria to evaluate IT security product
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

19. 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
The likelihood that a threat can result into an incident. This is the overall risk of a system
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

20. ISO/IEC 27005:2008
Still under development - aimsto address ISMS implementation guidance
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Support for accreditation and certification bodies that audit and certify ISMS

21. Phsychological acceptability
Security functionality is easy to use and transparent
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

22. Least common mechanism
Design to mitigate any single source of complete compromise
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.
OWASP - ITIL

23. 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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

24. Authorization
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

25. Clipping level
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

26. 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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

27. After identification step is...
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
Authentication
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

28. Complete mediation
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Support policies at a granular and specific level - Can be characterized as internal and external
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Access request by a subject to an object is mediated each time and every time.

29. Compartmentalization
Predetermined number of user error allowed before recording it as a security violation
Security controls applied after a threat has been materialized
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

30. Categories of controls
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
Technical - Management - Operational
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

31. Take-Grant 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.
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

32. Implementation challenges
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

33. Total Risk
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
The likelihood that a threat can result into an incident. This is the overall risk of a system

34. Single point failure
Support for accreditation and certification bodies that audit and certify ISMS
OWASP - ITIL
Design to mitigate any single source of complete compromise
Provides Common Criteria to evaluate IT security product

35. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Security controls applied after a threat has been materialized
Design to mitigate any single source of complete compromise
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

36. OWASP development guide
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

37. 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
OWASP - ITIL
Provides Common Criteria to evaluate IT security product
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.

38. Single Loss Expectancy (SLE)
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

39. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

40. Common best practices significant to Sofware Security
OWASP - ITIL
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
Development guide - Code Review Guide - Testing Guide
Support for accreditation and certification bodies that audit and certify ISMS

41. Confidentiality
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:
Protection against unauthorized information disclosure. It helps maintaining privacy
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

42. ISO/IEC 27003
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Security controls applied to mitigate a threat before it materializes
Still under development - aimsto address ISMS implementation guidance
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development

43. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

44. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Predetermined number of user error allowed before recording it as a security violation
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

45. Access Matrix model

46. Vulnerabilities repositories
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

47. Security Policies

48. Risk management process
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
Confidentiality - Integrity - Availability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

49. EALs levels
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
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

50. Develop hack resilient software
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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