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. Session Management
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
Provides Common Criteria to evaluate IT security product
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
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

2. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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. Total Risk
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
The likelihood that a threat can result into an incident. This is the overall risk of a system
Support policies at a granular and specific level - Can be characterized as internal and external
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

4. Authorization
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Security functionality is easy to use and transparent
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

5. Technical Controls
The likelihood that a threat can result into an incident. This is the overall risk of a system
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

6. Annual Loss Expectancy (ALE)
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk remains after the implementation of mitigating security controls

7. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

8. 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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Protection against unauthorized information disclosure. It helps maintaining privacy

9. Authentication
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
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

10. After identification step is...
OWASP - ITIL
Provides Common Criteria to evaluate IT security product
Authentication
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

11. General security concept
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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

12. Core Security Concept
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
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
Confidentiality - Integrity - Availability
Design to mitigate any single source of complete compromise

13. ISO/IEC 27002:2005
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Covers the necessary procedures and tools to validate software assurance
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

14. Implementation challenges
Design to mitigate any single source of complete compromise
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

15. Error and exception management
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Predetermined number of user error allowed before recording it as a security violation
Number of incidents that can be expected in a year

16. Clipping level
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Predetermined number of user error allowed before recording it as a security violation
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

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

18. ISO /IEC 27000:2009
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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
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

19. Single point failure
Design to mitigate any single source of complete compromise
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Authentication
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

20. FIPS 197 (Advance Cryptographic standards - AES)
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
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

21. Multifactor authentication
Security functionality is easy to use and transparent
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

22. NIST standards related to software security
Access request by a subject to an object is mediated each time and every time.
Security functionality is easy to use and transparent
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

23. Exposure factor (EF)
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

24. ISO/IEC 27006:2007
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Support for accreditation and certification bodies that audit and certify ISMS
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information

25. Single Loss Expectancy (SLE)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Confidentiality - Integrity - Availability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
estimate potential loss of a single incident: SLE = Asset value * EF(%)

26. Security Risk Management Discipline
Security controls applied after a threat has been materialized
Risk remains after the implementation of mitigating security controls
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

27. Counter measures
Protection against unauthorized information disclosure. It helps maintaining privacy
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Security controls applied after a threat has been materialized

28. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented 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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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

29. 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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
OWASP - ITIL
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

30. FIPS140-2 (Security requirement for cryptographic modules)
Covers the necessary procedures and tools to validate software assurance
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Development guide - Code Review Guide - Testing 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

31. Security Standards
Security controls applied to mitigate a threat before it materializes
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
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

32. Configurations Parameters 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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Security functionality is easy to use and transparent

33. ISO/IEC 9216
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

34. Phsychological acceptability
Security functionality is easy to use and transparent
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

35. DREAD
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Secure applicatios running on secure hosts (systems) in a secure network
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

36. Benefits of coding standards
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

37. Holistic Security in software
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Secure applicatios running on secure hosts (systems) in a secure network
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Predetermined number of user error allowed before recording it as a security violation

38. Integrity
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
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
OWASP - ITIL
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

39. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Security functionality is easy to use and transparent
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

40. Security design principles
Security controls applied to mitigate a threat before it materializes
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
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
Secure applicatios running on secure hosts (systems) in a secure network

41. Availability
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.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
Security controls applied after a threat has been materialized

42. Security Policies

43. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Security functionality is easy to use and transparent

44. Management Controls
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

45. Complete mediation
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
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
Access request by a subject to an object is mediated each time and every time.

46. Challenges in implementing auditing/logging
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
OWASP - ITIL

47. STRIDE
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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

48. Categories of controls
Technical - Management - Operational
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software

49. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of 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

50. Operation Controls
Design to mitigate any single source of complete compromise
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors