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. OWASP Code Review Guide
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

2. DREAD
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

3. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify 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
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

4. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

5. Security design principles
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Confidentiality - Integrity - Availability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

6. ISO/IEC 15408
Still under development - aimsto address ISMS implementation guidance
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Provides Common Criteria to evaluate IT security product

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

8. General security concept
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

9. Safeguards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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 controls applied to mitigate a threat before it materializes
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

10. Economy of mechanism
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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. Implementation challenges
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

12. Categories of controls
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Technical - Management - Operational

13. Authentication
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Confidentiality - Integrity - Availability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

14. Counter measures
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Security controls applied after a threat has been materialized

15. ISO/IEC 27002:2005
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

16. Security Policies

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

17. Complete mediation
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Access request by a subject to an object is mediated each time and every time.
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
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

18. Compartmentalization
Technical - Management - Operational
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
The likelihood that a threat can result into an incident. This is the overall risk of a system

19. OWASP development guide
Support for accreditation and certification bodies that audit and certify ISMS
Security controls applied to mitigate a threat before it materializes
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Covers the necessary procedures and tools to validate software assurance

20. FIPS 197 (Advance Cryptographic standards - AES)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Indicator of magnitude risk in a year ALE = SLE * ARO
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

21. Total Risk
Security controls applied after a threat has been materialized
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
The likelihood that a threat can result into an incident. This is the overall risk of a system
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

22. 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
Technical - Management - Operational
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

23. Auditing
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Design to mitigate any single source of complete compromise
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

24. OWASP testing guide
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Covers the necessary procedures and tools to validate software assurance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

25. Least privilege
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Provides Common Criteria to evaluate IT security product
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

26. 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
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
Still under development - aimsto address ISMS implementation guidance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

27. ISO/IEC 9216
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Access request by a subject to an object is mediated each time and every time.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

28. EALs levels
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Covers the necessary procedures and tools to validate software assurance
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

29. Multifactor authentication
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Predetermined number of user error allowed before recording it as a security violation

30. Core Security Concept
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Confidentiality - Integrity - Availability

31. 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
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

32. Annual Rate of Occurence (ARO)
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
Number of incidents that can be expected in a year
Provides Common Criteria to evaluate IT security product

33. PCI DSS
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

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

35. Flaw Hypothesis Method (FHM)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security controls applied to mitigate a threat before it materializes

36. Examples of Security Standards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

37. Single point failure
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Design to mitigate any single source of complete compromise
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

38. Operation Controls
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
OWASP - ITIL

39. Security Risk Management Discipline
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
The likelihood that a threat can result into an incident. This is the overall risk of a system

40. Common best practices significant to Sofware Security
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
OWASP - ITIL
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Secure applicatios running on secure hosts (systems) in a secure network

41. ISO/IEC 27003
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
Number of incidents that can be expected in a year
Still under development - aimsto address ISMS implementation guidance

42. Open design
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

43. ISO/IEC 21827:2008
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

44. Accountability
OWASP - ITIL
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

45. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

46. After identification step is...
Authentication
Provides Common Criteria to evaluate IT security product
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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

47. STRIDE
OWASP - ITIL
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Protection against unauthorized information disclosure. It helps maintaining privacy

48. Confidentiality
Indicator of magnitude risk in a year ALE = SLE * ARO
Protection against unauthorized information disclosure. It helps maintaining privacy
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

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

50. Holistic Security in software
Confidentiality - Integrity - Availability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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