Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Subjects : certifications, csslp, it-skills

Instructions:

Answer 50 questions in 30 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. General security concept
Still under development - aimsto address ISMS implementation guidance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

2. FIPS 197 (Advance Cryptographic standards - AES)
Covers the necessary procedures and tools to validate software assurance
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Development guide - Code Review Guide - Testing Guide

3. Annual Rate of Occurence (ARO)
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
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
Number of incidents that can be expected in a year

4. EALs levels
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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

5. Security Standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
The likelihood that a threat can result into an incident. This is the overall risk of a 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
Support policies at a granular and specific level - Can be characterized as internal and external

6. Core Security Concept
Confidentiality - Integrity - Availability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

7. Information Security Models
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
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

8. Examples of Security Standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

9. Counter measures
Security controls applied after a threat has been materialized
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:
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

10. 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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Technical - Management - Operational

11. OWASP testing guide
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Confidentiality - Integrity - Availability
Covers the necessary procedures and tools to validate software assurance
Technical - Management - Operational

12. Single point failure
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
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
Design to mitigate any single source of complete compromise

13. FIPS 201
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
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
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

14. ISO/IEC 27002:2005
Security controls applied to mitigate a threat before it materializes
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Access request by a subject to an object is mediated each time and every time.
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

15. ISO/IEC 27006:2007
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
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
Support for accreditation and certification bodies that audit and certify ISMS

16. Authorization
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
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
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
Confidentiality - Integrity - Availability

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

18. Multifactor authentication
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Security functionality is easy to use and transparent

19. Annual Loss Expectancy (ALE)
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
Covers the necessary procedures and tools to validate software assurance
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

20. Security Controls
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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

21. Benefits of coding standards
Authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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.

22. Challenges in implementing auditing/logging
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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

23. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Covers the necessary procedures and tools to validate software assurance
The likelihood that a threat can result into an incident. This is the overall risk of a system

24. Security design principles
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

25. Software security risk management methodologies
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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

26. Access Matrix model

27. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
The likelihood that a threat can result into an incident. This is the overall risk of a 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

28. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

29. Risk management process
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
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
Provides Common Criteria to evaluate IT security product

30. Non Repudiation
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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.
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
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

31. ISO/IEC 27005:2008
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

32. Vulnerability
Authentication
Development guide - Code Review Guide - Testing Guide
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

33. Take-Grant Model
Development guide - Code Review Guide - Testing Guide
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
Security controls applied to mitigate a threat before it materializes
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

34. Common best practices significant to Sofware Security
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
OWASP - ITIL
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)

35. NIST standards related to software security
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
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

36. 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
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

37. Confidentiality
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security controls applied after a threat has been materialized
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.
Protection against unauthorized information disclosure. It helps maintaining privacy

38. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

39. Open design
Confidentiality - Integrity - Availability
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

40. 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
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
Number of incidents that can be expected in a year

41. Economy of mechanism
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

42. OWASP Code Review Guide
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

43. ISO/IEC 15408
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Development guide - Code Review Guide - Testing Guide
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Provides Common Criteria to evaluate IT security product

44. Operation Controls
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

45. ISO /IEC 27000:2009
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
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
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied after a threat has been materialized

46. Compartmentalization
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

47. ISO/IEC 27003
Security controls applied after a threat has been materialized
Development guide - Code Review Guide - Testing Guide
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Still under development - aimsto address ISMS implementation guidance

48. Develop hack resilient software
OWASP - ITIL
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk remains after the implementation of mitigating security controls
Access request by a subject to an object is mediated each time and every time.

49. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Number of incidents that can be expected in a year
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

50. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Risk remains after the implementation of mitigating 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
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