Join our Newsletter — 33% off our NHI Course
Home› Guides› Risk Treatment Plan Template: ISO 27001 Clause 6.1.3…
Template Security Leadership & Governance

Risk Treatment Plan Template: ISO 27001 Clause 6.1.3 Actions, Owners and Acceptance

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 10 min read
On this page

Many organisations have a well-scored risk register but no plan that says, for each risk, what will be done, by whom, by when, at what cost and what risk will be left afterwards. That plan is the risk treatment plan required by ISO/IEC 27001:2022 clause 6.1.3, and auditors test it separately from the register and the Statement of Applicability. This template gives a ready-to-adopt treatment plan: the treatment options and how to choose between them, the fields each treatment action needs, how residual risk is approved and accepted by risk owners, and how progress is tracked and escalated. It uses the NIST risk response vocabulary (accept, avoid, mitigate, share or transfer) alongside ISO terms, so it also suits NIST CSF and SP 800-53 programmes. It is written for ISMS managers, GRC leads and risk owners. For the risk method itself, see the ISO/IEC 27005 Information Security Risk Guide.

How to use this template

  • Replace text in square brackets, such as [Organisation], [ISMS Manager], [Risk Committee] and [amount], with your own names and values.
  • "Must" indicates a mandatory requirement; "should" indicates a recommended practice where a documented exception may be justified.
  • Keep the treatment plan as a separate controlled document (or a separate view in your GRC tool) from the risk register. The register records the assessed risk; this plan records the decisions and actions taken in response.
  • Agree the acceptance authority table in section 3 before the first treatment decision, because residual risk can only be accepted by someone with authority for that level.
  • Use it with the Risk Register Template, the ISO 27001 Statement of Applicability Template and the Security Exceptions and Risk Acceptance Guide.

1. Purpose and scope

This plan records how [Organisation] treats the information security risks identified in its risk assessment, for the scope of the [ISMS / security programme] defined in [Scope Document, version]. It meets the requirement in ISO/IEC 27001:2022 clause 6.1.3 to formulate an information security risk treatment plan and to obtain risk owners' approval of the plan and acceptance of residual risks, and it is implemented under clause 8.3. It covers every risk rated above the acceptance criteria in [Risk Methodology, section x], and any risk below the criteria that a risk owner has chosen to treat.

2. Relationship to other documents

DocumentWhat it holdsLink to this plan
Risk methodologyCriteria for likelihood, impact and acceptance; approval authoritiesDefines when treatment is required and who can accept residual risk
Risk registerIdentified risks, owners, inherent and current ratingsEach plan entry cites a register ID
Statement of ApplicabilityAnnex A controls included or excluded, with justificationControls chosen here must appear in the SoA as included
Exceptions registerTime-limited deviations from policy or baselineA retained risk created by an exception is cross-referenced both ways
Budget and business casesFunding for treatment actionsFunded actions cite the case or budget line. See the Security Business Case Template.
POA&M (US federal and FedRAMP)Weaknesses with milestones (NIST SP 800-53 CA-5)Can serve as this plan for system-level risks if it carries owners and acceptance

3. Roles and acceptance authority

RoleResponsibilities
[Risk Owner]Chooses the treatment option with advice from security, approves the treatment actions, accepts residual risk within their authority.
[Action Owner]Delivers a treatment action by its due date and provides completion evidence.
[ISMS Manager / GRC Lead]Maintains this plan, checks that controls match the SoA, tracks progress, escalates overdue actions.
[CISO]Advises on control selection, challenges weak treatments, reports plan status to [Risk Committee].
[Risk Committee / Executive Committee]Approves acceptance of high residual risks and any risk retained above appetite.
Residual risk levelWho may acceptMaximum acceptance period
Low[Risk Owner][Until next annual review]
Medium[Risk Owner and CISO][12 months]
High[Executive Committee member][6 months]
Above appetite[Risk Committee or Board][3 months, with a treatment plan]

4. Treatment options and selection

For each risk the risk owner must select one or more options. NIST defines risk response as accepting, avoiding, mitigating, sharing or transferring risk; ISO/IEC 27005 and ISO 31000 describe equivalent choices. A single risk often needs a combination, for example mitigation plus insurance.

OptionWhat it meansChoose it whenExample
Mitigate (modify)Add or improve controls to reduce likelihood or impactCost of controls is proportionate to the risk reductionEnforce phishing-resistant MFA for administrators; segment backup networks
AvoidStop or change the activity that creates the riskThe activity is not essential or cannot be secured at reasonable costDecommission an internet-facing legacy application
Share or transferPass part of the impact to another party by contract or insuranceFinancial impact is the main concern and a capable party existsCyber insurance; contractual liability with a managed service provider
Accept (retain)Make an informed decision to keep the risk at its current levelRisk is within appetite, or treatment cost exceeds benefit, and an authorised owner agreesAccept residual risk on an isolated test system until its retirement date
  1. Determine controls from any source: controls may come from ISO/IEC 27001 Annex A, NIST SP 800-53, CIS Controls or the organisation's own design. Compare the chosen controls with Annex A to confirm no necessary control has been overlooked (clause 6.1.3 c), and update the SoA.
  2. Transfer does not move accountability: sharing risk with a supplier or insurer changes who pays, not who answers to regulators and customers. Record the residual operational and reputational risk.
  3. Accept means a record, not silence: an accepted risk must have an owner, a rationale, an expiry date and a review trigger.

