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. Threat
Authentication
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

2. Total Risk
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
The likelihood that a threat can result into an incident. This is the overall risk of a system
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Number of incidents that can be expected in a year

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

4. ISO/IEC 9216
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
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

5. NIST standards related to software security
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Design to mitigate any single source of complete compromise
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

6. Exposure factor (EF)
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

7. Annual Loss Expectancy (ALE)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

8. EALs levels
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

9. Authorization
Access request by a subject to an object is mediated each time and every time.
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

10. Operation Controls
Access request by a subject to an object is mediated each time and every time.
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

11. Residual Risk
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Number of incidents that can be expected in a year
Support for accreditation and certification bodies that audit and certify ISMS
Risk remains after the implementation of mitigating security controls

12. Vulnerability
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

13. Popular guides developed by OWASP
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Development guide - Code Review Guide - Testing Guide
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

14. Least privilege
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Authentication
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
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

15. Challenges in implementing auditing/logging
Access request by a subject to an object is mediated each time and every time.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

16. ISO /IEC 27000:2009
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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

17. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

18. Security Policies

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

19. ISO/IEC 15408
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
Secure applicatios running on secure hosts (systems) in a secure network
Provides Common Criteria to evaluate IT security product
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

20. Accountability
Security controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

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

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

23. Complete mediation
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Access request by a subject to an object is mediated each time and every time.
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
Confidentiality - Integrity - Availability

24. General security concept
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
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

25. 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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
OWASP - ITIL

26. Compartmentalization
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

27. Vulnerabilities repositories
Provides Common Criteria to evaluate IT security product
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Number of incidents that can be expected in a year
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

28. Flaw Hypothesis Method (FHM)
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Predetermined number of user error allowed before recording it as a security violation

29. OCTAVE
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
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

30. PCI DSS
Authentication
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans

31. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Technical - Management - Operational
Security functionality is easy to use and transparent
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

32. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Technical - Management - Operational
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

33. Integrity
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Confidentiality - Integrity - Availability

34. Single point failure
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
Design to mitigate any single source of complete compromise
Predetermined number of user error allowed before recording it as a security violation
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

35. Security profile of a software
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
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. Least common mechanism
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

37. Software security risk management methodologies
Authentication
OWASP - ITIL
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

38. Counter measures
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Security controls applied after a threat has been materialized

39. DREAD
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

40. After identification step is...
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Covers the necessary procedures and tools to validate software assurance
Authentication
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

41. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

42. Multifactor authentication
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Indicator of magnitude risk in a year ALE = SLE * ARO

43. Holistic Security in software
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Secure applicatios running on secure hosts (systems) in a secure network
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

44. OWASP Top 10
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Periodic publication by OWASP for top 10 Web application security vulnerabilites
OWASP - ITIL

45. Core Security Concept
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Confidentiality - Integrity - Availability

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

47. Categories of controls
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Technical - Management - Operational

48. Configurations Parameters Management
Design to mitigate any single source of complete compromise
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of 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

49. Security design principles
Predetermined number of user error allowed before recording it as a security violation
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

50. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met