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. Compartmentalization
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Indicator of magnitude risk in a year ALE = SLE * ARO

2. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Secure applicatios running on secure hosts (systems) in a secure network
Support policies at a granular and specific level - Can be characterized as internal and external
Confidentiality - Integrity - Availability

3. 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
Protection against unauthorized information disclosure. It helps maintaining privacy
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
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

4. Management Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

5. 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
Support for accreditation and certification bodies that audit and certify ISMS
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

6. Security 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
Indicator of magnitude risk in a year ALE = SLE * ARO
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c

7. Benefits of coding standards
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

8. After identification step is...
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
Authentication
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
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

9. Security Risk Management Discipline
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
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Confidentiality - Integrity - Availability
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

10. ISO /IEC 27000:2009
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
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
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
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

11. Economy of mechanism
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
OWASP - ITIL
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

12. 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
Predetermined number of user error allowed before recording it as a security violation
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Design to mitigate any single source of complete compromise

13. FIPS140-2 (Security requirement for cryptographic modules)
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

14. Confidentiality
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Design to mitigate any single source of complete compromise
Protection against unauthorized information disclosure. It helps maintaining privacy
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

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

16. ISO/IEC 21827:2008
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Confidentiality - Integrity - Availability

17. FIPS 197 (Advance Cryptographic standards - AES)
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

18. Core Security Concept
Confidentiality - Integrity - Availability
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them

19. Multifactor authentication
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
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

20. ISO/IEC 27002:2005
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
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
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

21. Vulnerabilities repositories
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
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Periodic publication by OWASP for top 10 Web application security vulnerabilites

22. Single point failure
Design to mitigate any single source of complete compromise
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.
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
Technical - Management - Operational

23. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Access request by a subject to an object is mediated each time and every time.

24. OWASP testing guide
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
The likelihood that a threat can result into an incident. This is the overall risk of a system
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code

25. General security concept
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
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
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

26. Vulnerability
Still under development - aimsto address ISMS implementation guidance
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
Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

27. Threat
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Periodic publication by OWASP for top 10 Web application security vulnerabilites
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

28. ISO/IEC 15408
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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
Provides Common Criteria to evaluate IT security product
Risk remains after the implementation of mitigating security controls

29. Residual Risk
Risk remains after the implementation of mitigating security controls
Support policies at a granular and specific level - Can be characterized as internal and external
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
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

30. 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
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing 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

31. Annual Rate of Occurence (ARO)
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
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Number of incidents that can be expected in a year
Successful completion of a critical task is dependent on 2 or more conditions that need to be met

32. Authentication
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
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment
Access request by a subject to an object is mediated each time and every time.

33. OCTAVE
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Provides Common Criteria to evaluate IT security product
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
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards

34. Risk management process
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
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
OWASP - ITIL
Access request by a subject to an object is mediated each time and every time.

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

36. ISO/IEC 27003
Still under development - aimsto address ISMS implementation guidance
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
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
Confidentiality - Integrity - Availability

37. DREAD
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Secure applicatios running on secure hosts (systems) in a secure network
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
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

38. ISO/IEC 27005:2008
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data
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

39. Open design
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Preventive Controls: control of media access and disposal - securing wiring closets etx. - Detection Controls: cameras and motion detectors
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
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

40. FIPS 201
Support policies at a granular and specific level - Can be characterized as internal and external
Number of incidents that can be expected in a year
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Predetermined number of user error allowed before recording it as a security violation

41. Technical Controls
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Support for accreditation and certification bodies that audit and certify ISMS
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

42. Access Matrix model

43. Safeguards
Security controls applied to mitigate a threat before it materializes
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
Authentication
Protection against unauthorized information disclosure. It helps maintaining privacy

44. Error and exception management
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Security controls applied after a threat has been materialized
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
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

45. Complete mediation
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
Still under development - aimsto address ISMS implementation guidance
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
Access request by a subject to an object is mediated each time and every time.

46. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

47. Least common mechanism
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Support policies at a granular and specific level - Can be characterized as internal and external

48. Phsychological acceptability
Security functionality is easy to use and transparent
Support for accreditation and certification bodies that audit and certify ISMS
Provides Common Criteria to evaluate IT security product
Technical - Management - Operational

49. Security Standards
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Support policies at a granular and specific level - Can be characterized as internal and external
Support for accreditation and certification bodies that audit and certify ISMS
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

50. OWASP development guide
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges