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. Least privilege
Access request by a subject to an object is mediated each time and every time.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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

2. Software security risk management methodologies
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

3. Risk management process
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Number of incidents that can be expected in a year
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

4. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

5. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
The likelihood that a threat can result into an incident. This is the overall risk of a system
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

6. Take-Grant Model
Protection against unauthorized information disclosure. It helps maintaining privacy
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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 the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

7. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

8. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Predetermined number of user error allowed before recording it as a security violation

9. Authentication
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

10. ISO /IEC 27000:2009
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

11. Operation Controls
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security functionality is easy to use and transparent
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

12. Counter measures
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Predetermined number of user error allowed before recording it as a security violation
Security controls applied after a threat has been materialized

13. Non Repudiation
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
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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

14. Threat
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

15. Benefits of coding standards
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
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 likelihood that a threat can result into an incident. This is the overall risk of a system

16. General security concept
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Provides Common Criteria to evaluate IT security product
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

17. ISO/IEC 9216
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.
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

18. Access Matrix model

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

19. 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
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 for accreditation and certification bodies that audit and certify ISMS
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

20. Residual Risk
Security controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

21. ISO/IEC 27006:2007
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Security functionality is easy to use and transparent
Support for accreditation and certification bodies that audit and certify ISMS
Predetermined number of user error allowed before recording it as a security violation

22. Open design
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
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

23. OWASP development guide
Design to mitigate any single source of complete compromise
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Support for accreditation and certification bodies that audit and certify ISMS

24. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

25. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

26. Develop hack resilient software
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
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)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

27. Challenges in implementing auditing/logging
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
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
Support for accreditation and certification bodies that audit and certify ISMS

28. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Support for accreditation and certification bodies that audit and certify ISMS
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data

29. OWASP Code Review Guide
Technical - Management - Operational
Access request by a subject to an object is mediated each time and every time.
Development guide - Code Review Guide - Testing Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

30. Single Loss Expectancy (SLE)
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

31. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

32. ISO/IEC 27003
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Still under development - aimsto address ISMS implementation guidance
Indicator of magnitude risk in a year ALE = SLE * ARO
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

33. Exposure factor (EF)
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
Covers the necessary procedures and tools to validate software assurance
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.

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

35. OWASP Top 10
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
Security controls applied to mitigate a threat before it materializes
Provides Common Criteria to evaluate IT security product
Periodic publication by OWASP for top 10 Web application security vulnerabilites

36. Configurations Parameters Management
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
OWASP - ITIL

37. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Support for accreditation and certification bodies that audit and certify 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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

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

39. 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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

40. Properties of secure software
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

41. Security profile of a software
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Predetermined number of user error allowed before recording it as a security violation
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

42. Confidentiality
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Protection against unauthorized information disclosure. It helps maintaining privacy

43. Vulnerability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Development guide - Code Review Guide - Testing Guide
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

44. Security Policies

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

45. Vulnerabilities repositories
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Development guide - Code Review Guide - Testing Guide

46. Categories of controls
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Technical - Management - Operational

47. FIPS140-2 (Security requirement for cryptographic modules)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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 functionality is easy to use and transparent

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

49. Common best practices significant to Sofware Security
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
OWASP - ITIL

50. EALs levels
Technical - Management - Operational
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
Support for accreditation and certification bodies that audit and certify ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data