Clause 8 – Operation

Clause 8.3 Information security risk treatment (operation)

Mandatory requirement Documented information required

What it means in plain language

Implement the risk treatment plan and keep records of the results – are the actions done and is the residual risk now acceptable?

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • Results of the information security risk treatment.

Why this requirement matters

The operational priority is execution, not planning: the treatment plan must move from assigned actions to completed actions with evidence that residual risk has been re-evaluated. In practice, accountable owners, target dates, and acceptance decisions are tracked through the register and escalated when slippage affects risk. Another frequent weakness is closing actions administratively without confirming that the control was actually deployed and that the remaining risk is still within the organisation’s criteria.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Treatment actions are marked complete, but the supporting control evidence is absent, so the organisation cannot show that the risk response was implemented.
  • Residual risk is not recalculated after controls change, leaving outdated acceptance statements that no longer reflect the current exposure.
  • Overdue actions remain open without escalation records, making it unclear whether management was informed about risks that exceeded target dates.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Assign each treatment action to a named owner with due date, dependency, and completion evidence field in the Risk Register & Treatment Plan. The risk owner should verify the action is operational, not just planned, before the status is changed to done.
  • Once a control is in place, reassess residual risk using the same scoring method as the original assessment. Capture the post-treatment likelihood and impact, note any compensating controls, and state whether the residual level is accepted, further treated, or escalated.
  • Set an illustrative monthly review by the ISMS manager or risk coordinator to chase overdue actions, validate evidence, and update management on blockers. Use concise status codes and comments that show why a treatment is delayed, such as vendor dependency, budget approval, or technical remediation.
  • Retain records that show the treatment journey from decision to closure: approval of the selected option, implementation proof, residual risk reassessment, and acceptance authority. If treatment changes midstream, keep the reason and revised due date so reviewers can follow the decision trail.

What an auditor will ask to see

  • Risk register rows showing action owner, target date, status, and residual risk before and after treatment.
  • Implementation artefacts such as change tickets, configuration screenshots, contract updates, or training logs tied to the treatment action.
  • Management escalation note for overdue treatment actions with revised dates or acceptance decision.

Baseline documents in the kit

These free kit documents help you document or evidence clause 8.3. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 8.2 — Information security risk assessment (operation) and 6.1.3 — Information security risk treatment. Keep the ownership and evidence consistent across these activities.

Plan your ISO/IEC 27001 implementation timeline for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.