Cybernion
← Insights

ISO 22301

What Is ISO 22301? Business Continuity Management Explained

3 July 2026 · Updated 3 July 2026

ISO 22301 is the international standard for a business continuity management system. It sets out how an organisation identifies its critical activities, decides how quickly they must recover, and puts strategies and plans in place to keep operating through disruption. The current version is ISO 22301:2019, and it can be independently certified.

Most continuity plans are written once, filed, and never tested against a real outage. ISO 22301 exists to stop that. It asks whether an organisation runs a system for continuity, not whether it owns a plan document.

What is ISO 22301 in plain terms?

ISO 22301 is the international standard for a business continuity management system (BCMS), published by ISO. It defines how an organisation prepares for, responds to and recovers from disruptive incidents. The current edition is ISO 22301:2019, titled Security and resilience, Business continuity management systems, Requirements. It replaced the 2012 first edition and carries a 2024 amendment covering climate change.

The standard does not dictate which disasters to plan for or what technology to buy. It sets the requirements for the system that makes those decisions: how continuity is scoped, who owns it, how the impact of disruption is analysed, and how it is tested and improved. Certification against ISO 22301 confirms that this system exists, runs and is maintained. It is a management system standard, not a recovery product. Compare it with information security in our guide to ISO 22301 versus ISO 27001.

What does a business continuity management system (BCMS) actually cover?

A BCMS covers the full loop from understanding the organisation to improving after an incident. It starts by identifying the products and services that must keep being delivered, then works out the activities behind them and how long each can be interrupted before the damage becomes unacceptable.

From there the system sets recovery objectives, chooses continuity strategies, and documents the plans people follow during a disruption. It defines roles, communication, and the resources each recovery depends on. It then exercises those plans, records what failed, and feeds the lessons back in.

The point is that continuity becomes a managed, audited discipline rather than a binder. ISO 22301 groups these requirements under clauses 4 to 10, which we break down in ISO 22301 clauses explained. The analysis that drives most of it is the business impact analysis, covered in our business impact analysis guide.

How is ISO 22301 structured?

ISO 22301 uses the Annex SL high level structure, the common ten clause skeleton ISO applies across its modern management system standards. The requirements audited against live in clauses 4 to 10, which follow a Plan, Do, Check, Act rhythm.

Clause Title What it asks for
4 Context Understand the organisation, interested parties and the BCMS scope
5 Leadership Top management commitment, policy and continuity roles
6 Planning Address risks and opportunities, set continuity objectives
7 Support Resources, competence, awareness, communication, documentation
8 Operation Business impact analysis, risk assessment, strategies, plans, exercising
9 Performance evaluation Monitoring, measurement, internal audit, management review
10 Improvement Handle nonconformity, corrective action, continual improvement

Clauses 1 to 3 cover scope, normative references and terms, and hold no auditable requirements. Because this is the same structure used by ISO 27001 and ISO 9001, an organisation running one of those standards already knows the structure of this one.

What are RTO, RPO and MAO in ISO 22301?

RTO, RPO and MAO are the recovery targets that turn a business impact analysis into something concrete. Recovery Time Objective (RTO) is the time within which an activity must be restored after disruption. Recovery Point Objective (RPO) is the maximum data loss that is acceptable, measured as the point in time recovery must reach back to. Maximum Acceptable Outage (MAO) is the longest an activity can be down before the harm becomes unacceptable, so every RTO has to be shorter than its MAO.

These numbers are not guesses. They come out of the business impact analysis, where the impact of losing an activity is judged over time. Once set, they drive everything downstream: the strategies funded, the plans written, and the recovery capability built. Get them wrong and the result is either overspending on activities that can wait or under protecting the ones that cannot.

Who needs ISO 22301?

Any organisation whose customers, regulators or contracts depend on it staying operational is a candidate for ISO 22301. It is common in financial services, government, health, critical infrastructure, data centres and managed services, where a prolonged outage causes real harm and continuity is often a contractual or regulatory expectation.

In Australia it also intersects with sector rules. APRA regulated entities work to CPS 230 on operational risk and business continuity, and critical infrastructure operators have resilience obligations under the SOCI regime. ISO 22301 is not those rules, but a working BCMS makes meeting them far easier because the underlying discipline is shared. For weighing which standards apply, see how to choose a cyber security framework in Australia. For continuity as part of a broader information security programme, our ISO 27001 guide covers the neighbouring standard.

How do we get certified to ISO 22301?

Build the management system, run it long enough to generate records, then bring in an accredited certification body. The auditor works in two stages: a stage one review of the documentation and readiness, then a stage two on site audit that tests whether the BCMS operates as described and meets clauses 4 to 10.

Before that, most of the work is internal: define scope, complete a business impact analysis and risk assessment, set recovery objectives, choose strategies, write and exercise plans, and run at least one internal audit and management review so there is evidence to audit. A certificate typically lasts three years, with annual surveillance audits and a full recertification at the end of the cycle. As with any ISO standard, the certificate says the system meets the requirements, not that disruption will never happen. Our ISO 27001 and business continuity service covers both the information security and continuity management pathways.

Frequently asked questions

What is ISO 22301 used for?

ISO 22301 is used to build and certify a business continuity management system. It gives an organisation a repeatable way to work out which activities matter most, how long they can be down, and what it will do to keep them running or restore them after a disruption such as an outage, a cyber attack or a supplier failure.

Is ISO 22301 certifiable?

Yes. ISO 22301 is a certifiable management system standard. An accredited certification body audits the business continuity management system against clauses 4 to 10, and if it conforms the organisation receives a certificate, usually valid for three years with annual surveillance audits in between.

What is the current version of ISO 22301?

The current version is ISO 22301:2019, the second edition, published in October 2019. A 2024 amendment added climate change wording to the context and planning requirements. The standard is under systematic review, so a future revision is possible, but 2019 remains the version in force.

What is the difference between ISO 22301 and a disaster recovery plan?

A disaster recovery plan is a technical document for restoring IT systems after an incident. ISO 22301 is the management system around it. It covers governance, the business impact analysis, recovery objectives, strategies, plans, exercises and improvement, of which IT disaster recovery is one part.

How long does ISO 22301 certification take?

For most organisations, building a business continuity management system and reaching certification takes six to twelve months, depending on size, scope and how much continuity work already exists. The certification audit itself runs in two stages, a documentation review followed by an on site assessment.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. ISO 22301:2019 Security and resilience, Business continuity management systems, Requirements, ISO, published October 2019 (Edition 2)
  2. ISO 22301:2019/Amd 1:2024 Climate action changes, ISO, 2024
  3. ISO 22313:2020 Guidance on the use of ISO 22301, ISO, 2020

Last updated: 3 July, 2026

Talk to us about your engagement

A scoped proposal within one business day.