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. Benefits of coding standards
Support for accreditation and certification bodies that audit and certify ISMS
Predetermined number of user error allowed before recording it as a security violation
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

2. STRIDE
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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Periodic publication by OWASP for top 10 Web application security vulnerabilites

3. Security profile of a software
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Provides Common Criteria to evaluate IT security product
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Protection against unauthorized information disclosure. It helps maintaining privacy

4. PCI DSS
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Support for accreditation and certification bodies that audit and certify ISMS
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 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

5. OWASP Top 10
Technical - Management - Operational
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

6. Multifactor authentication
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering 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

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

8. ISO/IEC 9216
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Design to mitigate any single source of complete compromise
Authentication

9. Develop hack resilient software
Access request by a subject to an object is mediated each time and every time.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Development guide - Code Review Guide - Testing Guide

10. Session Management
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Technical - Management - Operational
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

11. Security Risk Management Discipline
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
The likelihood that a threat can result into an incident. This is the overall risk of a system
Confidentiality - Integrity - Availability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

12. Compartmentalization
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

13. Phsychological acceptability
Indicator of magnitude risk in a year ALE = SLE * ARO
Security functionality is easy to use and transparent
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

14. Single point failure
Design to mitigate any single source of complete compromise
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

15. Software security risk management methodologies
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Indicator of magnitude risk in a year ALE = SLE * ARO
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

16. OWASP development guide
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Provides Common Criteria to evaluate IT security product

17. 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
Technical - Management - Operational
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

18. Complete mediation
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

19. After identification step is...
Support policies at a granular and specific level - Can be characterized as internal and external
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.
Security functionality is easy to use and transparent
Authentication

20. FIPS140-2 (Security requirement for cryptographic modules)
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Support policies at a granular and specific level - Can be characterized as internal and external

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

22. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

23. Risk management process
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
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
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

24. Take-Grant Model
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

25. Counter measures
Security controls applied after a threat has been materialized
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

26. Least privilege
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
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.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

27. Access Matrix model

28. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Security controls applied after a threat has been materialized
Predetermined number of user error allowed before recording it as a security violation
Support for accreditation and certification bodies that audit and certify ISMS

29. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
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.
Indicator of magnitude risk in a year ALE = SLE * ARO
Secure applicatios running on secure hosts (systems) in a secure network

30. Flaw Hypothesis Method (FHM)
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
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.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Periodic publication by OWASP for top 10 Web application security vulnerabilites

31. ISO/IEC 15408
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Provides Common Criteria to evaluate IT security product

32. Accountability
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

33. Single Loss Expectancy (SLE)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

34. Vulnerabilities repositories
Provides Common Criteria to evaluate IT security product
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

35. Holistic Security in software
Design to mitigate any single source of complete compromise
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Secure applicatios running on secure hosts (systems) in a secure network
The likelihood that a threat can result into an incident. This is the overall risk of a system

36. Security Policies

37. General security concept
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Confidentiality - Integrity - Availability

38. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
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
Protection against unauthorized information disclosure. It helps maintaining privacy

39. Implementation challenges
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Security functionality is easy to use and transparent
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

40. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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

41. Auditing
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

42. FIPS 197 (Advance Cryptographic standards - AES)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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.

43. Least common mechanism
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

44. Residual Risk
Risk remains after the implementation of mitigating security controls
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Still under development - aimsto address ISMS implementation guidance
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

45. Authorization
Secure applicatios running on secure hosts (systems) in a secure network
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Design to mitigate any single source of complete compromise

46. Confidentiality
Security functionality is easy to use and transparent
Protection against unauthorized information disclosure. It helps maintaining privacy
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

47. Operation Controls
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.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

48. Exposure factor (EF)
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.
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:

49. Categories of controls
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Technical - Management - Operational
Development guide - Code Review Guide - Testing Guide

50. Security Controls
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards