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. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Security controls applied to mitigate a threat before it materializes

2. 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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Protection against unauthorized information disclosure. It helps maintaining privacy
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

3. Risk management process
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Specifies 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
Provides Common Criteria to evaluate IT security product
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

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

5. Access Matrix model

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

6. OWASP development guide
Risk remains after the implementation of mitigating security controls
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Confidentiality - Integrity - Availability
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

7. Authentication
OWASP - ITIL
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

8. Complete mediation
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Access request by a subject to an object is mediated each time and every time.
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

9. ISO/IEC 27006:2007
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
Support for accreditation and certification bodies that audit and certify ISMS

10. Common best practices significant to Sofware Security
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Indicator of magnitude risk in a year ALE = SLE * ARO
OWASP - ITIL
estimate potential loss of a single incident: SLE = Asset value * EF(%)

11. Open design
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
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
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

12. Single point failure
Covers the necessary procedures and tools to validate software assurance
Design to mitigate any single source of complete compromise
Protection against unauthorized information disclosure. It helps maintaining privacy
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

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

14. NIST standards related to software security
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

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

16. Security profile of a software
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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

17. Operation Controls
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Covers the necessary procedures and tools to validate software assurance

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

19. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

20. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
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
Covers the necessary procedures and tools to validate software assurance

22. Compartmentalization
Secure applicatios running on secure hosts (systems) in a secure network
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Security functionality is easy to use and transparent

23. Total Risk
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security controls applied after a threat has been materialized
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
The likelihood that a threat can result into an incident. This is the overall risk of a system

24. 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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

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

26. ISO /IEC 27000:2009
Provides Common Criteria to evaluate IT security product
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Confidentiality - Integrity - Availability
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

27. Core Security Concept
Confidentiality - Integrity - Availability
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Support for accreditation and certification bodies that audit and certify ISMS

28. Examples of Security Standards
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
Predetermined number of user error allowed before recording it as a security violation
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. Software security risk management methodologies
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.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security functionality is easy to use and transparent
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

30. ISO/IEC 15408
Support for accreditation and certification bodies that audit and certify ISMS
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Provides Common Criteria to evaluate IT security product
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

31. Authorization
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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
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

32. Management Controls
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
Development guide - Code Review Guide - Testing Guide
Protection against unauthorized information disclosure. It helps maintaining privacy

33. ISO/IEC 27005:2008
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
Development guide - Code Review Guide - Testing Guide
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

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

35. Implementation challenges
Covers the necessary procedures and tools to validate software assurance
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

36. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

37. Holistic Security in software
Risk remains after the implementation of mitigating security controls
Security functionality is easy to use and transparent
Secure applicatios running on secure hosts (systems) in a secure network
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

38. Session Management
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 policies at a granular and specific level - Can be characterized as internal and external
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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

39. Single Loss Expectancy (SLE)
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Development guide - Code Review Guide - Testing Guide
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

40. Exposure factor (EF)
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

41. EALs levels
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
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
Provides Common Criteria to evaluate IT security product
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

42. ISO/IEC 21827:2008
Protection against unauthorized information disclosure. It helps maintaining privacy
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

43. Annual Rate of Occurence (ARO)
Confidentiality - Integrity - Availability
Covers the necessary procedures and tools to validate software assurance
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Number of incidents that can be expected in a year

44. After identification step is...
Authentication
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

45. FIPS 201
Technical - Management - Operational
Predetermined number of user error allowed before recording it as a security violation
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

46. ISO/IEC 27003
Covers the necessary procedures and tools to validate software assurance
Security controls applied after a threat has been materialized
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
Still under development - aimsto address ISMS implementation guidance

47. OWASP Top 10
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

48. FIPS 197 (Advance Cryptographic standards - AES)
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

49. ISO/IEC 9216
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Still under development - aimsto address ISMS implementation guidance

50. Benefits of coding standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Secure applicatios running on secure hosts (systems) in a secure network
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards