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. Least privilege
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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 functionality is easy to use and transparent
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.

2. Vulnerability
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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

3. After identification step is...
Security functionality is easy to use and transparent
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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

4. Information Security Models
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:
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
Predetermined number of user error allowed before recording it as a security violation

5. Security Controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Risk remains after the implementation of mitigating security controls
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

6. Session Management
Authentication
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
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

7. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

8. Operation 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
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: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Number of incidents that can be expected in a year

9. Security Policies

10. Challenges in implementing auditing/logging
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Confidentiality - Integrity - Availability
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans

11. Clipping level
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Predetermined number of user error allowed before recording it as a security violation

12. ISO/IEC 27001:2005
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Protection against unauthorized information disclosure. It helps maintaining privacy
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

13. ISO/IEC 27005:2008
Provides Common Criteria to evaluate IT security product
Secure applicatios running on secure hosts (systems) in a secure network
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

14. ISO/IEC 15408
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Provides Common Criteria to evaluate IT security product
Authentication

15. Categories of controls
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Provides Common Criteria to evaluate IT security product
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
Technical - Management - Operational

16. Safeguards
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Security controls applied to mitigate a threat before it materializes
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

17. Core Security Concept
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.
Confidentiality - Integrity - Availability
Security functionality is easy to use and transparent
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

18. Properties of secure software
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

19. Error and exception management
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
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 controls applied after a threat has been materialized

20. Accountability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Technical - Management - Operational

21. Benefits of coding standards
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
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security controls applied after a threat has been materialized

22. Configurations Parameters Management
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Access request by a subject to an object is mediated each time and every time.
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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

23. STRIDE
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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering 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

24. ISO/IEC 21827:2008
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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. 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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC

26. NIST standards related to software security
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

27. Examples of Security Standards
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
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
Confidentiality - Integrity - Availability

28. Popular guides developed by OWASP
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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

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

30. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Support for accreditation and certification bodies that audit and certify ISMS

31. Risk management process
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

32. Common best practices significant to Sofware Security
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
OWASP - ITIL

33. Complete mediation
Covers the necessary procedures and tools to validate software assurance
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Access request by a subject to an object is mediated each time and every time.

34. Phsychological acceptability
Design to mitigate any single source of complete compromise
Security functionality is easy to use and transparent
Number of incidents that can be expected in a year
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

35. Management Controls
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

36. PCI DSS
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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

37. 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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

38. Compartmentalization
Technical - Management - Operational
Number of incidents that can be expected in a year
Confidentiality - Integrity - Availability
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

39. Exposure factor (EF)
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Predetermined number of user error allowed before recording it as a security violation
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

40. Authentication
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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

41. General security concept
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Design to mitigate any single source of complete compromise

42. Security profile of a software
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
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Security controls applied after a threat has been materialized

43. Annual Loss Expectancy (ALE)
Security controls applied to mitigate a threat before it materializes
Indicator of magnitude risk in a year ALE = SLE * ARO
Technical - Management - Operational
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

44. Vulnerabilities repositories
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)
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)

45. ISO/IEC 27003
Development guide - Code Review Guide - Testing Guide
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
Risk remains after the implementation of mitigating security controls
Still under development - aimsto address ISMS implementation guidance

46. OWASP testing guide
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Covers the necessary procedures and tools to validate software assurance
Secure applicatios running on secure hosts (systems) in a secure network

47. FIPS 197 (Advance Cryptographic standards - AES)
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Support for accreditation and certification bodies that audit and certify ISMS
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

48. ISO/IEC 27002:2005
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

49. Multifactor authentication
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
Authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

50. Economy of mechanism
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code