HOPEX Aquila EN

GRC - Governance, Risk & Compliance > HOPEX LDC > Collecting Incidents > Analyzing Incidents > Incident scope

Incident scope

To specify the scope of an incident:

1. See Accessing incidents.

2. In the property page of Incident, select the Characteristics page and expand the Scope section.

Incident scope enables definition of risk location within the organization.

Organization description is detailed in paragraph Organization.

The scope is specified on several component types:

• entities concerned by the incident

An entity can be internal or external to the enterprise: an entity represents an organizational element of enterprise structure such as a management, department, or job function. It is defined at a level depending on the degree of detail to be provided on the organization (see org-unit type). Example: financial management, sales management, marketing department, account manager. An external entity represents an organization that exchanges flows with the enterprise, Example: customer, supplier, government office.

• business lines concerned by the incident

A business line is a skill or grouping of skills of interest for the enterprise. It corresponds for example to major product segments, to distribution channels or to business activities.

• risk typesto be associated with the incident

A risk type defines a risk typology standardized within the context of an organization.

• process categories and processes concerned by the incident

A process category regroups several processes. It serves as a categorization level and provides access to finer grained processes.

A process describes how to implement all or part of the process required to make a product or handle a flow.

• products impacted by the incident

A product represents commodities offered for sale, either goods or merchandise produced as the result of manufacturing, or a service, ie. work done by one person or group that benefits another.

• applications impacted by the incident

An application is a set of software tools coherent from a software development viewpoint.