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. Examples of Security Standards
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Design to mitigate any single source of complete compromise

2. Accountability
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

3. Error and exception management
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

4. Exposure factor (EF)
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.
Development guide - Code Review Guide - Testing Guide
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

5. Challenges in implementing auditing/logging
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Indicator of magnitude risk in a year ALE = SLE * ARO

6. Vulnerability
Technical - Management - Operational
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
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
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. 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
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
Security controls applied to mitigate a threat before it materializes

8. Security Risk Management Discipline
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

9. Popular guides developed by OWASP
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
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
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

10. Risk management process
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
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

11. ISO/IEC 27005:2008
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
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

12. Non Repudiation
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery 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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

13. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Support policies at a granular and specific level - Can be characterized as internal and external
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

14. Take-Grant 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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

15. Security Policies

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

16. Implementation challenges
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
OWASP - ITIL
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

17. Safeguards
Development guide - Code Review Guide - Testing Guide
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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
Security controls applied to mitigate a threat before it materializes

18. 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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

19. Total Risk
Security controls applied to mitigate a threat before it materializes
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
The likelihood that a threat can result into an incident. This is the overall risk of a system

20. ISO/IEC 15408
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
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

21. Develop hack resilient software
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
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

22. Authentication
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
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors

23. Annual Rate of Occurence (ARO)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Number of incidents that can be expected in a year
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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. Authorization
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

25. Holistic Security in software
OWASP - ITIL
Number of incidents that can be expected in a year
Support policies at a granular and specific level - Can be characterized as internal and external
Secure applicatios running on secure hosts (systems) in a secure network

26. Multifactor authentication
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

27. Counter measures
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
Access request by a subject to an object is mediated each time and every time.
Security controls applied after a threat has been materialized
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

28. Properties of secure 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Indicator of magnitude risk in a year ALE = SLE * ARO
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

29. Availability
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.
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 the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

30. OCTAVE
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.
Support for accreditation and certification bodies that audit and certify ISMS
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

31. OWASP testing guide
Covers the necessary procedures and tools to validate software assurance
Security controls applied after a threat has been materialized
Still under development - aimsto address ISMS implementation guidance
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

32. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c

33. After identification step is...
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
Authentication
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

34. Management Controls
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Security functionality is easy to use and transparent
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

35. FIPS140-2 (Security requirement for cryptographic modules)
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Security functionality is easy to use and transparent
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

36. Security Controls
Security controls applied after a threat has been materialized
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
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system

37. Categories of controls
Technical - Management - Operational
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
The likelihood that a threat can result into an incident. This is the overall risk of a system

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

39. 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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

40. OWASP Top 10
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Predetermined number of user error allowed before recording it as a security violation

41. ISO/IEC 27001:2005
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 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 requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

42. Compartmentalization
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Still under development - aimsto address ISMS implementation guidance
Security controls applied to mitigate a threat before it materializes

43. Common best practices significant to Sofware Security
Design to mitigate any single source of complete compromise
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
OWASP - ITIL

44. Single point failure
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
Design to mitigate any single source of complete compromise
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

45. OWASP Code Review Guide
Risk remains after the implementation of mitigating security controls
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Secure applicatios running on secure hosts (systems) in a secure network
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

46. ISO /IEC 27000:2009
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
Indicator of magnitude risk in a year ALE = SLE * ARO
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
Still under development - aimsto address ISMS implementation guidance

47. Phsychological acceptability
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Security functionality is easy to use and transparent

48. Flaw Hypothesis Method (FHM)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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
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

49. 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
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

50. Residual Risk
Access request by a subject to an object is mediated each time and every time.
Secure applicatios running on secure hosts (systems) in a secure network
Risk remains after the implementation of mitigating security controls
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

Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?

Major Subjects
Tests & Exams AP CLEP DSST GRE SAT GMAT	Certifications CISSP go to https://www.isc2.org/ PMP ITIL RHCE MCTS More...	IT Skills Android Programming Data Modeling Objective C Programming Basic Python Programming Adobe Illustrator More...	Business Skills Advertising Techniques Business Accounting Basics Business Strategy Human Resource Management Marketing Basics More...
Soft Skills Body Language People Skills Public Speaking Persuasion Job Hunting And Resumes More...	Vocabulary GRE Vocab SAT Vocab TOEFL Essential Vocab Basic English Words For All Global Words You Should Know Business English More...	Languages AP German Vocab AP Latin Vocab SAT Subject Test: French Italian Survival Norwegian Survival More...	Engineering Audio Engineering Computer Science Engineering Aerospace Engineering Chemical Engineering Structural Engineering More...
Health Sciences Basic Nursing Skills Health Science Language Fundamentals Veterinary Technology Medical Language Cardiology Clinical Surgery More...	English Grammar Fundamentals Literary And Rhetorical Vocab Elements Of Style Vocab Introduction To English Major Complete Advanced Sentences Literature Homonyms More...	Math Algebra Formulas Basic Arithmetic: Measurements Metric Conversions Geometric Properties Important Math Facts Number Sense Vocab Business Math More...	Other Major Subjects Science Economics History Law Performing-arts Cooking Logic & Reasoning Trivia

Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?

Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests

Major Subjects

Tests & Exams

Certifications

IT Skills

Business Skills

Soft Skills

Vocabulary

Languages

Engineering

Health Sciences

English

Math

Other Major Subjects

Browse all subjects

Browse all tests

Most popular tests