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. 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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
The likelihood that a threat can result into an incident. This is the overall risk of a system
Security controls applied to mitigate a threat before it materializes

2. PCI DSS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
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 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

3. Security Policies

4. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

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

6. 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
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
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

7. Properties of secure software
OWASP - ITIL
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Still under development - aimsto address ISMS implementation guidance
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

8. Multifactor authentication
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

9. Information Security Models
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
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

10. ISO/IEC 15408
Security functionality is easy to use and transparent
Provides Common Criteria to evaluate IT security product
Predetermined number of user error allowed before recording it as a security violation
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

11. Error and exception management
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Support for accreditation and certification bodies that audit and certify 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
OWASP - ITIL

12. ISO /IEC 27000:2009
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
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
Development guide - Code Review Guide - Testing Guide
Support for accreditation and certification bodies that audit and certify ISMS

13. Clipping level
Secure applicatios running on secure hosts (systems) in a secure network
Predetermined number of user error allowed before recording it as a security violation
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.
Protection against unauthorized information disclosure. It helps maintaining privacy

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

15. Auditing
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Authentication
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

16. 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
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
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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

17. Configurations Parameters Management
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

18. Popular guides developed by OWASP
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
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
Development guide - Code Review Guide - Testing Guide

19. ISO/IEC 27005:2008
Authentication
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Indicator of magnitude risk in a year ALE = SLE * ARO
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

20. Core Security Concept
Confidentiality - Integrity - Availability
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
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
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

21. ISO/IEC 21827:2008
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Indicator of magnitude risk in a year ALE = SLE * ARO

22. Flaw Hypothesis Method (FHM)
Still under development - aimsto address ISMS implementation guidance
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
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.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

23. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Covers the necessary procedures and tools to validate software assurance
Security controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls

24. NIST standards related to software security
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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

25. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

26. ISO/IEC 27002:2005
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 to mitigate a threat before it materializes
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Design to mitigate any single source of complete compromise

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

28. Phsychological acceptability
Security functionality is easy to use and transparent
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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

29. Operation 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
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

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

31. OWASP Top 10
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Technical - Management - Operational
Secure applicatios running on secure hosts (systems) in a secure network
Periodic publication by OWASP for top 10 Web application security vulnerabilites

32. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Provides Common Criteria to evaluate IT security product
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

33. Benefits of coding standards
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

34. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Development guide - Code Review Guide - Testing Guide
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

35. Single Loss Expectancy (SLE)
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
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

36. Management Controls
Authentication
Secure applicatios running on secure hosts (systems) in a secure network
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

37. Security Standards
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Support policies at a granular and specific level - Can be characterized as internal and external
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

38. STRIDE
Number of incidents that can be expected in a year
Authentication
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

39. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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. Implementation challenges
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

41. Security Risk Management Discipline
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

42. Common best practices significant to Sofware Security
OWASP - ITIL
Predetermined number of user error allowed before recording it as a security violation
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Confidentiality - Integrity - Availability

43. Counter measures
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
Security controls applied after a threat has been materialized
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

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

45. EALs levels
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
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
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

46. Vulnerabilities repositories
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)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Security controls applied after a threat has been materialized

47. Availability
Security controls applied to mitigate a threat before it materializes
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.
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

48. OWASP development guide
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

49. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Security controls applied to mitigate a threat before it materializes
Number of incidents that can be expected in a year

50. After identification step is...
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Authentication
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.