5. Treatment plan register

Each treatment action must be recorded with at least these fields.

FieldDescriptionExample (illustrative)
Plan ID and risk IDPlan reference and register referenceRTP-017; R-042
Risk summary and current ratingOne sentence and current levelStolen CI/CD tokens give production access; High
Option chosen and rationaleFrom section 4Mitigate: tokens are long-lived and widely scoped
ActionsSpecific, testable stepsReplace static cloud keys in pipelines with short-lived workload identity federation; restrict token scopes
Controls and referencesAnnex A, SP 800-53 or internal IDs[Annex A control]; SP 800-53 AC-2, IA-5
Action owner and due dateNamed person and date[Platform Engineering Lead]; [DD/MM/YYYY]
Resources and costEffort, budget line, business case[20 days]; [SEC-PR-008]
Target residual ratingExpected level after treatmentLow
Status and evidenceNot started, in progress, complete, verifiedComplete; [link to configuration evidence]
Residual risk approvalOwner, date, expiry[Name]; [date]; [review in 12 months]

Machine credentials deserve a note here: many high risks in modern registers concern service accounts, API keys and pipeline tokens, and their treatments (rotation, short-lived credentials, scope reduction, ownership) need an owning engineering team, not only a policy owner. See the Non-Human Identity (NHI) Guide.

6. Residual risk approval and acceptance

  1. When the actions for a risk are planned, the risk owner must approve the plan entry and the target residual rating.
  2. When actions are complete and verified, the risk must be reassessed and the actual residual rating recorded in the register.
  3. The risk owner must formally accept the residual risk within the authority limits in section 3. Acceptance records must state who, when, the level accepted and the expiry date.
  4. Where residual risk remains above appetite, the entry must be escalated to [Risk Committee] with the options considered and the reason no further treatment is proposed.

7. Monitoring, escalation and closure

  • Review cycle: [ISMS Manager] reviews plan status [monthly] with action owners, and reports to [Risk Committee] [quarterly].
  • Overdue actions: actions overdue by more than [30] days are escalated to the risk owner; by more than [90] days to [CISO] and [Risk Committee], with a revised date or an acceptance decision.
  • Verification: an action is closed only when evidence shows the control operates (for example a configuration export, test result or audit sample), not when a ticket is closed.
  • Triggers for re-planning: a significant incident, a major change, new threat intelligence or an audit finding that affects a treated risk.
  • Measures: percentage of actions on time; number of risks above appetite without an approved plan; median age of open actions; accepted risks past expiry; actions closed without verification evidence.

8. Review and approval

This plan is reviewed at least [annually], at each risk assessment cycle (clause 8.2) and after significant change, and its status is an input to management review. Version: [1.0]. Owner: [ISMS Manager]. Approved by: [Name, role]. Date: [DD/MM/YYYY]. Next review: [DD/MM/YYYY].

Implementation guidance

  1. Start from the register: extract every risk above acceptance criteria and confirm each has a named risk owner with authority.
  2. Hold treatment workshops by risk owner: one session per owner is faster than one per risk, and gives consistent choices.
  3. Write testable actions: "improve access control" cannot be verified; "remove standing Global Administrator roles and require just-in-time activation" can.
  4. Reconcile with the SoA: every control named in the plan must appear as included in the Statement of Applicability, with the risk as justification.
  5. Record acceptances properly: collect signed or system-recorded acceptance with expiry dates before the certification audit, not during it.
  6. Pilot then extend: run the plan for the top [10] risks for one quarter, fix the process, then extend to all treated risks.
  7. Roll back safely: if moving from spreadsheets to a GRC tool, keep the exported plan as the controlled record until the tool has passed one internal audit.

Weaknesses auditors commonly find

  • Plan and register are the same list: treatment columns are added to the register with no owner approval or acceptance record, so the plan cannot be shown as a distinct, approved document.
  • Acceptance by the wrong person: the security team accepts residual risk on behalf of a business owner who never saw it.
  • Accepted forever: acceptances carry no expiry date, so risks accepted for a migration remain years after the migration slipped.
  • Controls missing from the SoA: the plan names controls that the Statement of Applicability marks as excluded or does not mention.
  • Closed without evidence: actions are marked complete because a change ticket closed, but no one checked that the control operates.

Framework mapping

FrameworkReferenceWhat this plan provides
ISO/IEC 27001:2022Clauses 6.1.3 and 8.3Treatment plan, owner approval, residual risk acceptance, implementation
NIST CSF 2.0ID.RA-06, ID.RA-07, GV.RM-02Risk responses planned and tracked; exceptions recorded; appetite and tolerance applied
NIST SP 800-53 Rev. 5RA-7, CA-5, PM-4, PM-9Risk response, POA&M, POA&M process, risk management strategy
NIST IR 8286 seriesIR 8286 Rev. 1, IR 8286BRisk response and projected cost recorded in the cybersecurity risk register
UK Cyber Governance Code of PracticePrinciple ARisk appetite set and a plan to meet it; mitigations kept current

Related NHI Mgmt Group resources: ISO/IEC 27005 Information Security Risk Guide · ISO 27001 Certification Guide · Risk Register Template · Security Exceptions and Risk Acceptance Guide · Risk Appetite and Tolerance for Cyber Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.