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. ISO /IEC 27000:2009
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

2. Complete mediation
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Access request by a subject to an object is mediated each time and every time.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

3. Threat
Development guide - Code Review Guide - Testing Guide
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

4. Holistic Security in software
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Secure applicatios running on secure hosts (systems) in a secure network
Risk remains after the implementation of mitigating security controls
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

5. DREAD
Covers the necessary procedures and tools to validate software assurance
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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 calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

6. Total Risk
Protection against unauthorized information disclosure. It helps maintaining privacy
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

7. OWASP testing guide
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
Authentication
Confidentiality - Integrity - Availability

8. Popular guides developed by OWASP
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Development guide - Code Review Guide - Testing Guide
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

9. Common best practices significant to Sofware Security
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
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
OWASP - ITIL
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

10. Information Security Models
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Covers the necessary procedures and tools to validate software assurance
Predetermined number of user error allowed before recording it as a security violation
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

11. Develop hack resilient software
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
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.
The likelihood that a threat can result into an incident. This is the overall risk of a system
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

12. OWASP development guide
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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. FIPS 201
Still under development - aimsto address ISMS implementation guidance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

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

15. Auditing
Security functionality is easy to use and transparent
Access request by a subject to an object is mediated each time and every time.
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

16. 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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

17. Confidentiality
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Protection against unauthorized information disclosure. It helps maintaining privacy
Development guide - Code Review Guide - Testing Guide

18. 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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

19. 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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

20. Open design
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
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

21. Operation Controls
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Authentication
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

22. Non Repudiation
Indicator of magnitude risk in a year ALE = SLE * ARO
Secure applicatios running on secure hosts (systems) in a secure network
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

23. Phsychological acceptability
Security functionality is easy to use and transparent
Number of incidents that can be expected in a year
Risk remains after the implementation of mitigating security controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

24. ISO/IEC 27006:2007
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Support for accreditation and certification bodies that audit and certify 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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

25. Single point failure
Development guide - Code Review Guide - Testing Guide
Authentication
Design to mitigate any single source of complete compromise
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

26. Vulnerabilities repositories
Provides Common Criteria to evaluate IT security product
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

27. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
OWASP - ITIL
Indicator of magnitude risk in a year ALE = SLE * ARO
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

28. OWASP Top 10
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Periodic publication by OWASP for top 10 Web application security vulnerabilites

29. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Security controls applied after a threat has been materialized
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Access 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

30. Security Controls
Still under development - aimsto address ISMS implementation guidance
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Access request by a subject to an object is mediated each time and every time.

31. ISO/IEC 15408
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
OWASP - ITIL
Provides Common Criteria to evaluate IT security product
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

32. Core Security Concept
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Confidentiality - Integrity - Availability
Predetermined number of user error allowed before recording it as a security violation

33. Configurations Parameters 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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Support for accreditation and certification bodies that audit and certify ISMS
Support policies at a granular and specific level - Can be characterized as internal and external

34. ISO/IEC 21827:2008
Protection against unauthorized information disclosure. It helps maintaining privacy
Indicator of magnitude risk in a year ALE = SLE * 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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

35. Clipping level
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 Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Confidentiality - Integrity - Availability
Predetermined number of user error allowed before recording it as a security violation

36. STRIDE
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Security controls applied after a threat has been materialized

37. Vulnerability
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Support for accreditation and certification bodies that audit and certify 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

38. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Support for accreditation and certification bodies that audit and certify ISMS
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
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

39. FIPS 197 (Advance Cryptographic standards - AES)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Support for accreditation and certification bodies that audit and certify ISMS

40. Availability
Support policies at a granular and specific level - Can be characterized as internal and external
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
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
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.

41. Security Risk Management Discipline
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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.

42. PCI DSS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Design to mitigate any single source of complete compromise
Protection against unauthorized information disclosure. It helps maintaining privacy
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

43. Categories of controls
Security controls applied after a threat has been materialized
Technical - Management - Operational
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

44. Security Policies

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

45. Access Matrix model

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

46. Integrity
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

47. ISO/IEC 27003
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Still under development - aimsto address ISMS implementation guidance
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

48. Software security risk management methodologies
Secure applicatios running on secure hosts (systems) in a secure network
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

49. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk 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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Covers the necessary procedures and tools to validate software assurance

50. Multifactor authentication
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Protection against unauthorized information disclosure. It helps maintaining privacy
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