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. Open design
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
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 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

2. ISO/IEC 27002:2005
Security controls applied to mitigate a threat before it materializes
Secure applicatios running on secure hosts (systems) in a secure network
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

3. Common best practices significant to Sofware Security
OWASP - ITIL
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

4. Compartmentalization
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Design to mitigate any single source of complete compromise

5. 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
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
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 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

6. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Number of incidents that can be expected in a year
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

7. ISO/IEC 21827:2008
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
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

8. Security Standards
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
Development guide - Code Review Guide - Testing Guide
Support policies at a granular and specific level - Can be characterized as internal and external
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

9. 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
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

10. ISO/IEC 27001:2005
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

11. Multifactor authentication
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Authentication

12. Session Management
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
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

13. Holistic Security in software
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
The likelihood that a threat can result into an incident. This is the overall risk of a system
Secure applicatios running on secure hosts (systems) in a secure network
Access request by a subject to an object is mediated each time and every time.

14. After identification step is...
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Protection against unauthorized information disclosure. It helps maintaining privacy
Authentication
Development guide - Code Review Guide - Testing Guide

15. Accountability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

16. OWASP testing guide
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Covers the necessary procedures and tools to validate software assurance
Security functionality is easy to use and transparent
Risk remains after the implementation of mitigating security controls

17. 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
Still under development - aimsto address ISMS implementation guidance
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

18. Access Matrix model

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

19. Exposure factor (EF)
Predetermined number of user error allowed before recording it as a security violation
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Secure applicatios running on secure hosts (systems) in a secure network

20. General security concept
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
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

21. Phsychological acceptability
Security functionality is easy to use and transparent
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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.
Provides Common Criteria to evaluate IT security product

22. Security Policies

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

23. Residual Risk
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Risk remains after the implementation of mitigating security controls
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

24. Challenges in implementing auditing/logging
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Predetermined number of user error allowed before recording it as a security violation
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

25. Benefits of coding standards
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Security controls applied after a threat has been materialized
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

26. PCI DSS
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Predetermined number of user error allowed before recording it as a security violation
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

27. Authorization
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

28. 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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Authentication
Secure applicatios running on secure hosts (systems) in a secure network

29. Implementation challenges
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Access request by a subject to an object is mediated each time and every time.
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

30. Risk management process
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
Confidentiality - Integrity - Availability
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
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

31. Properties of secure 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
Secure applicatios running on secure hosts (systems) in a secure network
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

32. Vulnerabilities repositories
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

33. Security Risk Management Discipline
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Risk remains after the implementation of mitigating security controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

34. ISO/IEC 27006:2007
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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.
Covers the necessary procedures and tools to validate software assurance
Support for accreditation and certification bodies that audit and certify ISMS

35. 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

36. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Predetermined number of user error allowed before recording it as a security violation
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

37. Annual Rate of Occurence (ARO)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Number of incidents that can be expected in a year
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

38. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Support policies at a granular and specific level - Can be characterized as internal and external

39. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security controls applied after a threat has been materialized
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

40. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

41. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

42. Vulnerability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
The likelihood that a threat can result into an incident. This is the overall risk of a system

43. OWASP Code Review Guide
Technical - Management - Operational
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

44. Core Security Concept
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
Technical - Management - Operational
Confidentiality - Integrity - Availability

45. Authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

46. Management Controls
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Support for accreditation and certification bodies that audit and certify ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

47. Safeguards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security controls applied to mitigate a threat before it materializes
OWASP - ITIL
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

48. 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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Confidentiality - Integrity - Availability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

49. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Risk remains after the implementation of mitigating security controls

50. Flaw Hypothesis Method (FHM)
Secure applicatios running on secure hosts (systems) in a secure network
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Authentication