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. Authentication
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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 calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

2. Complete mediation
Access request by a subject to an object is mediated each time and every time.
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

3. After identification step is...
Authentication
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Support for accreditation and certification bodies that audit and certify ISMS
Design to mitigate any single source of complete compromise

4. Core Security Concept
Confidentiality - Integrity - Availability
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
Protection against unauthorized information disclosure. It helps maintaining privacy
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

5. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
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 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
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

6. Residual Risk
OWASP - ITIL
Risk remains after the implementation of mitigating security controls
Number of incidents that can be expected in a year
estimate potential loss of a single incident: SLE = Asset value * EF(%)

7. Security Policies

8. Multifactor authentication
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
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection

9. Vulnerability
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Provides Common Criteria to evaluate IT security product
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

10. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Provides Common Criteria to evaluate IT security product
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

11. ISO/IEC 27002:2005
Covers the necessary procedures and tools to validate software assurance
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
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

12. ISO/IEC 21827:2008
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 the architecture and technical requirements for a common identified standard for federal employee and contractors
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Risk remains after the implementation of mitigating security controls

13. Security Standards
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
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
Support policies at a granular and specific level - Can be characterized as internal and external
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

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

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

16. Flaw Hypothesis Method (FHM)
Design to mitigate any single source of complete compromise
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
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

17. Phsychological acceptability
Security functionality is easy to use and transparent
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Secure applicatios running on secure hosts (systems) in a secure network
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

18. Single point failure
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
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
Design to mitigate any single source of complete compromise
Indicator of magnitude risk in a year ALE = SLE * ARO

19. Exposure factor (EF)
OWASP - ITIL
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
The likelihood that a threat can result into an incident. This is the overall risk of a system

20. Non Repudiation
Predetermined number of user error allowed before recording it as a security violation
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
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
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

21. Management Controls
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
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
Periodic publication by OWASP for top 10 Web application security vulnerabilites

22. Least common mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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
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

23. Take-Grant Model
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Still under development - aimsto address ISMS implementation guidance

24. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security controls applied to mitigate a threat before it materializes

25. Properties of secure software
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

26. FIPS 197 (Advance Cryptographic standards - AES)
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 an approved cryptographic algorithm to ensure the confidentiality of electronic data
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

27. NIST standards related to software security
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
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Support for accreditation and certification bodies that audit and certify ISMS

28. Holistic Security in software
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Secure applicatios running on secure hosts (systems) in a secure network
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

29. Authorization
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
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
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
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

30. Security design principles
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
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
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

31. Annual Loss Expectancy (ALE)
Indicator of magnitude risk in a year ALE = SLE * ARO
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

32. Safeguards
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
OWASP - ITIL
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Security controls applied to mitigate a threat before it materializes

33. Common best practices significant to Sofware Security
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
OWASP - ITIL
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
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

34. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
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
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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. Total Risk
The likelihood that a threat can result into an incident. This is the overall risk of a system
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

36. Open design
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software
Provides 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
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

37. Benefits of coding standards
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Indicator of magnitude risk in a year ALE = SLE * ARO
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

38. OWASP testing guide
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Covers the necessary procedures and tools to validate software assurance
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

39. Challenges in implementing auditing/logging
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
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

40. EALs levels
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Provides Common Criteria to evaluate IT security product

41. ISO /IEC 27000:2009
Predetermined number of user error allowed before recording it as a security violation
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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. ISO/IEC 27001:2005
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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

43. Confidentiality
Protection against unauthorized information disclosure. It helps maintaining privacy
Secure applicatios running on secure hosts (systems) in a secure network
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
Number of incidents that can be expected in a year

44. ISO/IEC 15408
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Provides Common Criteria to evaluate IT security product
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

45. Risk management process
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Security 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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

46. Examples of Security Standards
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
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

47. DREAD
Technical - Management - Operational
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability
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
The likelihood that a threat can result into an incident. This is the overall risk of a system

48. Technical Controls
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Authentication
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
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.

49. Annual Rate of Occurence (ARO)
Provides Common Criteria to evaluate IT security product
Access request by a subject to an object is mediated each time and every time.
Number of incidents that can be expected in a year
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

50. Session Management
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
Risk remains after the implementation of mitigating security controls
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