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. OCTAVE
Covers the necessary procedures and tools to validate software assurance
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

2. Authorization
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Authentication
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

3. FIPS 201
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

4. ISO/IEC 27003
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Still under development - aimsto address ISMS implementation guidance

5. Technical Controls
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

6. 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
Security controls applied to mitigate a threat before it materializes
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

7. Safeguards
Still under development - aimsto address ISMS implementation guidance
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Security controls applied to mitigate a threat before it materializes
Development guide - Code Review Guide - Testing Guide

8. Properties of secure software
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

9. After identification step is...
Security functionality is easy to use and transparent
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 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
Authentication

10. Security Policies

11. Access Matrix model

12. FIPS140-2 (Security requirement for cryptographic modules)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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. Residual Risk
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk remains after the implementation of mitigating security controls
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

14. Session Management
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

15. Authentication
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
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Indicator of magnitude risk in a year ALE = SLE * ARO

16. Software security risk management methodologies
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Number of incidents that can be expected in a year
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

17. Security design principles
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

18. Error and exception management
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
estimate potential loss of a single incident: SLE = Asset value * EF(%)

19. Compartmentalization
Security functionality is easy to use and transparent
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

20. Single Loss Expectancy (SLE)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
estimate potential loss of a single incident: SLE = Asset value * EF(%)
OWASP - ITIL
The likelihood that a threat can result into an incident. This is the overall risk of a system

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

22. OWASP Code Review Guide
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Technical - Management - Operational
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

23. Availability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

24. Develop hack resilient software
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information

25. Holistic Security in software
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Secure applicatios running on secure hosts (systems) in a secure network
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

26. Security 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
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Security functionality is easy to use and transparent
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

27. ISO/IEC 15408
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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.

28. Vulnerability
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
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
Authentication
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

29. Exposure factor (EF)
Development guide - Code Review Guide - Testing Guide
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Secure applicatios running on secure hosts (systems) in a secure network
Authentication

30. Common best practices significant to Sofware Security
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
OWASP - ITIL
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

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

32. Challenges in implementing auditing/logging
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

33. Least privilege
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Design to mitigate any single source of complete compromise
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

34. ISO/IEC 21827:2008
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Covers the necessary procedures and tools to validate software assurance

35. Open design
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

36. Operation Controls
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

37. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Access request by a subject to an object is mediated each time and every time.
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

38. Total Risk
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Authentication
The likelihood that a threat can result into an incident. This is the overall risk of a system

39. PCI DSS
Technical - Management - Operational
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

40. Security profile of a software
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

41. Complete mediation
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Access request by a subject to an object is mediated each time and every time.
Support for accreditation and certification bodies that audit and certify ISMS
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

42. 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
OWASP - ITIL
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

43. Clipping level
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Predetermined number of user error allowed before recording it as a security violation
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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

44. Annual Loss Expectancy (ALE)
Covers the necessary procedures and tools to validate software assurance
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

45. ISO/IEC 27005:2008
Design to mitigate any single source of complete compromise
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Support for accreditation and certification bodies that audit and certify ISMS
Provides Common Criteria to evaluate IT security product

46. ISO/IEC 27002:2005
Security functionality is easy to use and transparent
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

47. OWASP development guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

48. OWASP testing guide
Design to mitigate any single source of complete compromise
Access request by a subject to an object is mediated each time and every time.
Indicator of magnitude risk in a year ALE = SLE * ARO
Covers the necessary procedures and tools to validate software assurance

49. Benefits of coding standards
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

50. Vulnerabilities repositories
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)