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. Core Security Concept
Access request by a subject to an object is mediated each time and every time.
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
Confidentiality - Integrity - Availability
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

2. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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 to mitigate a threat before it materializes
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

3. OCTAVE
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Technical - Management - Operational
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

4. ISO/IEC 27002:2005
Secure applicatios running on secure hosts (systems) in a secure network
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Confidentiality - Integrity - Availability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

5. Confidentiality
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Provides Common Criteria to evaluate IT security product

6. Challenges in implementing auditing/logging
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
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
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

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

8. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

9. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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
Provides Common Criteria to evaluate IT security product

10. Technical Controls
Support for accreditation and certification bodies that audit and certify ISMS
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 weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

11. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Covers the necessary procedures and tools to validate software assurance

12. Total Risk
Support for accreditation and certification bodies that audit and certify ISMS
Technical - Management - Operational
OWASP - ITIL
The likelihood that a threat can result into an incident. This is the overall risk of a system

13. Safeguards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Risk remains after the implementation of mitigating security controls
Development guide - Code Review Guide - Testing Guide
Security controls applied to mitigate a threat before it materializes

14. 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 policies at a granular and specific level - Can be characterized as internal and external
Predetermined number of user error allowed before recording it as a security violation
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. Benefits of coding standards
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

16. Counter measures
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Security controls applied after a threat has been materialized
Provides Common Criteria to evaluate IT security product
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

17. ISO/IEC 27001:2005
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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. Residual Risk
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Risk remains after the implementation of mitigating security controls

19. NIST standards related to software security
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
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
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

20. Security Policies

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

21. Software security risk management methodologies
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Indicator of magnitude risk in a year ALE = SLE * ARO

22. Risk management process
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Still under development - aimsto address ISMS implementation guidance
Technical - Management - Operational
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

23. Properties of secure software
Number of incidents that can be expected in a year
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

24. Vulnerability
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
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
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
Authentication

25. Error and exception management
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

26. Security profile of a software
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
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

27. Information Security Models
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
Authentication
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

28. Multifactor authentication
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Number of incidents that can be expected in a year
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Confidentiality - Integrity - Availability

29. Economy of mechanism
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

30. Single point failure
Design to mitigate any single source of complete compromise
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

31. After identification step is...
Predetermined number of user error allowed before recording it as a security violation
Authentication
The likelihood that a threat can result into an incident. This is the overall risk of a system
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

32. ISO/IEC 21827:2008
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
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

33. Availability
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

34. Clipping level
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Predetermined number of user error allowed before recording it as a security violation
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

35. Configurations Parameters Management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
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

36. Annual Rate of Occurence (ARO)
Confidentiality - Integrity - Availability
Number of incidents that can be expected in a year
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

37. Non Repudiation
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
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
Risk remains after the implementation of mitigating security controls
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

38. ISO/IEC 27005:2008
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
Security controls applied to mitigate a threat before it materializes
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

39. Open design
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

40. Least privilege
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Technical - Management - Operational
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

41. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

42. ISO/IEC 27003
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
Still under development - aimsto address ISMS implementation guidance
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

43. Authentication
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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 concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied

44. STRIDE
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
Development guide - Code Review Guide - Testing Guide
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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

45. EALs levels
Still under development - aimsto address ISMS implementation guidance
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

46. FIPS 197 (Advance Cryptographic standards - AES)
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Design to mitigate any single source of complete compromise
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

47. Categories of controls
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Technical - Management - Operational
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

48. Develop hack resilient software
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 Common Criteria to evaluate IT security product
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

49. Security Risk Management Discipline
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
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
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

50. Exposure factor (EF)
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.
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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