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. Single Loss Expectancy (SLE)
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
Risk remains after the implementation of mitigating security controls
estimate potential loss of a single incident: SLE = Asset value * EF(%)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

2. Holistic Security in software
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
Authentication
Access request by a subject to an object is mediated each time and every time.

3. Security Policies

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

4. Security profile of a software
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

5. Security Risk Management Discipline
Secure applicatios running on secure hosts (systems) in a secure network
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

6. After identification step is...
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Authentication
Development guide - Code Review Guide - Testing Guide

7. Common best practices significant to Sofware Security
OWASP - ITIL
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Number of incidents that can be expected in a year
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

8. Annual Loss Expectancy (ALE)
Predetermined number of user error allowed before recording it as a security violation
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

9. Develop hack resilient software
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Security controls applied to mitigate a threat before it materializes
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

10. Authorization
Predetermined number of user error allowed before recording it as a security violation
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

11. Risk management process
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
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
Security controls applied to mitigate a threat before it materializes
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

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

13. Economy of mechanism
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Technical - Management - Operational
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

14. Information Security Models
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Technical - Management - Operational
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

15. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Design to mitigate any single source of complete compromise
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

16. 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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

17. General security concept
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
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

18. Least common mechanism
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Number of incidents that can be expected in a year
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

19. FIPS 197 (Advance Cryptographic standards - AES)
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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Protection against unauthorized information disclosure. It helps maintaining privacy

20. OWASP development guide
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
Provides Common Criteria to evaluate IT security product
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

21. Least privilege
Provides Common Criteria to evaluate IT security product
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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

22. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Authentication

23. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
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
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

24. 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
Risk remains after the implementation of mitigating security controls
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Provides Common Criteria to evaluate IT security product

25. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied to mitigate a threat before it materializes
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

26. ISO/IEC 27002:2005
Indicator of magnitude risk in a year ALE = SLE * ARO
Development guide - Code Review Guide - Testing Guide
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

27. OWASP Code Review Guide
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)
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
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

28. Counter measures
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 possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security controls applied after a threat has been materialized
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

29. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

30. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

31. ISO /IEC 27000:2009
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
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
Still under development - aimsto address ISMS implementation guidance

32. ISO/IEC 27005:2008
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

33. Open design
Security controls applied to mitigate a threat before it materializes
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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

34. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

35. Vulnerability
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Security functionality is easy to use and transparent
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.
Access request by a subject to an object is mediated each time and every time.

36. OWASP Top 10
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
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

37. ISO/IEC 9216
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Periodic publication by OWASP for top 10 Web application security vulnerabilites

38. ISO/IEC 21827:2008
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
Access request by a subject to an object is mediated each time and every time.
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

39. Properties of secure software
Still under development - aimsto address ISMS implementation guidance
Indicator of magnitude risk in a year ALE = SLE * ARO
Security functionality is easy to use and transparent
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

40. OCTAVE
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Support for accreditation and certification bodies that audit and certify ISMS
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

41. Authentication
The likelihood that a threat can result into an incident. This is the overall risk of a system
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

42. 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

43. Complete mediation
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Access request by a subject to an object is mediated each time and every time.
Authentication

44. Safeguards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied to mitigate a threat before it materializes

45. Flaw Hypothesis Method (FHM)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

46. Auditing
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

47. 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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

48. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Design to mitigate any single source of complete compromise
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

49. Operation Controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

50. NIST standards related to software security
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)