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. FIPS 197 (Advance Cryptographic standards - AES)
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Technical - Management - Operational

2. Security Policies

3. Integrity
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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
The likelihood that a threat can result into an incident. This is the overall risk of a system
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

4. Implementation challenges
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

5. ISO /IEC 27000:2009
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Security controls applied after a threat has been materialized

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

7. Authorization
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

8. Clipping level
Security controls applied after a threat has been materialized
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
Security controls applied to mitigate a threat before it materializes

9. Multifactor authentication
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Still under development - aimsto address ISMS implementation guidance

10. General security concept
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

11. After identification step is...
Authentication
Design to mitigate any single source of complete compromise
Support for accreditation and certification bodies that audit and certify ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

12. Flaw Hypothesis Method (FHM)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Technical - Management - Operational
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

13. Exposure factor (EF)
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.
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

14. 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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Risk remains after the implementation of mitigating security 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.

15. Auditing
Secure applicatios running on secure hosts (systems) in a secure network
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
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

16. Develop hack resilient software
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Still under development - aimsto address ISMS implementation guidance

17. Operation Controls
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Number of incidents that can be expected in a year

18. Benefits of coding standards
Authentication
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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. ISO/IEC 27006:2007
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Support for accreditation and certification bodies that audit and certify ISMS
Security functionality is easy to use and transparent
Access request by a subject to an object is mediated each time and every time.

20. 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
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

21. Security design principles
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

22. Software security risk management methodologies
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Confidentiality - Integrity - Availability

23. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

24. ISO/IEC 27001:2005
Support for accreditation and certification bodies that audit and certify ISMS
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
Technical - Management - Operational
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

25. Session Management
Confidentiality - Integrity - Availability
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

26. Security Risk Management Discipline
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
Technical - Management - Operational
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

27. OCTAVE
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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

28. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
The likelihood that a threat can result into an incident. This is the overall risk of a system

29. ISO/IEC 9216
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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

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

31. Safeguards
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
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
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 to mitigate a threat before it materializes

32. Non Repudiation
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

33. FIPS140-2 (Security requirement for cryptographic modules)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

34. Compartmentalization
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

35. Least privilege
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
Support policies at a granular and specific level - Can be characterized as internal and external
Access request by a subject to an object is mediated each time and every time.
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

36. Annual Rate of Occurence (ARO)
OWASP - ITIL
Authentication
Number of incidents that can be expected in a year
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

37. Error and exception management
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

38. OWASP Code Review Guide
Risk remains after the implementation of mitigating security controls
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

39. PCI DSS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Design to mitigate any single source of complete compromise
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
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

40. Examples of Security Standards
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Provides Common Criteria to evaluate IT security product
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

41. 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
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

42. Annual Loss Expectancy (ALE)
Security controls applied after a threat has been materialized
Support policies at a granular and specific level - Can be characterized as internal and external
Indicator of magnitude risk in a year ALE = SLE * ARO
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

43. Authentication
Access request by a subject to an object is mediated each time and every time.
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Still under development - aimsto address ISMS implementation guidance
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

44. Information Security Models
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Support policies at a granular and specific level - Can be characterized as internal and external
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

45. Challenges in implementing auditing/logging
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

46. Take-Grant Model
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

47. Security profile of a software
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Support for accreditation and certification bodies that audit and certify ISMS

48. ISO/IEC 27003
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Design to mitigate any single source of complete compromise
Still under development - aimsto address ISMS implementation guidance

49. Single Loss Expectancy (SLE)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Technical - Management - Operational
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

50. 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
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection