A.   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

C.   Risk remains after the implementation of mitigating security controls

D.   Successful completion of a critical task is dependent on 2 or more conditions that need to be met

A.   Authentication

B.   Microsoft SRMD (Security Risk Management Discipline) - Vulnerability oriented risk management - Charles Le Grand - Morana Risk Management Activities - Cigital Risk Management Methods

D.   Design to mitigate any single source of complete compromise

A.   Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

B.   Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

C.   Secure applicatios running on secure hosts (systems) in a secure network

A.   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

B.   Support policies at a granular and specific level - Can be characterized as internal and external

D.   Support for accreditation and certification bodies that audit and certify ISMS

A.   Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject

C.   OWASP - ITIL

D.   Indicator of magnitude risk in a year ALE = SLE * ARO

A.   Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

C.   Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

D.   Secure applicatios running on secure hosts (systems) in a secure network

B.   Still under development - aimsto address ISMS implementation guidance

C.   A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

D.   Successful completion of a critical task is dependent on 2 or more conditions that need to be met

B.   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

C.   Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

D.   Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

A.   Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

C.   Design to mitigate any single source of complete compromise

D.   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

B.   Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

C.   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

D.   Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management

A.   Risk remains after the implementation of mitigating security controls

B.   Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

D.   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

A.   Support for accreditation and certification bodies that audit and certify ISMS

B.   Design to mitigate any single source of complete compromise

C.   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

B.   Security controls applied to mitigate a threat before it materializes

C.   Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

D.   Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

B.   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

C.   The likelihood that a threat can result into an incident. This is the overall risk of a system

D.   Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

A.   The likelihood that a threat can result into an incident. This is the overall risk of a system

B.   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

C.   Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

A.   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

C.   Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS

D.   Provides Common Criteria to evaluate IT security product

B.   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

C.   Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)

D.   Secure applicatios running on secure hosts (systems) in a secure network

A.   Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

C.   Specifies an approved cryptographic algorithm to ensure the confidentiality of electronic data

D.   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.

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

C.   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

D.   Security controls applied after a threat has been materialized

B.   Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run

C.   Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability

D.   Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

A.   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

B.   Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

D.   Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:

A.   Provides Common Criteria to evaluate IT security product

B.   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

D.   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.

A.   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

B.   Still under development - aimsto address ISMS implementation guidance

D.   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

A.   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

C.   Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege

D.   Support policies at a granular and specific level - Can be characterized as internal and external

A.   SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer

B.   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

D.   Periodic publication by OWASP for top 10 Web application security vulnerabilites

A.   27. DREAD

B.   Development guide - Code Review Guide - Testing Guide

D.   Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

E.   Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

B.   Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA

C.   Support policies at a granular and specific level - Can be characterized as internal and external

D.   A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

A.   Technical - Management - Operational

B.   Security controls applied to mitigate a threat before it materializes

D.   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

A.   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.

B.   Provides Common Criteria to evaluate IT security product

D.   Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

A.   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

C.   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

D.   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