ISO 22301 Certification: The Path from Scope to Certificate
ISO 22301 certification is the independent audit that proves your business continuity management system can keep critical services running, or bring them back fast, after a disruption. This guide walks through the path in order, from scoping to the three-year certificate cycle, with notes for SaaS and service companies that already hold SOC 2 or ISO 27001.
For what the standard is and who buys it, start with the ISO 22301 guide. This post assumes you have decided to certify.
What ISO 22301 Certification Is (in One Paragraph)
ISO 22301 sets the requirements for a business continuity management system (BCMS): a managed way to understand what your organization must keep running, how fast it must recover, and how you prepare for, respond to, and learn from disruptions. ISO publishes the standard but does not certify anyone. An accredited certification body audits your BCMS against ISO 22301 and issues the certificate. In the United States, ANAB is one of the bodies that accredits certification bodies for ISO 22301.
Why SaaS Buyers Ask for It
Business continuity used to be a bank and utility topic. Now it shows up in enterprise vendor reviews for software and service companies. Large customers want to know what happens to them if you have an outage, lose a cloud region, or lose a key team.
That is why the large cloud providers publish ISO 22301 certificates alongside their security reports. If you build on a cloud provider with ISO 22301, you can use its certificate as supporting evidence. It does not cover your own application, team, or processes, though. Your BCMS still has to cover those.
Organization Certification vs Individual Credentials
Many search results for ISO 22301 certification are courses for individuals, such as lead implementer, lead auditor, or business continuity manager credentials. These certify a person's knowledge. They do not certify a company.
A trained lead implementer is useful for running your project. But the certificate a customer asks for in a vendor questionnaire is the organizational one, issued by an accredited certification body. The rest of this guide covers that path.
The Current Edition: ISO 22301:2019 and the 2024 Amendment
ISO 22301:2019 is the current edition. In February 2024, ISO added Amendment 1, a short climate action change applied across many management system standards. It asks you to:
- Consider climate in your context (clause 4.1). Decide whether climate change is a relevant issue for your BCMS. For many companies, climate-driven events such as floods, heat waves, and grid outages are real continuity risks.
- Note climate requirements of interested parties (clause 4.2). Customers, regulators, or insurers may have climate-related expectations.
National standards bodies list a full revision in early development. It is not close to publication, so build to the 2019 edition with the amendment and confirm the audit edition with your certification body.
Step 1: Scope and Context
Scope is the most important decision in an ISO 22301 project. It defines which products, services, sites, and teams the BCMS covers.
For a SaaS company, a common scope is the production platform and the teams that support it: engineering, operations, support, and the functions they depend on. A narrow scope is faster and cheaper. But if a customer's contract depends on a service you left out, the certificate will not answer their question.
Also settle ownership. Name a BCMS lead and get top management to commit. Leadership involvement is a frequent audit finding when it is weak.
Step 2: Business Impact Analysis and Risk Assessment
These two analyses are the core of ISO 22301. They are where most first-time projects spend the most effort.
Business impact analysis
A business impact analysis (BIA) identifies the activities that deliver your products and services and works out what happens over time if each one stops. From that, you set:
- Maximum tolerable period of disruption. How long an activity can be down before the impact becomes unacceptable.
- Recovery time objective (RTO). How fast you must restore the activity, which must be shorter than the maximum tolerable period.
- Minimum service level. What reduced level of service is acceptable during recovery.
- Dependencies. The people, systems, data, suppliers, and facilities each activity needs.
For data, you will also set a recovery point objective (RPO): how much data loss is acceptable. Tie RTOs and RPOs to customer commitments, such as your SLA.
Risk assessment
The risk assessment looks at what could disrupt those prioritized activities, such as a cloud region failure, a ransomware attack, a key supplier failing, or losing a building. You assess likelihood and impact, then decide how to treat each risk.
Step 3: Strategies, Plans, and Exercises
Continuity strategies
For each prioritized activity, choose how you will protect it and recover it. Options include redundancy, failover to another region, alternate suppliers, cross-trained staff, or manual workarounds. The strategy must meet the RTO and RPO you set in the BIA.
Plans and procedures
Write plans people can actually use during an incident. ISO 22301 expects a response structure with clear roles, warning and communication procedures, and recovery steps. Keep plans short, current, and easy to find when systems are down.
Exercising and testing
ISO 22301 requires you to exercise and test your plans. That can range from a tabletop walk-through to a live failover test. Record what happened, what went wrong, and what you changed. Auditors look closely at exercise records, because a plan that has never been tested is only a theory.
A practical exercise program builds up over time:
- Plan walk-through. The team reads the plan together and checks contacts, roles, and steps are current.
- Tabletop exercise. Leaders work through a realistic scenario, such as a cloud region outage or ransomware, and make decisions as they would in a real event.
- Technical recovery test. Restore a backup or fail over a service, and measure the actual recovery time against your RTO.
- Full simulation. Combine people, communication, and technical recovery in one exercise, usually once the earlier types run smoothly.
Pick scenarios from your risk assessment, so you test the disruptions that matter most. Cover the full set of prioritized activities across the three-year cycle.
Step 4: Internal Audit and Management Review
Before the certification audit, the BCMS needs an operating history and two formal checks:
- Internal audit. Audit the BCMS against ISO 22301 and your own procedures, using people independent of the area. Fix findings through corrective action.
- Management review. Top management reviews BIA results, risks, exercise outcomes, incidents, and audit results, then records decisions.
If you already run these for ISO 27001, you can extend the same cycle to cover the BCMS.
Step 5: Stage 1 and Stage 2 Audits
The certification audit has two stages, run by an accredited certification body.
Stage 1 reviews readiness. The auditor checks your scope, BIA, risk assessment, strategies, plans, exercise program, internal audit, and management review. You learn whether you are ready for Stage 2 and which areas may lead to findings.
Stage 2 tests implementation. The auditor samples records, interviews staff, and checks that plans match reality and that exercises happened. Minor nonconformities need a corrective action plan. Major nonconformities must be closed before a certificate is issued.
The certificate is valid for three years, with annual surveillance audits and a full recertification audit at the end of the cycle.
Using SOC 2 and ISO 27001 Evidence
If you already hold SOC 2 or ISO 27001, you are not starting from zero. Backup, disaster recovery, incident response, and supplier management evidence often carries over.
The gaps are usually in the parts that are unique to ISO 22301: a formal BIA with tolerable disruption periods, continuity strategies for non-technical activities, and a structured exercise program. For a detailed control comparison, see ISO 22301 vs SOC 2 and ISO 22301 vs ISO 27001.
What Drives the Timeline
Many organizations take several months to a year from kickoff to certificate. The main drivers are:
- Existing disaster recovery. Documented and tested recovery for your platform saves a lot of time.
- Scope size. More services, sites, and teams mean more BIA work.
- Decision speed. Leadership has to approve recovery objectives and strategies. Slow decisions stall projects.
- Exercise history. You need at least some exercise records before Stage 2.
- Findings. Major nonconformities must be closed first.
What Drives the Cost
We do not quote prices in a blog post. The cost of ISO 22301 certification depends on scope, size, and starting point, and comes down to these buckets:
- Readiness work. Scoping, BIA facilitation, risk assessment, plan writing, and exercise design.
- Internal effort. Time from service owners, engineering, and leadership. This is often the largest hidden cost.
- Certification body fees. Audit days for Stage 1 and Stage 2, based on headcount, sites, and complexity.
- Recovery capability. If the BIA shows you cannot meet a required RTO, closing that gap, such as adding multi-region failover, has its own cost.
- Ongoing costs. Surveillance audits, recertification, and regular exercises.
When comparing quotes, check whether the certification body can run a combined audit with ISO 27001. That can reduce audit days.
Where Teams Get Stuck
- Treating disaster recovery as the whole BCMS. ISO 22301 covers people, suppliers, and facilities, not only systems.
- RTOs that nobody approved. Recovery objectives need leadership sign-off and must match customer commitments.
- Plans nobody has read. If staff cannot find or follow the plan, it fails the exercise and the audit.
- No real exercises. A tabletop once a year with no lessons recorded is a weak record.
- Scope that misses what customers care about. Check your contracts before fixing the scope.
For the foundation, read the ISO 22301 guide. For overlaps, see ISO 22301 vs SOC 2 and ISO 22301 vs ISO 27001. For combined systems, read about integrated management systems. For service details, see our ISO 22301, ISO 27001, and SOC 2 pages.
Frequently Asked Questions
What does ISO 22301 certified mean? An accredited certification body has audited your business continuity management system and confirmed it meets the standard. It shows you know your critical activities, have recovery objectives, and test your plans.
How do I get ISO 22301 certification? Scope the BCMS, run a BIA and risk assessment, choose strategies, write plans, and exercise them. Complete an internal audit and management review, then pass Stage 1 and Stage 2 audits with an accredited certification body.
How much does it cost to get ISO 22301 certified? It depends on scope, size, sites, and existing continuity work. The buckets are readiness work, internal time, audit fees, any new recovery capability, and ongoing audits. Compare written quotes.
Is there a certification for ISO 22301? Yes. Organizations are certified by accredited certification bodies. Individuals can earn course credentials such as lead implementer, but those do not certify a company.
Which edition of ISO 22301 is current? ISO 22301:2019 with Amendment 1:2024, which adds climate action changes. A revision is in early development, so confirm the audit edition with your certification body.
Does ISO 22301 certification replace SOC 2 or ISO 27001? No. It adds depth on continuity and recovery. Evidence overlaps, but customers asking for SOC 2 or ISO 27001 will still expect those.
Ready to Start Your ISO 22301 Certification?
ShieldKey Solutions runs the readiness work: scoping, business impact analysis, continuity strategies, exercise design, and internal audit preparation. If you already hold SOC 2 or ISO 27001, we map your existing evidence so you only build what is missing.