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. OWASP Top 10
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Confidentiality - Integrity - Availability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

2. Annual Loss Expectancy (ALE)
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

3. FIPS140-2 (Security requirement for cryptographic modules)
Design to mitigate any single source of complete compromise
Protection against unauthorized information disclosure. It helps maintaining privacy
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

4. Benefits of coding 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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

5. NIST standards related to software security
Covers the necessary procedures and tools to validate software assurance
Authentication
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
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

6. Clipping level
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Predetermined number of user error allowed before recording it as a security violation
Access request by a subject to an object is mediated each time and every time.

7. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

8. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
The likelihood that a threat can result into an incident. This is the overall risk of a system
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

9. Vulnerabilities repositories
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

10. Authorization
Security functionality is easy to use and transparent
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
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

11. Access Matrix model

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

12. Auditing
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Security controls applied to mitigate a threat before it materializes

13. Examples of Security Standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

14. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

15. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Authentication
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

16. EALs levels
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
Covers the necessary procedures and tools to validate software assurance
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

17. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Risk remains after the implementation of mitigating security controls

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

19. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Confidentiality - Integrity - Availability

20. ISO/IEC 27006:2007
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
Support for accreditation and certification bodies that audit and certify 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

21. Categories of controls
Technical - Management - Operational
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Protection against unauthorized information disclosure. It helps maintaining privacy

22. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security functionality is easy to use and transparent

23. Authentication
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security controls applied after a threat has been materialized
Development guide - Code Review Guide - Testing Guide
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

24. Develop hack resilient software
Protection against unauthorized information disclosure. It helps maintaining privacy
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Security functionality is easy to use and transparent
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

25. Single point failure
Security controls applied after a threat has been materialized
Risk remains after the implementation of mitigating security controls
Design to mitigate any single source of complete compromise
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

26. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Development guide - Code Review Guide - Testing Guide
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
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

27. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Still under development - aimsto address ISMS implementation guidance
Technical - Management - Operational
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

28. Information Security Models
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Protection against unauthorized information disclosure. It helps maintaining privacy
Support policies at a granular and specific level - Can be characterized as internal and external

29. 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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Secure applicatios running on secure hosts (systems) in a secure network
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

30. Annual Rate of Occurence (ARO)
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
Authentication
Number of incidents that can be expected in a year
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

31. OWASP testing guide
Provides Common Criteria to evaluate IT security product
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Covers the necessary procedures and tools to validate software assurance

32. Security profile of a software
Secure applicatios running on secure hosts (systems) in a secure network
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

33. Counter measures
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security controls applied after a threat has been materialized
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

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

35. Core Security Concept
Confidentiality - Integrity - Availability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

36. Security design principles
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

37. Risk management process
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
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

38. Open design
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
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
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

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

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

41. Multifactor authentication
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
Security controls applied after a threat has been materialized
Development guide - Code Review Guide - Testing Guide

42. Integrity
Security functionality is easy to use and transparent
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

43. Flaw Hypothesis Method (FHM)
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

44. Security Standards
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
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

45. 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
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Authentication

46. Exposure factor (EF)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security functionality is easy to use and transparent
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

47. Residual Risk
Risk remains after the implementation of mitigating security controls
Support policies at a granular and specific level - Can be characterized as internal and external
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
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

48. Session Management
OWASP - ITIL
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
Development guide - Code Review Guide - Testing Guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

49. Error and exception management
Development guide - Code Review Guide - Testing Guide
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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

50. Single Loss Expectancy (SLE)
Support for accreditation and certification bodies that audit and certify ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege