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. Annual Rate of Occurence (ARO)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

2. Management Controls
Technical - Management - Operational
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

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

4. Error and exception management
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
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

5. Technical Controls
Covers the necessary procedures and tools to validate software assurance
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

6. Core Security Concept
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Support policies at a granular and specific level - Can be characterized as internal and external
Confidentiality - Integrity - Availability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

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

8. Categories of controls
Security controls applied to mitigate a threat before it materializes
Covers the necessary procedures and tools to validate software assurance
Technical - Management - Operational
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

9. NIST standards related to software security
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

10. 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
Support policies at a granular and specific level - Can be characterized as internal and external
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
estimate potential loss of a single incident: SLE = Asset value * EF(%)

11. Authentication
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

12. DREAD
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

13. 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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

14. Challenges in implementing auditing/logging
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

15. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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.
Still under development - aimsto address ISMS implementation guidance
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

16. ISO/IEC 27006:2007
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
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 for accreditation and certification bodies that audit and certify ISMS
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

17. Security Policies

18. Auditing
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

19. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

20. Accountability
Risk remains after the implementation of mitigating security controls
Confidentiality - Integrity - Availability
Technical - Management - Operational
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

21. Access Matrix model

22. ISO/IEC 27001:2005
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

23. Annual Loss Expectancy (ALE)
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Indicator of magnitude risk in a year ALE = SLE * ARO

24. Exposure factor (EF)
Security controls applied to mitigate a threat before it materializes
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

25. Single Loss Expectancy (SLE)
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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 unauthorized information disclosure. It helps maintaining privacy

26. Single point failure
Support for accreditation and certification bodies that audit and certify ISMS
Design to mitigate any single source of complete compromise
Technical - Management - Operational
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

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

28. Safeguards
Security controls applied to mitigate a threat before it materializes
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
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

29. FIPS140-2 (Security requirement for cryptographic modules)
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

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

31. Non Repudiation
Secure applicatios running on secure hosts (systems) in a secure network
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

32. Clipping level
Authentication
Predetermined number of user error allowed before recording it as a security violation
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

33. Common best practices significant to Sofware Security
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.
OWASP - ITIL
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

34. Economy of mechanism
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

35. STRIDE
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

36. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
OWASP - ITIL
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

37. Compartmentalization
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
Predetermined number of user error allowed before recording it as a security violation
Risk remains after the implementation of mitigating security controls

38. ISO/IEC 15408
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Provides Common Criteria to evaluate IT security product

39. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Protection against unauthorized information disclosure. It helps maintaining privacy

40. EALs levels
Support for accreditation and certification bodies that audit and certify 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
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software

41. Flaw Hypothesis Method (FHM)
Support for accreditation and certification bodies that audit and certify ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Covers the necessary procedures and tools to validate software assurance
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

42. PCI DSS
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a 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
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
Covers the necessary procedures and tools to validate software assurance

43. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

44. Security Controls
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
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

45. OWASP Top 10
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
Security controls applied after a threat has been materialized
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Periodic publication by OWASP for top 10 Web application security vulnerabilites

46. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Number of incidents that can be expected in a year

47. Information Security Models
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
Covers the necessary procedures and tools to validate software assurance
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

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

49. Session Management
Still under development - aimsto address ISMS implementation guidance
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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

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