ISO 22301: what it is and how certification works

ISO 22301 explained: what the business continuity standard requires clause by clause, the 2024 climate amendment, its link to NIS2 and DORA, and certification.

8 min read
ISO 22301: what it is and how certification works

Key takeaways

  • ISO 22301 is the international standard that sets the requirements for a business continuity management system (BCMS): voluntary, and certifiable by an accredited certification body.
  • The current edition is ISO 22301:2019, amended in 2024 to ask whether climate change is a relevant issue; IAF treated the change as a clarification, with no revised certificate needed.
  • The requirements sit in clauses 4 to 10; those specific to business continuity are almost all in clause 8: business impact analysis and risk assessment, strategies, plans and procedures, exercises.
  • Neither NIS2 nor DORA requires ISO 22301, but NIS2 Article 21(2)(c) and DORA Article 11 require business continuity, and the standard is a recognised way to organise it.
  • Certification runs through Stage 1 and Stage 2 audits by a body accredited under ISO/IEC 17021-1, then surveillance audits and recertification; the certification body cannot also be your consultant.
  • Organisations with ISO/IEC 27001 or ISO 9001 reuse the shared structure of clauses 4 to 10; clause 8 is the new work.

ISO 22301 is the international standard that sets the requirements for a business continuity management system (BCMS): how an organisation prepares for disruption, keeps delivering its products and services at an acceptable level while it lasts, and returns to normal. The current edition is ISO 22301:2019, amended in 2024 on climate change. It is voluntary and can be certified by an accredited certification body.

Below: what the standard asks clause by clause, what changed between editions, how it relates to NIS2 and DORA, and how certification works in practice. If you first need the background on business continuity itself, and how it differs from disaster recovery, start with our guide to the business continuity plan.

What ISO 22301 is, in practice

The full title is Security and resilience, Business continuity management systems, Requirements. It is developed by the ISO technical committee ISO/TC 292, Security and resilience, and adopted in Europe as EN ISO 22301, so the same text sits behind the national editions published by European standards bodies.

According to its scope, the standard sets requirements to implement, maintain and improve a management system that reduces the likelihood of disruptions and lets the organisation prepare for, respond to and recover from them when they happen. It applies to organisations of any type and size, and also to a part of an organisation.

Two features set it apart from a good-practice guide:

  • It is a requirements standard. It says what has to be in place, not how to build it, which is why a third party can audit it.
  • It covers a management system, not a single plan. Policy, roles, objectives, analysis, plans, exercises, internal audit, management review and improvement are held together and kept current over time.

A companion standard, ISO 22313, gives guidance on the use of ISO 22301. It contains guidance, not requirements, so certification is always against ISO 22301.

ISO 22301:2019 and the 2024 amendment

The first edition was ISO 22301:2012. The second, ISO 22301:2019, replaced it, and its foreword notes that the requirements specific to business continuity were brought together almost entirely in clause 8. The transition from the 2012 edition is over: in a technical bulletin of 28 April 2020, UKAS, the UK national accreditation body, set its end at 30 April 2023, after a six-month extension of all transitions decided by IAF. A certificate you see today refers to the 2019 edition.

Amendment 1:2024 on climate change

In February 2024 ISO amended a group of management system standards, ISO 22301:2019 among them, to add two statements to the shared clauses on context and interested parties. The joint ISO and IAF communiqué of 22 February 2024 gives the added text. In clause 4.1: "The organization shall determine whether climate change is a relevant issue." In clause 4.2, a note that relevant interested parties can have requirements related to climate change.

For business continuity the question is concrete: floods, heatwaves or wildfires can become disruption scenarios for a site, a supplier or a logistics route, and belong in the risk assessment if they are relevant.

For organisations already certified, the communiqué states that the overall intent of clauses 4.1 and 4.2 is unchanged. The IAF decision published with it treated the change as a clarification rather than a new requirement, with no full transition programme, and stated that a revised certificate should not need to be issued. Auditors check the point as part of the normal audit of context.

What ISO 22301 requires, clause by clause

