Выбрать главу

Incident

(1) An occurrence that actually or potentially jeopardizes the confidentiality, integrity, or availability of an information system or the information the system processes, stores, or transmits or that constitutes a violation or imminent threat of violation of computer security policies, acceptable use policies, or standard security practices.

Incident handling

The mitigation of violations of security policies and recommended practices.

Incident indications

A sign that an incident (e.g., malware) may have occurred or may be currently occurring.

Incident precursors

(1) A sign that a malware attack may occur in the future. (2) A sign that an attacker may be preparing to cause an incident.

Incident response plan

The documentation of a predetermined set of instructions or procedures to detect, respond to, and limit consequences of a malicious cyber attack against an organization’s IT system(s).

Incident-response team

A multidisciplined team consisting of technical, legal, audit, and public affairs specialists to address adverse events.

Incineration

A physically destructive method of sanitizing media; the act of burning completely to ashes.

Incomplete parameter checking

A system design fault that exists when all parameters have not been fully checked for accuracy and consistency by the operating system, thus makes the system vulnerable to penetration.

Incorrect file and directory permissions

File and directory permissions control the access users and processes have to files and directories. Appropriate permissions are critical to the security of any system. Poor permissions could allow any number of attacks, including the reading or writing of password files or the addition of hosts to the list of trusted remote hosts.

Inculpatory evidence

Evidence that tends to increase the likelihood of fault or guilt.

Independent validation and verification

Review, analysis, and testing conducted by an independent party throughout the life cycle of software development to ensure that the new software meets user or contract requirements.

Indication

A sign that an incident (e.g., malware) may have occurred or may be currently occurring.

Individual accountability

The ability to positively associate the identity of a user with the time, method, and degree of system access.

Inference

Derivation of new information from known information. The inference problem refers to the fact that the derived information may be classified at a level for which the user is not cleared. Users may deduce unauthorized information from the legitimate information they acquire. Inference is a problem that derives primarily from poor database design.

Inference attacks

An inference attack occurs when a user or intruder is able to deduce information to which he had no privilege from information to which he has privilege. It is a part of traffic analysis attacks.

Information architecture

The technologies, interfaces, and geographical locations of functions involved with an organization’s information activities.

Information assurance

Measures that protect and defend data/information and information systems by ensuring their availability, integrity, authentication, confidentiality, and nonrepudiation. These measures include providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.

Information density

The total amount and quality of information available to all market participants, consumers, and merchants.

Information economics

Deals with the principle that the costs to obtain information should be equal to or less than the benefits to be derived from the information.

Information engineering

An approach to planning, analyzing, designing, and developing an information system with an enterprise-wide perspective and an emphasis on data and architectures.

Information flow

The sequence, timing, and direction of how information proceeds through an organization.

Information flow control

Access control based on restricting the information flow into an object (e.g., Bell and La Padula model).

Information owner

An official with responsibility for establishing controls for information generation, collection, processing, dissemination, and disposal.

Information portal

A single point of access through a Web browser to business information inside and/or outside an organization.

Information quality

Information quality is composed of three elements such as utility, integrity, and objectivity.

Information resources

Information and related resources, such as personnel, equipment, funds, and information technology.

Information rights

The rights that individuals and organizations have regarding information that pertains to them.

Information security

The protection of information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability.

Information security architecture

An embedded, integral part of the enterprise architecture that describes the structure and behavior for an enterprise’s security processes, information security systems, personnel and organizational subunits, showing their alignment with the enterprise’s mission and strategic plans.

Information security policy

Aggregate of directives, regulations, rules, and practices that prescribe how an organization manages, protects, and distributes information.

Information security program plan

A formal document that provides an overview of the security requirements for an organization-wide information security program and describes the program management controls and common controls in place or planned for meeting those requirements.

Information system (IS)

A discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

Information system owner

An official responsible for the overall procurement, development, integration, modification, or operation and maintenance of an information system.

Information system resilience

The ability of an information system to continue to: (1) operate under adverse conditions or stress, even if in a degraded or debilitated state, while maintaining essential operational capabilities; and (2) recover to an effective operational posture in a time frame consistent with mission needs. It supports agile defense strategy and is the same as resilience.

Information system security officer (ISSO)

Individual assigned responsibility by the senior agency information security officer, authorizing official, management official, or information system owner for ensuring the appropriate operational security posture is maintained for an information system or program.

Information-systems (IS) security

The protection afforded to information systems in order to preserve the availability, integrity, and confidentiality of the systems and information contained within the systems. Such protection is the application of the combination of all security disciplines that will, at a minimum, include communications security, emanation security, emission security, computer security, operational security, information security, personnel security, industrial security, resource protection, and physical security.