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. Compartmentalization
Technical - Management - Operational
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

2. Categories of controls
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
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
Technical - Management - Operational

3. Safeguards
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 controls applied to mitigate a threat before it materializes
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
estimate potential loss of a single incident: SLE = Asset value * EF(%)

4. Least common mechanism
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

5. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Covers the necessary procedures and tools to validate software assurance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

6. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Development guide - Code Review Guide - Testing Guide
Security controls applied to mitigate a threat before it materializes
OWASP - ITIL

7. Auditing
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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
Confidentiality - Integrity - Availability

8. OWASP Top 10
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

9. Core Security Concept
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Security controls applied after a threat has been materialized
Confidentiality - Integrity - Availability

10. Popular guides developed by OWASP
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Indicator of magnitude risk in a year ALE = SLE * ARO
Authentication
Development guide - Code Review Guide - Testing Guide

11. Security Standards
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Support policies at a granular and specific level - Can be characterized as internal and external

12. Authentication
Security functionality is easy to use and transparent
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

13. Properties of secure software
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

14. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Still under development - aimsto address ISMS implementation guidance
Covers the necessary procedures and tools to validate software assurance

15. Security profile of a software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

16. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Security functionality is easy to use and transparent

17. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security controls applied to mitigate a threat before it materializes
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

18. FIPS 197 (Advance Cryptographic standards - AES)
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

19. 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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

20. Common best practices significant to Sofware Security
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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.
OWASP - ITIL
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. Clipping level
Technical - Management - Operational
Security controls applied to mitigate a threat before it materializes
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
Predetermined number of user error allowed before recording it as a security violation

22. Risk management process
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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
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
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

23. Phsychological acceptability
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Security functionality is easy to use and transparent

24. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Covers the necessary procedures and tools to validate software assurance
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

25. Security Risk Management Discipline
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Indicator of magnitude risk in a year ALE = SLE * ARO

26. Management Controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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)

27. OWASP Code Review Guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Authentication
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

28. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
OWASP - ITIL
Support policies at a granular and specific level - Can be characterized as internal and external

29. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Still under development - aimsto address ISMS implementation guidance
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

30. Annual Rate of Occurence (ARO)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Number of incidents that can be expected in a year
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
Access request by a subject to an object is mediated each time and every time.

31. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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

32. Authorization
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

33. Configurations Parameters Management
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 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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

34. Open design
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Technical - Management - Operational
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

35. Error and exception management
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO

36. After identification step is...
Indicator of magnitude risk in a year ALE = SLE * ARO
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Authentication

37. 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 remains after the implementation of mitigating security controls
OWASP - ITIL
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

38. Least privilege
Still under development - aimsto address ISMS implementation guidance
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 controls applied after a threat has been materialized
Covers the necessary procedures and tools to validate software assurance

39. Take-Grant Model
Number of incidents that can be expected in a year
Authentication
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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. DREAD
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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

41. ISO/IEC 27003
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Still under development - aimsto address ISMS implementation guidance
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

42. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

43. Multifactor authentication
Security controls applied after a threat has been materialized
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
OWASP - ITIL

44. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Authentication

45. Threat
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

46. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Support for accreditation and certification bodies that audit and certify ISMS
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

47. Non Repudiation
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy

48. Challenges in implementing auditing/logging
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
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
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

49. Operation Controls
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

50. Availability
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.
Security controls applied to mitigate a threat before it materializes
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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