Like the other ISO management system standards, ISO 22301 applies the Plan-Do-Check-Act cycle and follows the harmonised structure. The same communiqué lists ISO 22301:2019 and ISO/IEC 27001:2022 among the standards that share it, which makes integration with a system you already run simpler. The requirements sit in clauses 4 to 10:

  • 4, Context of the organisation: internal and external issues, interested parties, legal and regulatory requirements, scope of the BCMS.
  • 5, Leadership: top management commitment, business continuity policy, roles and responsibilities.
  • 6, Planning: risks and opportunities for the system, business continuity objectives, planning of changes.
  • 7, Support: resources, competence, awareness, communication, documented information.
  • 8, Operation: the core of the discipline, described below.
  • 9, Performance evaluation: monitoring and measurement, internal audit, management review.
  • 10, Improvement: nonconformity, corrective action, continual improvement.

Clause 8: where business continuity lives

The sub-clauses of clause 8 follow the order in which the work is actually done:

  1. 8.1, Operational planning and control: the processes needed to meet the requirements are planned, run and controlled.
  2. 8.2, Business impact analysis and risk assessment: which activities matter, how much downtime each can tolerate, which events can interrupt them.
  3. 8.3, Business continuity strategies: identification, selection, the resources needed and putting them in place.
  4. 8.4, Business continuity plans and procedures: response structure, warning and communication, the plans themselves, recovery.
  5. 8.5, Exercise programme: plans are tested, not assumed.
  6. 8.6, Evaluation of business continuity documentation and capabilities: periodic evaluation of the plans and of the capabilities behind them.

Clause 8.4 is where the business continuity plan sits. If you are writing one, our business continuity plan template follows the same order: analysis first, strategies second, plans third.

Is ISO 22301 mandatory?

No. ISO 22301 is voluntary, and neither NIS2 nor DORA asks for a certificate. Business continuity itself, however, is an obligation for many organisations:

  • NIS2. Article 21(2)(c) of Directive (EU) 2022/2555 lists "business continuity, such as backup management and disaster recovery, and crisis management" among the cybersecurity risk-management measures of essential and important entities. Article 21(1) asks that the measures take into account, where applicable, relevant European and international standards, and Article 25 asks Member States to encourage their use. Under Article 20 the management bodies approve the measures and oversee their implementation. How the measure is detailed depends on each Member State's transposing law; our guide to the NIS2 Directive covers the framework.
  • DORA. For financial entities, Article 11 of Regulation (EU) 2022/2554 requires a comprehensive ICT business continuity policy, a business impact analysis of exposures to severe business disruptions (Article 11(5)) and testing of the ICT business continuity plans at least yearly (Article 11(6)).

ISO 22301 is a recognised way to organise those obligations into a single system. Certification adds an independent check, repeated over the certificate's life, that the system exists and works, which is evidence that customers, tenders and supervisors can read without rebuilding it themselves.

How ISO 22301 certification works

The certificate is issued by a certification body, not by ISO. What makes it credible is accreditation: in the EU, Article 4(1) of Regulation (EC) No 765/2008 requires each Member State to appoint a single national accreditation body, and bodies that certify management systems are accredited against ISO/IEC 17021-1. Before choosing one, check that its accreditation covers ISO 22301 specifically, not only ISO 9001 or ISO/IEC 27001. The criteria are the same as for information security, explained in our article on how to choose a certification body.

The path, in sequence

  1. Gap analysis against clauses 4 to 10, to know where you start.
  2. Scope and mandate from management: which products, services, sites and suppliers are in the system.
  3. Business impact analysis and risk assessment, then continuity strategies.
  4. Plans and procedures, with roles, activation conditions and communication.
  5. Exercises, recorded, with the lessons learnt.
  6. Internal audit and management review.
  7. Stage 1 and Stage 2 audits by the certification body: Stage 1 checks readiness and documentation, Stage 2 checks that the system works in practice.
  8. Certificate and cycle: surveillance audits in the following years, then a recertification audit before the certificate expires.

