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. Single point failure
Covers the necessary procedures and tools to validate software assurance
Design to mitigate any single source of complete compromise
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Security functionality is easy to use and transparent

2. ISO/IEC 27005:2008
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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:
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

3. Software security risk management methodologies
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

4. OWASP Top 10
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

5. ISO/IEC 27002:2005
Indicator of magnitude risk in a year ALE = SLE * ARO
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

6. Security profile of a software
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

7. Least 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
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
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

8. Benefits of coding standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Confidentiality - Integrity - Availability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

9. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

10. Non Repudiation
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

11. Access Matrix model

12. Categories of controls
Technical - Management - Operational
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

13. Compartmentalization
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Security controls applied after a threat has been materialized
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

14. Single Loss Expectancy (SLE)
Confidentiality - Integrity - Availability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Protection against unauthorized information disclosure. It helps maintaining privacy
estimate potential loss of a single incident: SLE = Asset value * EF(%)

15. Properties of secure software
Confidentiality - Integrity - Availability
Authentication
Security controls applied to mitigate a threat before it materializes
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

16. After identification step is...
Development guide - Code Review Guide - Testing Guide
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Authentication
Covers the necessary procedures and tools to validate software assurance

17. Core Security Concept
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Confidentiality - Integrity - Availability
Security controls applied after a threat has been materialized
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

18. ISO/IEC 21827:2008
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 the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

19. Availability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

20. Security Risk Management Discipline
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

21. Challenges in implementing auditing/logging
Support for accreditation and certification bodies that audit and certify ISMS
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

22. Examples of Security Standards
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
Confidentiality - Integrity - Availability
Risk remains after the implementation of mitigating security controls

23. STRIDE
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
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
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

24. Security Policies

25. Operation Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

26. Holistic Security in software
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Provides Common Criteria to evaluate IT security product
Secure applicatios running on secure hosts (systems) in a secure network
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

27. Total Risk
Security controls applied to mitigate a threat before it materializes
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

28. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on 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
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

29. Exposure factor (EF)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Design to mitigate any single source of complete compromise
estimate potential loss of a single incident: SLE = Asset value * EF(%)

30. Integrity
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

31. ISO/IEC 27001:2005
The likelihood that a threat can result into an incident. This is the overall risk of a system
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

32. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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.
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Provides Common Criteria to evaluate IT security product

33. FIPS 201
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Support for accreditation and certification bodies that audit and certify ISMS
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

34. 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
Technical - Management - Operational
Security controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls

35. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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 functionality is easy to use and transparent

36. Develop hack resilient software
Protection against unauthorized information disclosure. It helps maintaining privacy
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Access request by a subject to an object is mediated each time and every time.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

37. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Covers the necessary procedures and tools to validate software assurance
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

38. Economy of mechanism
Development guide - Code Review Guide - Testing Guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

39. Phsychological acceptability
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Covers the necessary procedures and tools to validate software assurance
Security functionality is easy to use and transparent
Technical - Management - Operational

40. Security design principles
Risk remains after the implementation of mitigating security controls
Indicator of magnitude risk in a year ALE = SLE * ARO
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 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

41. ISO/IEC 27003
Protection against unauthorized information disclosure. It helps maintaining privacy
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Secure applicatios running on secure hosts (systems) in a secure network
Still under development - aimsto address ISMS implementation guidance

42. FIPS140-2 (Security requirement for cryptographic modules)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Technical - Management - Operational
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

43. Accountability
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security functionality is easy to use and transparent

44. 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
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

45. ISO/IEC 9216
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans

46. OWASP development guide
Confidentiality - Integrity - Availability
The likelihood that a threat can result into an incident. This is the overall risk of a system
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

47. Technical Controls
Technical - Management - Operational
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

48. Common best practices significant to Sofware Security
OWASP - ITIL
Provides Common Criteria to evaluate IT security product
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

49. OWASP Code Review Guide
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Still under development - aimsto address ISMS implementation guidance

50. Residual Risk
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Risk remains after the implementation of mitigating security 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