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. Develop hack resilient software
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

2. Vulnerabilities repositories
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 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
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)

3. Categories of controls
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Technical - Management - Operational
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

4. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

5. Technical Controls
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

6. Access Matrix model

7. 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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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.
Indicator of magnitude risk in a year ALE = SLE * ARO

8. 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
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
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
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

9. EALs levels
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
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 to mitigate a threat before it materializes
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

10. Management Controls
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

11. Implementation challenges
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Predetermined number of user error allowed before recording it as a security violation

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

13. Security design principles
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
Support for accreditation and certification bodies that audit and certify ISMS
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
Access request by a subject to an object is mediated each time and every time.

14. Non Repudiation
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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

15. Security Controls
Security controls applied after a threat has been materialized
Protection against unauthorized information disclosure. It helps maintaining privacy
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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

16. Properties of secure software
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

17. Annual Rate of Occurence (ARO)
Number of incidents that can be expected in a year
Risk remains after the implementation of mitigating security controls
Security controls applied after a threat has been materialized
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

18. Integrity
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Predetermined number of user error allowed before recording it as a security violation
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

19. ISO/IEC 21827:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

20. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

21. OWASP Code Review Guide
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Protection against unauthorized information disclosure. It helps maintaining privacy
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

22. Core Security Concept
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Confidentiality - Integrity - Availability

23. Single point failure
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
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
Design to mitigate any single source of complete compromise
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

24. Clipping level
Design to mitigate any single source of complete compromise
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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.

25. Single Loss Expectancy (SLE)
Access request by a subject to an object is mediated each time and every time.
Secure applicatios running on secure hosts (systems) in a secure network
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
estimate potential loss of a single incident: SLE = Asset value * EF(%)

26. General security concept
Security functionality is easy to use and transparent
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

27. Information Security Models
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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 functionality is easy to use and transparent
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

28. Confidentiality
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Protection against unauthorized information disclosure. It helps maintaining privacy

29. Safeguards
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 controls applied to mitigate a threat before it materializes
Risk remains after the implementation of mitigating security controls
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

30. ISO /IEC 27000:2009
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
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
Indicator of magnitude risk in a year ALE = SLE * ARO
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

31. Operation Controls
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Number of incidents that can be expected in a year

32. Challenges in implementing auditing/logging
Indicator of magnitude risk in a year ALE = SLE * ARO
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

33. Accountability
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

34. ISO/IEC 27005:2008
Secure applicatios running on secure hosts (systems) in a secure network
Covers the necessary procedures and tools to validate software assurance
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

35. Residual Risk
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Risk remains after the implementation of mitigating security controls
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

36. Phsychological acceptability
Security functionality is easy to use and transparent
Risk remains after the implementation of mitigating security 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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

37. Holistic Security in software
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Secure applicatios running on secure hosts (systems) in a secure network
Access request by a subject to an object is mediated each time and every time.
Design to mitigate any single source of complete compromise

38. OWASP testing guide
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Covers the necessary procedures and tools to validate software assurance
Design to mitigate any single source of complete compromise
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

39. Authentication
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Predetermined number of user error allowed before recording it as a security violation
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

40. Multifactor authentication
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)
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

41. Popular guides developed by OWASP
Provides Common Criteria to evaluate IT security product
Development guide - Code Review Guide - Testing Guide
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
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

42. Benefits of coding 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
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

43. FIPS 197 (Advance Cryptographic standards - AES)
Support for accreditation and certification bodies that audit and certify ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Technical - Management - Operational

44. ISO/IEC 15408
Provides Common Criteria to evaluate IT security product
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
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.

45. ISO/IEC 27006:2007
Provides Common Criteria to evaluate IT security product
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Support for accreditation and certification bodies that audit and certify ISMS
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

46. ISO/IEC 27001:2005
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

47. ISO/IEC 27003
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
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Still under development - aimsto address ISMS implementation guidance

48. After identification step is...
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Security controls applied to mitigate a threat before it materializes
Authentication
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

49. Security profile of a software
Security controls applied to mitigate a threat before it materializes
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

50. Security Policies