DocumentaciónHelp

Incident risks, controls, action plan and finding

Connect the incident to the risk that materialized and the controls that failed, and create from it a new risk, its action plan and its finding.

On this page

An incident isn't isolated: it says which risk materialized, which control failed and what was done so it doesn't happen again. From its details you create the new risk it reveals, the action plan that corrects it and the corresponding finding or nonconformity.

Before you start

  • You need the Administrator or Editor role. With Read only you see these sections, but the buttons are disabled.

  • To mark risks, they must exist in ISMS → Risk matrix. To mark controls, the ISMS must have controls: they appear when you adopt the first standard.

Indicate the risk and the controls

  1. Go to Operations → Incidents and press the incident's pencil (Edit).

  2. In Related risks, choose for each risk:

    • Materialized: the incident is that risk happening.

    • Arises from the incident: a risk the incident brought to light.

  3. In ISMS controls, mark Failed on the control that didn't work and Helped respond on the one that helped contain or recover.

  4. Press Save.

In the details you'll see the risks grouped by their role and the controls in red (failed) or green (helped respond).

Create a new risk

  1. Open the incident's details.

  2. In Risks, press Create risk.

  3. In Create risk from the incident, fill in Risk name (required) and review what is proposed: Description (the incident's), Likelihood (1–5) and Impact (1–5) (they start at 3) and Risk owner (the incident owner).

  4. Press Create risk.

You'll see Risk created from the incident. The risk:

  • is in Identified status, with a sequential code (for example, RSK-0012);

  • appears in the incident as Arises from the incident;

  • inherits the incident's assets, services, processes, suppliers and processing activities;

  • is marked as a privacy risk if the incident is a personal data breach.

Finish its assessment and treatment in ISMS → Risk matrix.

Create the action plan

  1. In Action plans, press Create plan.

  2. In Create action plan, review the Title (it comes as Action plan INC-…: plus the incident title) and fill in Due date (optional), Priority (it comes with the severity) and Owner (it comes with the incident owner).

  3. Press Create plan.

You'll see Action plan PA-… created. The plan:

  • is a corrective action with origin Incident;

  • is linked to the incident, the controls that failed, its risks and its assets;

  • takes the incident's root cause and lessons learned as its description.

You can create more than one plan per incident. Its progress is followed in ISMS → Action plans; in the incident's details you'll see each plan with its progress and status.

Record the finding

If the incident reveals an ISMS nonconformity (for example, a control that should have been operating and wasn't), record it as a finding:

  1. In Findings, press Record finding.

  2. Review the Title (it comes with the incident's code and title) and the Classification: Major nonconformity, Minor nonconformity, Observation, Improvement opportunity or Technical finding. If a control failed, it comes as Minor nonconformity; otherwise, as Improvement opportunity.

  3. Press Record finding.

You'll see Finding HAL-… recorded. The finding has origin Incident and inherits the incident's description, severity, root cause, failed controls and assets. Its treatment (correction, action plan and effectiveness verification) continues in Audit and improvement → Findings and nonconformities: see Findings and nonconformities.

You can also ask the SofIA assistant to create the action plan or record the finding of an incident. It will show you what it is going to create and will only do it when you confirm with its button. See Authorize actions.

Related

Search SofIA Governance

Type at least 2 characters to search SofIA Governance.

↑↓ to navigate · Enter to open · Esc to close