Platform

What is a risk treatment plan in GRC?

Direct answer

A risk treatment plan documents how an organisation addresses identified risks. Four standard options exist: mitigate (implement controls to reduce likelihood or impact), accept (acknowledge the risk with formal sign-off), transfer (shift risk to a third party via insurance or outsourcing), and avoid (eliminate the activity that creates the risk).

In Acuna GRC, the strategy is set on the risk with target values after treatment, and a treatment plan with an owner and a status links the controls, measures, tasks, documents and records that carry it out. The plan's health is computed from those links and rolls up into the risk, and the risk matrix switches between actual and target positions, giving auditors a before-and-after view.

What does ISO 27001 require for risk treatment?

In ISO/IEC 27001:2022, risk treatment is clause 6.1.3, and it runs in a fixed sequence:

  • Choose a treatment option for each risk found in the risk assessment.
  • Determine all the controls needed to carry out that treatment, from any source.
  • Compare them with Annex A to check that no necessary control has been left out.
  • Produce the Statement of Applicability (clause 6.1.3 d).
  • Formulate the risk treatment plan (clause 6.1.3 e).
  • Obtain the risk owners’ approval of the plan and their acceptance of the residual risks (clause 6.1.3 f).

Clause 8.3 then requires you to implement the plan and retain documented information on the results of risk treatment. The plan is therefore both a planning document and the thread auditors follow to the evidence that it was carried out. See which documents ISO 27001 requires.

What goes into a good risk treatment plan?

For each risk, or group of related risks, a plan usually records:

  • The risk it addresses and the treatment option chosen.
  • The controls and measures to put in place or strengthen, and the tasks that carry them out.
  • An owner for the plan, and owners and due dates for each action.
  • The target level of risk after treatment, so you can tell when the plan has worked.
  • The risk owner’s approval and acceptance of the residual risk.
  • Its status, and the records that prove each action was done.

Accepting a risk is a treatment decision too. It still needs a named owner and a formal sign-off, and it should come back for review rather than stay accepted indefinitely.

What mistakes do auditors find in risk treatment plans?

  • Plans that list controls but no owners or dates, so nothing shows whether they were ever implemented.
  • Residual risk never stated, or accepted by someone who is not the risk owner.
  • A Statement of Applicability that does not match the controls named in the plans.
  • Risks marked “Mitigate” with no plan or control behind them.
  • Plans closed as complete with no record that the controls actually run.
  • Accepted risks that are never reviewed again.

How are treatment plans run in Acuna GRC?

In Acuna GRC, treatment plans sit in the Operate workspace next to the risk register. You set the strategy (Mitigate, Accept, Transfer or Avoid) and the target impact and likelihood on the risk, then create a treatment plan with an owner and a status, linked to the risks it addresses and to the controls, measures, tasks, documents and records that carry it out. Plan health is computed from the linked controls, measures and tasks and rolls up into the risk, so a missed task shows on the risk it was meant to reduce.

Risks move through an approval workflow; only the owner or an administrator can approve, and approval sets a review date one year ahead, with reminders 30 days and 3 days before and once if overdue. The matrix switches between actual and target positions. See how enterprise risk management works in Acuna GRC.

How Acuna GRC handles it

Sources

  1. ISO/IEC 27001:2022, clauses 6.1.3 and 8.3

This page explains the rules in general terms and is not legal advice.

Frequently asked

Is the risk treatment plan the same as the Statement of Applicability?

No. The Statement of Applicability records which controls apply and why. The risk treatment plan, required by clause 6.1.3 e, sets out how the risks will be treated. ISO 27001 requires both, and they should agree.

Who approves a risk treatment plan?

Under ISO 27001 clause 6.1.3 f, the risk owners approve the plan and accept the residual risks. Approval by the security team alone does not meet that requirement.

Does accepting a risk need a treatment plan?

Acceptance is a treatment option, so it should be recorded with a justification, the residual level and the risk owner’s sign-off, and reviewed periodically.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US