SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
CSSLP: Certified Secure Software Lifecycle Professional
Start Test
Study First
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. Availability
Covers the necessary procedures and tools to validate software assurance
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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.
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
2. FIPS 201
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
3. Session Management
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Development guide - Code Review Guide - Testing Guide
4. Multifactor authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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
5. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
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
6. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Security controls applied to mitigate a threat before it materializes
7. Economy of mechanism
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
8. Least privilege
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.
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
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
9. After identification step is...
Authentication
Protection against unauthorized information disclosure. It helps maintaining privacy
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Secure applicatios running on secure hosts (systems) in a secure network
10. Security Standards
Support policies at a granular and specific level - Can be characterized as internal and external
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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
11. Operation Controls
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Predetermined number of user error allowed before recording it as a security violation
12. Phsychological acceptability
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
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
Security functionality is easy to use and transparent
13. Develop hack resilient software
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
14. ISO /IEC 27000:2009
Support policies at a granular and specific level - Can be characterized as internal and external
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
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
15. Total Risk
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
The likelihood that a threat can result into an incident. This is the overall risk of a system
16. Categories of controls
Technical - Management - Operational
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
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
17. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
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
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
18. Annual Loss Expectancy (ALE)
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Secure applicatios running on secure hosts (systems) in a secure network
19. Security profile of a software
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
Security controls applied to mitigate a threat before it materializes
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
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
20. Challenges in implementing auditing/logging
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Secure applicatios running on secure hosts (systems) in a secure network
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
21. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Protection against unauthorized information disclosure. It helps maintaining privacy
Support for accreditation and certification bodies that audit and certify ISMS
22. Risk management process
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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. Vulnerability
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
24. 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
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
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
Indicator of magnitude risk in a year ALE = SLE * ARO
25. DREAD
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
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
26. Threat
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
27. Clipping level
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
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
Predetermined number of user error allowed before recording it as a security violation
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
28. OWASP Top 10
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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
29. Single point failure
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Design to mitigate any single source of complete compromise
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
30. General security concept
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Number of incidents that can be expected in a year
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
31. Take-Grant Model
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
32. ISO/IEC 15408
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Provides Common Criteria to evaluate IT security product
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
33. Annual Rate of Occurence (ARO)
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Number of incidents that can be expected in a year
34. OWASP Code Review Guide
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
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
35. Safeguards
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
Security controls applied to mitigate a threat before it materializes
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
36. Properties of secure software
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Technical - Management - Operational
Security controls applied after a threat has been materialized
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
37. Holistic Security in software
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Secure applicatios running on secure hosts (systems) in a secure network
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
38. 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
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Support for accreditation and certification bodies that audit and certify ISMS
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
39. OWASP development guide
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the 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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
40. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Development guide - Code Review Guide - Testing Guide
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
41. 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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
42. Security design principles
estimate potential loss of a single incident: SLE = Asset value * EF(%)
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 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
43. Security Controls
Security controls applied after a threat has been materialized
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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
Covers the necessary procedures and tools to validate software assurance
44. Error and exception management
Covers the necessary procedures and tools to validate software assurance
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
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
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
45. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Access request by a subject to an object is mediated each time and every time.
46. ISO/IEC 27003
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
Still under development - aimsto address ISMS implementation guidance
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
Indicator of magnitude risk in a year ALE = SLE * ARO
47. FIPS140-2 (Security requirement for cryptographic modules)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Confidentiality - Integrity - Availability
48. Counter measures
Security controls applied after a threat has been materialized
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.
Development guide - Code Review Guide - Testing Guide
49. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
50. ISO/IEC 27006:2007
Support for accreditation and certification bodies that audit and certify ISMS
Number of incidents that can be expected in a year
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 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