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. Integrity
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Still under development - aimsto address ISMS implementation guidance
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

2. Authentication
Security controls applied to mitigate a threat before it materializes
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: 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

3. After identification step is...
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Authentication

4. Security Risk Management Discipline
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
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
Development guide - Code Review Guide - Testing Guide

5. 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
Covers the necessary procedures and tools to validate software assurance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

6. 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
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Technical - Management - Operational

7. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Number of incidents that can be expected in a year
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

8. STRIDE
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
Predetermined number of user error allowed before recording it as a security violation
Risk remains after the implementation of mitigating security controls
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

9. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Support for accreditation and certification bodies that audit and certify 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
Support policies at a granular and specific level - Can be characterized as internal and external

10. Technical Controls
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

11. Vulnerabilities repositories
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

12. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Number of incidents that can be expected in a year
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

13. Multifactor authentication
OWASP - ITIL
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

14. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Access request by a subject to an object is mediated each time and every time.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

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

16. 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
Covers the necessary procedures and tools to validate software assurance
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

17. Session Management
The likelihood that a threat can result into an incident. This is the overall risk of a system
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Authentication

18. Clipping level
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Predetermined number of user error allowed before recording it as a security violation
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

19. Core Security Concept
Security controls applied to mitigate a threat before it materializes
Confidentiality - Integrity - Availability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

20. Flaw Hypothesis Method (FHM)
Design to mitigate any single source of complete compromise
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

21. Availability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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.
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

22. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Access request by a subject to an object is mediated each time and every time.
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
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

23. Security Policies

24. Challenges in implementing auditing/logging
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Covers the necessary procedures and tools to validate software assurance
Risk remains after the implementation of mitigating security controls

25. Safeguards
Security controls applied to mitigate a threat before it materializes
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
Confidentiality - Integrity - Availability

26. 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
Risk remains after the implementation of mitigating security controls
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

27. General security concept
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

28. Single Loss Expectancy (SLE)
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
estimate potential loss of a single incident: SLE = Asset value * EF(%)

29. EALs levels
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

30. Counter measures
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Security controls applied after a threat has been materialized
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

31. Develop hack resilient software
Support for accreditation and certification bodies that audit and certify ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

32. NIST standards related to software security
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
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
Security controls applied to mitigate a threat before it materializes
Protection against unauthorized information disclosure. It helps maintaining privacy

33. Annual Rate of Occurence (ARO)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Number of incidents that can be expected in a year

34. 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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Covers the necessary procedures and tools to validate software assurance
Predetermined number of user error allowed before recording it as a security violation

35. Operation 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
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
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

36. Non Repudiation
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
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
Support for accreditation and certification bodies that audit and certify ISMS
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

37. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Predetermined number of user error allowed before recording it as a security violation
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

38. Software security risk management methodologies
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.
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

39. DREAD
Confidentiality - Integrity - Availability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

40. Error and exception management
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
Access request by a subject to an object is mediated each time and every time.
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
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.

41. ISO/IEC 27002:2005
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
Support policies at a granular and specific level - Can be characterized as internal and external
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

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

43. Security Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

44. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

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

46. ISO /IEC 27000:2009
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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 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
Access request by a subject to an object is mediated each time and every time.

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

48. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

49. ISO/IEC 21827:2008
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
The likelihood that a threat can result into an incident. This is the overall risk of a system
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

50. Categories of controls
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Technical - Management - Operational