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. Residual Risk
Risk remains after the implementation of mitigating security controls
Still under development - aimsto address ISMS implementation guidance
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

2. STRIDE
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Technical - Management - Operational
Secure applicatios running on secure hosts (systems) in a secure network

3. 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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

4. Session Management
Security functionality is easy to use and transparent
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

5. Develop hack resilient software
OWASP - ITIL
Indicator of magnitude risk in a year ALE = SLE * ARO
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Confidentiality - Integrity - Availability

6. Phsychological acceptability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Security functionality is easy to use and transparent

7. Operation Controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

8. DREAD
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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

9. Vulnerabilities repositories
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

10. ISO/IEC 27003
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Still under development - aimsto address ISMS implementation guidance
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
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

11. Access Matrix model

12. Auditing
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Security controls applied after a threat has been materialized
Periodic publication by OWASP for top 10 Web application security vulnerabilites

13. Take-Grant Model
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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.
Confidentiality - Integrity - Availability

14. Total Risk
Still under development - aimsto address ISMS implementation guidance
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

15. OWASP development guide
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Provides Common Criteria to evaluate IT security product
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

16. OWASP testing guide
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Number of incidents that can be expected in a year

17. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

18. Vulnerability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Protection against unauthorized information disclosure. It helps maintaining privacy
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
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

19. ISO/IEC 15408
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
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational

20. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Secure applicatios running on secure hosts (systems) in a secure network

21. Safeguards
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security controls applied to mitigate a threat before it materializes
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

22. Accountability
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

23. Properties of secure software
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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(%)

24. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify 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
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
Secure applicatios running on secure hosts (systems) in a secure network

25. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Number of incidents that can be expected in a year

26. EALs levels
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
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
Security functionality is easy to use and transparent
Still under development - aimsto address ISMS implementation guidance

27. Categories of controls
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Technical - Management - Operational
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

28. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Number of incidents that can be expected in a year
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

29. Security Risk Management Discipline
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Support for accreditation and certification bodies that audit and certify ISMS
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

30. ISO/IEC 27005:2008
Covers the necessary procedures and tools to validate software assurance
Number of incidents that can be expected in a year
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

31. Counter measures
Design to mitigate any single source of complete compromise
Security controls applied after a threat has been materialized
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

32. NIST standards related to software security
Indicator of magnitude risk in a year ALE = SLE * ARO
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
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

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

34. Least privilege
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Number of incidents that can be expected in a year

35. FIPS 197 (Advance Cryptographic standards - AES)
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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

36. Error and exception management
Covers the necessary procedures and tools to validate software assurance
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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

37. ISO/IEC 27002:2005
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Secure applicatios running on secure hosts (systems) in a secure network

38. OWASP Top 10
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
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
Authentication

39. Popular guides developed by OWASP
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
OWASP - ITIL
Development guide - Code Review Guide - Testing Guide
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

40. Software security risk management methodologies
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

41. Open design
Access request by a subject to an object is mediated each time and every time.
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Predetermined number of user error allowed before recording it as a security violation

42. Economy of mechanism
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Support for accreditation and certification bodies that audit and certify ISMS
OWASP - ITIL

43. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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

44. Information Security Models
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
OWASP - ITIL

45. Confidentiality
Indicator of magnitude risk in a year ALE = SLE * ARO
Authentication
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Protection against unauthorized information disclosure. It helps maintaining privacy

46. Authentication
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security controls applied after a threat has been materialized
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

47. Authorization
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
Security functionality is easy to use and transparent
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

48. Availability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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.
Indicator of magnitude risk in a year ALE = SLE * ARO

49. Core Security Concept
Number of incidents that can be expected in a year
Confidentiality - Integrity - Availability
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

50. Exposure factor (EF)
Support policies at a granular and specific level - Can be characterized as internal and external
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
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.