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. Configurations Parameters Management
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Still under development - aimsto address ISMS implementation guidance
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

2. Security Controls
Development guide - Code Review Guide - Testing Guide
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
Design to mitigate any single source of complete compromise
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

3. FIPS 197 (Advance Cryptographic standards - AES)
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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

4. Authorization
Support policies at a granular and specific level - Can be characterized as internal and external
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Predetermined number of user error allowed before recording it as a security violation
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. Examples of Security Standards
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

6. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

7. Error and exception management
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

8. Threat
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Indicator of magnitude risk in a year ALE = SLE * ARO
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

9. Develop hack resilient software
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Design to mitigate any single source of complete compromise

10. ISO /IEC 27000:2009
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Secure applicatios running on secure hosts (systems) in a secure network
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
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
Security controls applied after a threat has been materialized

12. Security Policies

13. Complete mediation
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Access request by a subject to an object is mediated each time and every time.
Provides Common Criteria to evaluate IT security product
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

14. Phsychological acceptability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Security functionality is easy to use and transparent
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

15. Security profile of a software
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Covers the necessary procedures and tools to validate software assurance
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

16. Integrity
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
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
Support policies at a granular and specific level - Can be characterized as internal and external

17. Multifactor authentication
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.
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

18. Counter measures
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Security controls applied after a threat has been materialized
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Development guide - Code Review Guide - Testing Guide

19. STRIDE
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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

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

21. Technical Controls
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

22. FIPS 201
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
Secure applicatios running on secure hosts (systems) in a secure network
Periodic publication by OWASP for top 10 Web application security vulnerabilites

23. Session Management
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

24. Common best practices significant to Sofware Security
OWASP - ITIL
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

25. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security functionality is easy to use and transparent

26. Authentication
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
Secure applicatios running on secure hosts (systems) in a secure network
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

27. General security concept
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Authentication

28. Residual Risk
Risk remains after the implementation of mitigating security controls
OWASP - ITIL
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)

29. PCI DSS
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

30. Flaw Hypothesis Method (FHM)
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

31. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

32. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

33. Confidentiality
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Protection against unauthorized information disclosure. It helps maintaining privacy
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

34. 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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Access request by a subject to an object is mediated each time and every time.

35. ISO/IEC 21827:2008
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Risk remains after the implementation of mitigating security controls
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

36. ISO/IEC 27003
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Still under development - aimsto address ISMS implementation guidance

37. Open design
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Predetermined number of user error allowed before recording it as a security violation
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
Authentication

38. Access Matrix model

39. ISO/IEC 9216
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Technical - Management - Operational
Risk remains after the implementation of mitigating security controls

40. Management Controls
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Covers the necessary procedures and tools to validate software assurance

41. Risk management process
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Indicator of magnitude risk in a year ALE = SLE * ARO
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

42. OWASP development guide
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
Still under development - aimsto address ISMS implementation guidance
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
The likelihood that a threat can result into an incident. This is the overall risk of a system

43. 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
Support for accreditation and certification bodies that audit and certify ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

44. OCTAVE
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Indicator of magnitude risk in a year ALE = SLE * ARO
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

45. Annual Loss Expectancy (ALE)
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security functionality is easy to use and transparent
Indicator of magnitude risk in a year ALE = SLE * ARO

46. Core Security Concept
Support policies at a granular and specific level - Can be characterized as internal and external
Development guide - Code Review Guide - Testing Guide
Confidentiality - Integrity - Availability
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

47. Vulnerabilities repositories
Number of incidents that can be expected in a year
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)
Support policies at a granular and specific level - Can be characterized as internal and external

48. Take-Grant Model
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Authentication

49. Categories of controls
Technical - Management - Operational
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

50. DREAD
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering 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
Provides Common Criteria to evaluate IT security product
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability