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. Software security risk management methodologies
Security controls applied to mitigate a threat before it materializes
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

2. Technical Controls
Number of incidents that can be expected in a year
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
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.

3. Benefits of coding standards
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
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
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

4. Counter measures
Covers the necessary procedures and tools to validate software assurance
Security controls applied after a threat has been materialized
OWASP - ITIL
Confidentiality - Integrity - Availability

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

6. Total Risk
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

7. 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
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
Technical - Management - Operational
Indicator of magnitude risk in a year ALE = SLE * ARO

8. ISO/IEC 27001:2005
Protection against unauthorized information disclosure. It helps maintaining privacy
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

9. DREAD
Support policies at a granular and specific level - Can be characterized as internal and external
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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

10. Implementation challenges
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Protection against unauthorized information disclosure. It helps maintaining privacy

11. 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
Technical - Management - Operational
Design to mitigate any single source of complete compromise
Security functionality is easy to use and transparent

12. Integrity
Support policies at a granular and specific level - Can be characterized as internal and external
Security controls applied to mitigate a threat before it materializes
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

13. Open design
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
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
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software

14. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

15. Economy of mechanism
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
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

16. ISO/IEC 27006:2007
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Support for accreditation and certification bodies that audit and certify ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

17. NIST standards related to software security
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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 the architecture and technical requirements for a common identified standard for federal employee and contractors
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

18. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Security controls applied after a threat has been materialized
The likelihood that a threat can result into an incident. This is the overall risk of a system
Security controls applied to mitigate a threat before it materializes

19. FIPS 197 (Advance Cryptographic standards - AES)
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
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

20. Auditing
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
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
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

21. Examples of Security Standards
Still under development - aimsto address ISMS implementation guidance
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

22. Properties of secure software
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
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
Risk remains after the implementation of mitigating security controls
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

23. ISO/IEC 15408
Access request by a subject to an object is mediated each time and every time.
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Provides Common Criteria to evaluate IT security product

24. ISO/IEC 9216
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Secure applicatios running on secure hosts (systems) in a secure network
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Protection against unauthorized information disclosure. It helps maintaining privacy

25. Authorization
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
Secure applicatios running on secure hosts (systems) in a secure network

26. Threat
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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

27. Vulnerabilities repositories
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Support for accreditation and certification bodies that audit and certify ISMS
Authentication
Predetermined number of user error allowed before recording it as a security violation

28. Clipping level
Support for accreditation and certification bodies that audit and certify ISMS
Predetermined number of user error allowed before recording it as a security violation
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

29. Non Repudiation
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
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

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

31. Core Security Concept
Confidentiality - Integrity - Availability
Security controls applied after a threat has been materialized
Support policies at a granular and specific level - Can be characterized as internal and external
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

32. Compartmentalization
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

33. Vulnerability
Protection against unauthorized information disclosure. It helps maintaining privacy
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
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

34. Multifactor 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
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Risk remains after the implementation of mitigating security controls

35. Operation Controls
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Security controls applied to mitigate a threat before it materializes
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors

36. Least common mechanism
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
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Provides Common Criteria to evaluate IT security product
OWASP - ITIL

37. Safeguards
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
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
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

38. 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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
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
Predetermined number of user error allowed before recording it as a security violation

39. Security Policies

40. OWASP development guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

41. ISO /IEC 27000:2009
Security controls applied after a threat has been materialized
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
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
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

42. 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
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Secure applicatios running on secure hosts (systems) in a secure network
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

43. Common best practices significant to Sofware Security
OWASP - ITIL
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
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Still under development - aimsto address ISMS implementation guidance

44. Annual Loss Expectancy (ALE)
Covers the necessary procedures and tools to validate software assurance
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Indicator of magnitude risk in a year ALE = SLE * ARO
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

45. Exposure factor (EF)
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

46. Configurations Parameters Management
Security functionality is easy to use and transparent
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Technical - Management - Operational

47. 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
Covers the necessary procedures and tools to validate software assurance
Technical - Management - Operational
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

48. Information Security Models
Security controls applied after a threat has been materialized
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
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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

49. Availability
Indicator of magnitude risk in a year ALE = SLE * ARO
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.
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
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

50. OCTAVE
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 Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans
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

Sorry, Topic not found.:)

Seach or Brouse Basicversity:

Major Subjects
Tests & Exams AP CLEP DSST GRE SAT GMAT	Certifications CISSP go 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

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