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

2. Implementation challenges
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Still under development - aimsto address ISMS implementation guidance
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

3. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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.
Support for accreditation and certification bodies that audit and certify ISMS

4. Authorization
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
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
Provides Common Criteria to evaluate IT security product
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

5. FIPS 197 (Advance Cryptographic standards - AES)
Development guide - Code Review Guide - Testing Guide
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

6. Take-Grant Model
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Confidentiality - Integrity - Availability

7. Management 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Security controls applied after a threat has been materialized

8. Residual Risk
Risk remains after the implementation of mitigating security controls
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Confidentiality - Integrity - Availability

9. Threat
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Number of incidents that can be expected in a year
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

10. Examples of Security Standards
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

11. Total Risk
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

12. OWASP development guide
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

13. Integrity
Access request by a subject to an object is mediated each time and every time.
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
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
Still under development - aimsto address ISMS implementation guidance

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

15. Counter measures
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security controls applied after a threat has been materialized

16. Categories of 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
Technical - Management - Operational
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

17. Least privilege
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Security controls applied to mitigate a threat before it materializes
Still under development - aimsto address ISMS implementation guidance

18. Information Security Models
Support for accreditation and certification bodies that audit and certify 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
Confidentiality - Integrity - Availability
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

19. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

20. Clipping level
Confidentiality - Integrity - Availability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Predetermined number of user error allowed before recording it as a security violation

21. Software security risk management methodologies
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

22. OCTAVE
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

23. Flaw Hypothesis Method (FHM)
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

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

25. Security Policies

26. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Support policies at a granular and specific level - Can be characterized as internal and external
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

27. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

28. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

29. Access Matrix model

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

31. Availability
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Support for accreditation and certification bodies that audit and certify ISMS
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

32. General security concept
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

33. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Development guide - Code Review Guide - Testing Guide
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

34. Annual Loss Expectancy (ALE)
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
OWASP - ITIL
Indicator of magnitude risk in a year ALE = SLE * ARO
estimate potential loss of a single incident: SLE = Asset value * EF(%)

35. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

36. NIST standards related to software security
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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

37. Benefits of coding standards
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

38. Security Risk Management Discipline
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

39. OWASP Code Review Guide
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
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

40. Security profile of a software
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

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

42. Security design principles
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
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
Security functionality is easy to use and transparent

43. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Development guide - Code Review Guide - Testing Guide
Periodic publication by OWASP for top 10 Web application security vulnerabilites

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

45. Common best practices significant to Sofware Security
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
OWASP - ITIL
Indicator of magnitude risk in a year ALE = SLE * ARO
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

46. ISO/IEC 27003
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
Still under development - aimsto address ISMS implementation guidance
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

47. Auditing
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
Still under development - aimsto address ISMS implementation guidance
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

48. Session Management
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Technical - Management - Operational
Development guide - Code Review Guide - Testing Guide

49. FIPS 201
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
OWASP - ITIL
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

50. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Support policies at a granular and specific level - Can be characterized as internal and external
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