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

2. Phsychological acceptability
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.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Security functionality is easy to use and transparent
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

3. ISO/IEC 27003
Provides Common Criteria to evaluate IT security product
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Still under development - aimsto address ISMS implementation guidance

4. Operation Controls
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
Confidentiality - Integrity - Availability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

5. Security Risk Management Discipline
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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.

6. DREAD
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

7. Configurations Parameters Management
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
Technical - Management - Operational
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

8. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Indicator of magnitude risk in a year ALE = SLE * ARO
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

9. Multifactor authentication
Indicator of magnitude risk in a year ALE = SLE * ARO
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Risk remains after the implementation of mitigating security controls

10. FIPS 197 (Advance Cryptographic standards - AES)
Risk remains after the implementation of mitigating security controls
Security controls applied after a threat has been materialized
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

11. Threat
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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 mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking

12. 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
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
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
OWASP - ITIL

13. ISO/IEC 15408
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Provides Common Criteria to evaluate IT security product
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

14. Vulnerability
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

15. ISO/IEC 9216
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
Support policies at a granular and specific level - Can be characterized as internal and external
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

16. Properties of secure 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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

17. Core Security Concept
Support policies at a granular and specific level - Can be characterized as internal and external
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
Confidentiality - Integrity - Availability

18. Security Standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Support policies at a granular and specific level - Can be characterized as internal and external

19. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Confidentiality - Integrity - Availability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

20. Least privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

21. Clipping level
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Access request by a subject to an object is mediated each time and every time.
Predetermined number of user error allowed before recording it as a security violation
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

22. OWASP development guide
Provides Common Criteria to evaluate IT security product
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

23. ISO/IEC 27001:2005
Covers the necessary procedures and tools to validate software assurance
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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

24. Single Loss Expectancy (SLE)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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(%)
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

25. 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
Support policies at a granular and specific level - Can be characterized as internal and external
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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.

26. Software security risk management methodologies
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security controls applied after a threat has been materialized

27. NIST standards related to software security
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Authentication

28. Access Matrix model

29. ISO/IEC 27005:2008
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
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
Covers the necessary procedures and tools to validate software assurance
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

30. Management Controls
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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.

31. Authorization
Access request by a subject to an object is mediated each time and every time.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

32. 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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

33. Counter measures
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

34. Develop hack resilient software
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Secure applicatios running on secure hosts (systems) in a secure network
Security controls applied after a threat has been materialized

35. Integrity
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Support policies at a granular and specific level - Can be characterized as internal and external
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

36. Challenges in implementing auditing/logging
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

37. Annual Rate of Occurence (ARO)
Security controls applied to mitigate a threat before it materializes
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Number of incidents that can be expected in a year

38. Popular guides developed by OWASP
The likelihood that a threat can result into an incident. This is the overall risk of a system
Development guide - Code Review Guide - Testing Guide
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
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

39. Benefits of coding 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
Indicator of magnitude risk in a year ALE = SLE * ARO
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

40. Categories of controls
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Technical - Management - Operational
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

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

42. Session Management
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
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
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

43. Implementation challenges
Security controls applied after a threat has been materialized
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
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

44. FIPS140-2 (Security requirement for cryptographic modules)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

45. Risk management process
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 functionality is easy to use and transparent
Support for accreditation and certification bodies that audit and certify ISMS
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

46. ISO/IEC 27002:2005
Protection against unauthorized information disclosure. It helps maintaining privacy
Covers the necessary procedures and tools to validate software assurance
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Access request by a subject to an object is mediated each time and every time.

47. ISO/IEC 21827:2008
Security functionality is easy to use and transparent
OWASP - ITIL
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Technical - Management - Operational
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

49. General security concept
The likelihood that a threat can result into an incident. This is the overall risk of a system
Support for accreditation and certification bodies that audit and certify ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

50. Safeguards
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
Number of incidents that can be expected in a year
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Security controls applied to mitigate a threat before it materializes