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. Take-Grant Model
Provides Common Criteria to evaluate IT security product
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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. Clipping level
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Predetermined number of user error allowed before recording it as a security violation

3. Configurations Parameters Management
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Indicator of magnitude risk in a year ALE = SLE * ARO

4. Non Repudiation
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
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

5. Security Risk Management Discipline
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

6. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

7. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Confidentiality - Integrity - Availability

8. ISO /IEC 27000:2009
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
Confidentiality - Integrity - Availability
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

9. Categories of controls
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
Technical - Management - Operational
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

10. General security concept
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Access request by a subject to an object is mediated each time and every time.
Technical - Management - Operational

11. Authentication
Risk remains after the implementation of mitigating security controls
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

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

13. Compartmentalization
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

14. Security profile of a software
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Provides Common Criteria to evaluate IT security product

15. ISO/IEC 27003
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Still under development - aimsto address ISMS implementation guidance
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

16. Phsychological acceptability
OWASP - ITIL
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Security functionality is easy to use and transparent

17. Risk management process
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
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

18. After identification step is...
Design to mitigate any single source of complete compromise
Authentication
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

19. Benefits of coding standards
Design to mitigate any single source of complete compromise
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Confidentiality - Integrity - Availability

20. FIPS140-2 (Security requirement for cryptographic modules)
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

21. Operation Controls
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Number of incidents that can be expected in a year
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

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

23. 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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk remains after the implementation of mitigating security controls
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

24. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

25. Integrity
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Risk remains after the implementation of mitigating security controls
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Security controls applied after a threat has been materialized

26. Security design principles
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Specifies 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

27. DREAD
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Design to mitigate any single source of complete compromise

28. Least common mechanism
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

29. Flaw Hypothesis Method (FHM)
Still under development - aimsto address ISMS implementation guidance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Security controls applied after a threat has been materialized

30. STRIDE
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
Design to mitigate any single source of complete compromise
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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

31. Technical 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
Secure applicatios running on secure hosts (systems) in a secure network
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

32. Challenges in implementing auditing/logging
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

33. Least privilege
Provides Common Criteria to evaluate IT security product
Security controls applied to mitigate a threat before it materializes
Development guide - Code Review Guide - Testing Guide
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

34. Information Security Models
Security controls applied after a threat has been materialized
OWASP - ITIL
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
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. Examples of Security Standards
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Predetermined number of user error allowed before recording it as a security violation

36. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

37. Economy of mechanism
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

38. Safeguards
Security controls applied to mitigate a threat before it materializes
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Confidentiality - Integrity - Availability
Security controls applied after a threat has been materialized

39. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

40. OWASP Code Review Guide
Support policies at a granular and specific level - Can be characterized as internal and external
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 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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

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

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

43. Common best practices significant to Sofware Security
Indicator of magnitude risk in a year ALE = SLE * ARO
Risk remains after the implementation of mitigating security controls
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
OWASP - ITIL

44. ISO/IEC 21827:2008
Predetermined number of user error allowed before recording it as a security violation
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)

45. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Still under development - aimsto address ISMS implementation guidance
Confidentiality - Integrity - Availability

46. Open design
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Security controls applied after a threat has been materialized
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
Security functionality is easy to use and transparent

47. Counter measures
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
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 controls applied after a threat has been materialized
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

48. Vulnerabilities repositories
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Confidentiality - Integrity - Availability

49. ISO/IEC 27001:2005
Protection against unauthorized information disclosure. It helps maintaining privacy
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Technical - Management - Operational
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

50. FIPS 201
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors