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. Annual Loss Expectancy (ALE)
Confidentiality - Integrity - Availability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Indicator of magnitude risk in a year ALE = SLE * ARO
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

2. FIPS140-2 (Security requirement for cryptographic modules)
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Provides Common Criteria to evaluate IT security product
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

3. Information Security Models
Development guide - Code Review Guide - Testing Guide
Authentication
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
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

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

5. ISO/IEC 27002:2005
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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

6. Security design principles
Secure applicatios running on secure hosts (systems) in a secure network
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

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

8. Security Policies

9. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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

10. Properties of secure software
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

11. Technical 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent

12. Multifactor authentication
Security functionality is easy to use and transparent
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

13. Flaw Hypothesis Method (FHM)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

14. Availability
Security controls applied to mitigate a threat before it materializes
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
Predetermined number of user error allowed before recording it as a security violation
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.

15. ISO/IEC 15408
Security functionality is easy to use and transparent
Security controls applied after a threat has been materialized
Provides Common Criteria to evaluate IT security product
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

16. Single Loss Expectancy (SLE)
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
OWASP - ITIL

17. Vulnerability
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
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

18. Compartmentalization
Risk remains after the implementation of mitigating security controls
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

19. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
OWASP - ITIL

20. EALs levels
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
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

21. Counter measures
Access request by a subject to an object is mediated each time and every time.
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Security controls applied after a threat has been materialized
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

22. Software security risk management methodologies
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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.

23. Access Matrix model

24. Security Risk Management Discipline
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
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

25. Core Security Concept
Predetermined number of user error allowed before recording it as a security violation
Access request by a subject to an object is mediated each time and every time.
Confidentiality - Integrity - Availability
Secure applicatios running on secure hosts (systems) in a secure network

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

27. Total Risk
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
The likelihood that a threat can result into an incident. This is the overall risk of a system
Covers the necessary procedures and tools to validate software assurance

28. ISO/IEC 27005:2008
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

29. Authentication
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Support policies at a granular and specific level - Can be characterized as internal and external

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

31. NIST standards related to software security
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
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

32. OWASP development guide
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

33. Common best practices significant to Sofware Security
Periodic publication by OWASP for top 10 Web application security vulnerabilites
OWASP - ITIL
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

34. Safeguards
Security controls applied to mitigate a threat before it materializes
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

35. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Provides Common Criteria to evaluate IT security product
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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. Residual Risk
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
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
Risk remains after the implementation of mitigating security controls
Development guide - Code Review Guide - Testing Guide

37. Management 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
Indicator of magnitude risk in a year ALE = SLE * ARO
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

38. 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
Support policies at a granular and specific level - Can be characterized as internal and external
Secure applicatios running on secure hosts (systems) in a secure network
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

39. Exposure factor (EF)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
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

40. Confidentiality
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Still under development - aimsto address ISMS implementation guidance
Protection against unauthorized information disclosure. It helps maintaining privacy
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

41. Categories of 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
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 request by a subject to an object is mediated each time and every time.

42. Develop hack resilient software
Security controls applied after a threat has been materialized
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

43. Integrity
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
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

44. OWASP Code Review Guide
Number of incidents that can be expected in a year
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Security controls applied to mitigate a threat before it materializes

45. FIPS 197 (Advance Cryptographic standards - AES)
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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

46. Holistic Security in software
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Secure applicatios running on secure hosts (systems) in a secure network
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.

47. Complete mediation
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Access request by a subject to an object is mediated each time and every time.
Periodic publication by OWASP for top 10 Web application security vulnerabilites

48. Session Management
Protection against unauthorized information disclosure. It helps maintaining privacy
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

49. Security Standards
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
Support policies at a granular and specific level - Can be characterized as internal and external
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

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