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. Confidentiality
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)
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
Security controls applied after a threat has been materialized

2. Common best practices significant to Sofware Security
OWASP - ITIL
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
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
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. 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security controls applied after a threat has been materialized
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

4. ISO/IEC 27005:2008
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

5. Error and exception management
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
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

6. PCI DSS
The likelihood that a threat can result into an incident. This is the overall risk of a system
Technical - Management - Operational
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
Number of incidents that can be expected in a year

7. Phsychological acceptability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
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 functionality is easy to use and transparent

8. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

9. Security Risk Management Discipline
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Number of incidents that can be expected in a year
Development guide - Code Review Guide - Testing Guide

10. ISO/IEC 9216
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job

11. OWASP testing guide
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Covers the necessary procedures and tools to validate software assurance

12. Annual Loss Expectancy (ALE)
Predetermined number of user error allowed before recording it as a security violation
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Indicator of magnitude risk in a year ALE = SLE * ARO
estimate potential loss of a single incident: SLE = Asset value * EF(%)

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

14. Challenges in implementing auditing/logging
OWASP - ITIL
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Support policies at a granular and specific level - Can be characterized as internal and external

15. Session Management
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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

16. Security Policies

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

17. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

18. General security concept
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

19. Non Repudiation
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

20. OWASP Top 10
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Security controls applied after a threat has been materialized

21. Flaw Hypothesis Method (FHM)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

22. Take-Grant Model
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

23. FIPS 201
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Secure applicatios running on secure hosts (systems) in a secure network

24. 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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security functionality is easy to use and transparent
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

25. 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

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

27. Clipping level
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
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
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
Predetermined number of user error allowed before recording it as a security violation

28. Operation Controls
Support policies at a granular and specific level - Can be characterized as internal and external
Access request by a subject to an object is mediated each time and every time.
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

29. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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

30. Security design principles
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

31. Residual Risk
Risk remains after the implementation of mitigating security controls
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

32. Accountability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
OWASP - ITIL
Predetermined number of user error allowed before recording it as a security violation
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

33. Security profile of a software
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.
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
Still under development - aimsto address ISMS implementation guidance
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

34. ISO /IEC 27000:2009
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
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 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

35. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Secure applicatios running on secure hosts (systems) in a secure network
Design to mitigate any single source of complete compromise
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

36. Compartmentalization
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

37. 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)
Protection against unauthorized information disclosure. It helps maintaining privacy
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Still under development - aimsto address ISMS implementation guidance

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

39. Availability
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

40. Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Still under development - aimsto address ISMS implementation guidance
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 policies at a granular and specific level - Can be characterized as internal and external

41. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Still under development - aimsto address ISMS implementation guidance
Security controls applied after a threat has been materialized
Protection against unauthorized information disclosure. It helps maintaining privacy

42. Least common mechanism
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

43. 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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

44. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Technical - Management - Operational
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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

45. Vulnerability
Security functionality is easy to use and transparent
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Secure applicatios running on secure hosts (systems) in a secure network
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

46. Authorization
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

47. Complete mediation
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system
Access request by a subject to an object is mediated each time and every time.
Support policies at a granular and specific level - Can be characterized as internal and external

48. Security Controls
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
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
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. Software security risk management methodologies
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

50. After identification step is...
Authentication
Covers the necessary procedures and tools to validate software assurance
Design to mitigate any single source of complete compromise
Successful completion of a critical task is dependent on 2 or more conditions that need to be met