Preparation and certification are separate jobs. ISO/IEC 17021-1 bars a certification body, and any entity under its organisational control, from offering management system consultancy, so the people who help you build the BCMS are not the people who certify it.

What an ISO 22301 auditor looks for

The auditor follows the clauses, but in practice the questions come back to a few points:

  • A real scope. The BCMS covers the activities that deliver your products and services, not only the IT department.
  • Suppliers inside the picture. If a critical activity depends on an outsourced service, that supplier and its recovery times appear in the analysis and, where it matters, in the contracts.
  • Analyses that are kept current. The business impact analysis and the risk assessment reflect today's organisation, not the one of three years ago.
  • Evidence of exercises. Records of what was tested, what did not work and what was changed afterwards, linked to clauses 8.5 and 8.6.
  • Management involvement. Approved policy and objectives, a management review with decisions, resources actually assigned.

Almost all of these points need fresh evidence at every surveillance audit. Keeping the business impact analysis, plans and exercise records tied to the tools you already use, instead of in folders rebuilt once a year, is what makes the cycle sustainable.

If you already hold ISO/IEC 27001 or ISO 9001

Because ISO 22301 shares the harmonised structure of clauses 4 to 10, policy, documented information, internal audit, management review and corrective action can be the same processes you already run for quality or information security, extended to business continuity.

What you do not inherit is clause 8. Business impact analysis, strategies, plans and exercises are specific work. Organisations with ISO/IEC 27001 often start from backup and system recovery; ISO 22301 asks you to start from business processes, including people, sites and suppliers. Our ISO 27001 page explains how an existing ISMS can be the base for an integrated system.

Where to start

Three questions tell you how far you are from ISO 22301. Do you have a current business impact analysis on the activities that carry revenue and obligations? Do your continuity plans have named roles, activation conditions and an exercise recorded in the last year? Are your critical suppliers inside the scope, with recovery times written into the contracts? If the answer is no to more than one, a gap analysis is the first step.

If you want to see how a certifiable system is built on your processes and your starting point, look at our ISO 22301 certification path.

Frequently asked questions

ISO 22301 is the international standard that sets the requirements for a business continuity management system: how an organisation prepares for disruption, keeps delivering its products and services at an acceptable level while it lasts, and returns to normal. The current edition is ISO 22301:2019, amended in 2024. Certification is voluntary: you build the system, then a certification body accredited under ISO/IEC 17021-1 runs a Stage 1 and a Stage 2 audit, followed by surveillance audits and a recertification audit before the certificate expires.
ISO 22301:2019, the second edition, which replaced ISO 22301:2012. It was amended in February 2024 by ISO 22301:2019/Amd 1:2024, which adds to clause 4.1 that the organisation determines whether climate change is a relevant issue, and a note to clause 4.2 that interested parties can have climate-related requirements. The IAF decision on the amendment treated it as a clarification and stated that a revised certificate should not need to be issued.
No. ISO 22301 is voluntary. NIS2 (Directive (EU) 2022/2555, Article 21(2)(c)) lists business continuity, backup management, disaster recovery and crisis management among the risk-management measures, and asks that relevant European and international standards be taken into account where applicable. DORA (Regulation (EU) 2022/2554, Article 11) requires financial entities to have an ICT business continuity policy, a business impact analysis and yearly tests of their plans. Neither asks for a certificate; ISO 22301 is a recognised way to organise and evidence those obligations.
ISO 22301 contains the requirements of a business continuity management system and is the standard you certify against. ISO 22313 gives guidance on the use of ISO 22301: it helps you interpret and apply the requirements, but it is not a certification standard.
Yes. Both follow the harmonised structure of ISO management system standards, so policy, documented information, internal audit, management review and corrective action can be shared processes. The specific work of ISO 22301 is in clause 8: business impact analysis, continuity strategies, plans and exercises, which start from business processes rather than from IT systems alone. Check that your certification body is accredited for both standards if you want integrated audits.

Let's talk about your security.

A 30-minute call to understand where you stand today and tell you, with no commitment, where it pays to start.

Book a call