← ISO 27001: Critical success factors ISO 27001

ISO 27001: The Risk Improvement Plan

Risk treatment and corrective action (clauses 6.1.3, 8.3 and 10)

Tom Whipp · 31 October 2026 · 4 min read

Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.

What it is

The risk improvement plan is the list of what you're going to do about your risks and your gaps, who's doing it and by when. It's where the forum's decisions turn into work.

Every organisation has gaps, and the standard is realistic about that. You can be certified while carrying known risks and unfinished improvements, as long as they're understood, owned and on an approved plan. Nonconformities against the standard itself are treated more strictly, as explained below. Either way, the credibility of this plan is critical to passing certification.

What the standard asks

Several clauses land here:

  • Risk treatment (6.1.3). Choose how to treat each risk, formulate a risk treatment plan, and get risk owners to approve the plan and accept the residual risk.
  • Implementation (8.3). Carry out the plan and keep the results.
  • Continual improvement (10.1). Keep improving the suitability, adequacy and effectiveness of the ISMS.
  • Nonconformity and corrective action (10.2). When something doesn't conform, react to it and correct it, then find the cause, decide whether corrective action is needed to stop it recurring, take that action, check it worked, and record what you did.

The standard doesn't require these to be separate documents. Many organisations keep treatment actions alongside the risks they relate to, which works well as long as the plan can be seen and reviewed as a whole.

Nonconformities: major and minor

A nonconformity is a failure to meet a requirement, either of the standard or of your own ISMS. Certification auditors grade them:

  • Major. A required process is missing or has broken down, or a failure casts real doubt on whether the ISMS is working: no management review held, no internal audit, or risk assessment never carried out. A major normally has to be corrected, and the corrective action accepted by the certification body, before a certificate is issued. That sometimes means a follow-up visit.
  • Minor. An isolated lapse that doesn't undermine the system, such as one missed access review or a policy past its review date. The certificate can usually be issued once the certification body accepts your plan, and they check progress at the next surveillance audit. Several minors can be open at certification; what matters is that each one has an accepted plan.
  • Observations or opportunities for improvement aren't nonconformities. They're the auditor's suggestions.

Minors that repeat, or that aren't addressed, can be raised to a major. This is where the credibility of your improvement plan matters most.

What good looks like

  • One plan, several sources. Actions from risk treatment, audit findings, events, metrics and forum decisions all live in the same place, each linked back to what raised it.
  • Every action has an owner, a realistic date and a status. Overdue actions are visible and re-planned openly at the forum.
  • Each action keeps its origin. A combined tracker works well as long as it's clear whether each item is risk treatment, a correction, a corrective action or a general improvement.
  • Closure needs evidence. An action is closed when someone can show it's done, and it stays closed. If more work is needed, a new action references the old one.
  • Risk owners approve the plan and accept what's left, and the minutes show it.

Evidence an auditor will ask for

  • The risk treatment plan, with owners and target dates
  • Risk owners' approval of the plan and acceptance of residual risk
  • Records of nonconformities, their causes and the corrective action taken
  • Evidence that closed actions were completed and checked

Common failure modes

  • The plan of everything. Fifty actions, all due next quarter, all slipping. A shorter plan that leadership believes is worth far more than a long one nobody expects to finish.
  • Dates that quietly move. Repeated re-dating without discussion is one of the first things an auditor will pick up.
  • Closed on say-so. Actions marked done without evidence come back as findings.
  • A plan that only exists at audit time. If the forum doesn't review it, it isn't the forum's plan.

How it connects

Feeds from

Feeds into

Where it sits in the plan

Stage: Plan, then Act on every cycle. The first plan comes out of the forum's review of the initial risk assessment. After that it's where Act lands: every cycle adds actions from audits, events and metrics, and closes the ones that are done.

The plan in the main article shows how this fits with everything else, and the bootstrapping guide covers each stage in detail.

Resources


Tom Whipp is the founder of RiskQuilt. He spent around thirty years in cyber and technology risk in UK financial services, including CISO and Director of Technology Risk roles.

Ready to leave the spreadsheets behind?

Start your free trial today. No credit card required. No sales call. Your data, your platform, in minutes.