An emergency plan in a binder is not evidence. Business continuity only becomes demonstrable once the required and the actual recovery time are compared side by side. CRISAM® brings critical processes, dependencies, plans and exercises together in one model.
As of 23 September 2026
| Deviation | Process | Rating | Status |
|---|---|---|---|
| Recovery takes longer than required | Order processing | open | |
| No alternate site for manufacturing | Production | in progress | |
| No exercise since the last cycle | Data center | in progress | |
| Alerting chain documented | Crisis team | done |
ISO 22301 is the international standard for business continuity management systems. It provides a framework that organizations use to plan, establish, operate, monitor, review, maintain and improve a documented management system in order to protect against disruptive events, reduce their likelihood and ensure recovery. It is certifiable.
In Germany, BSI Standard 200-4 sits alongside it. It provides practical guidance for building a business continuity management system and includes a mapping to ISO 22301:2019.
From the first analysis to continual improvement. Whatever does not hold up in the exercise flows back into the strategy.
Critical business processes, resources and dependencies are recorded. Business impact analysis and risk analysis form the foundation.
The analysis leads to the recovery strategy: which process has to resume how quickly, with which resources and at which location?
Plans, procedures, responsibilities and resources are defined and made available before an emergency occurs.
The plan is put to a practical test instead of assuming it works. Emergency tests and exercises show whether the required times are achievable.
Results from exercises, audits and actual disruptions flow back in. The cycle starts again with updated assumptions.
If a process, a dependency or a service provider changes, the cycle starts again for that area. That is why keeping the analysis up to date matters more than the volume of plans.
The standard itself is not mandatory. Business continuity becomes an obligation through regulation, customer requirements and supervision.
The recovery time objective (RTO) specifies how long a process may be down. The recovery point objective (RPO) specifies how much data may be lost in an emergency. Both values are defined in the business impact analysis and verified in testing. What matters is the deviation between the required values and those actually achieved.
No process resumes in isolation. It depends on applications, systems, sites, people and suppliers. Only once these dependencies are recorded can you say whether a required time is achievable at all.
Only a test shows whether a plan works. Auditors, customers and supervisory authorities expect tests, exercises and improvement measures to be documented in a traceable way.
Eight building blocks that build on one another. Without analysis there is no strategy, without exercises no evidence.
| Building block | Basis | What is required | How you map it in CRISAM® |
|---|---|---|---|
| Context and scope | ISO 22301 | Define which sites, organizational units and processes the management system covers, and determine the expectations of interested parties | Critical business processes, resources and dependencies are recorded centrally and linked to one another. |
| Leadership and policy | ISO 22301 | Top management is accountable for the BCMS, sets the policy and provides resources and responsibilities | Structures, responsibilities and workflows are clearly defined. KPI-based dashboards give management the basis for decisions. |
| Business impact analysis | ISO 22301, BSI 200-4 | Determine for each process what the consequences of an outage are, at what point they become unacceptable and which resources are needed for recovery | Business impact analyses and risk analyses form the foundation for reliable recovery strategies. Dependencies are linked directly to the respective process. |
| Risk assessment | ISO 22301, BSI 200-4 | Assess threats and vulnerabilities that can lead to a disruption, and define the treatment | Risks, controls, measures and tests are managed together instead of being kept in separate repositories. |
| Recovery strategy with RTO and RPO | ISO 22301, BSI 200-4 | Define how quickly each time-critical process has to resume and how much data loss is acceptable, and provide the resources for it | Identify, assess and treat deviations between required and actual recovery times in a structured and traceable way. |
| Plans and procedures | ISO 22301, BSI 200-4 | Documented procedures for alerting, crisis communication, emergency operation and recovery, with named owners | Predefined content, control objectives and assessment criteria for establishing and operating a BCMS are available, complemented by practical checklists and question sets. |
| Testing and exercises | ISO 22301, BSI 200-4 | Exercise the plans at planned intervals, evaluate the results and turn deviations into measures | CRISAM® supports audits, emergency tests and exercises and makes it easier to provide audit-proof evidence to auditors, customers and other stakeholders. |
| Evaluation, audit and improvement | ISO 22301 | Measure effectiveness, conduct internal audits, have management review the system and improve it continually | Standardized management and audit reports and traceable documentation of tests, exercises and improvement measures provide transparency on maturity, status and deviations at all times. |
From the critical process to evidence for the audit.
Each process is assigned its dependencies: applications, systems, sites, people, suppliers. Without them, no recovery time can be assessed.
A process does not resume on its own. Only the chain of applications, systems, sites and suppliers shows what is achievable.
RTO and RPO belong togetherThe recovery time objective says how long it may take. The recovery point objective says how much work may be lost.
The justification counts in the auditWhy a process is considered time-critical must be traceable, not just the rating itself.
The business impact analysis shows at what point an outage becomes critical, per process and time window rather than as an overall estimate.
| Process | 1 hour | 4 hours | 1 day | 3 days | 1 week | RTO |
|---|---|---|---|---|---|---|
| Order processing | 4 h | |||||
| Production, South site | 24 h | |||||
| Customer service | 24 h | |||||
| Payroll | 1 week | |||||
| Marketing and communications | 2 weeks |
What is required and what is achieved today sit directly side by side. The measures address the deviation between them.
| Process | RTO required | RTO actual | RPO required | Cause | Rating |
|---|---|---|---|---|---|
| Order processing | 4 h | 11 h | 1 h | No fallback system for the ERP | |
| Production, South site | 24 h | 72 h | 4 h | No alternate site | |
| Data center | 2 h | 5 h | 1 h | Recovery not exercised | |
| Customer service | 24 h | 26 h | 8 h | Telephony depends on a single provider | |
| Payroll | 1 week | 3 days | 1 day | no deviation |
Every deviation results in a measure with an owner and a due date. Progress flows back into the same analysis the deviation came from.
Only the evaluation turns an exercise into evidence. Scope, participants, result and the derived measures are documented directly on the plan that was tested.
| Exercise | Type | Scope | Objective | Result | Measures |
|---|---|---|---|---|---|
| ERP outage | Plan review | Sales, IT | RTO 4 h | 3 | |
| Data center recovery | Technical test | IT operations | RTO 2 h | 2 | |
| Crisis team alerting | Unannounced | Management | 30 minutes | 1 | |
| Telephony outage | Plan review | Customer service | RTO 24 h | 2 | |
| Evacuation of South site | Full-scale exercise | All | Completeness | 1 | |
| Freight carrier outage | Plan review | Logistics, Purchasing | RTO 24 h | 2 |
| Exercise | Open item | Owner |
|---|---|---|
| ERP outage | No fallback system, target time not achievable | IT operations |
| Freight carrier outage | Replacement service provider not under contract | Purchasing |
The final step is the report that sets maturity, deviations and exercised plans side by side. The same basis serves the audit, the customer inquiry and the meeting with the supervisory authority.
| Evidence | Content | As of | Owner | Status |
|---|---|---|---|---|
| Business continuity policy | Approval by management | 16.02.2026 | Management | |
| Business impact analysis | 64 processes, 17 time-critical | 03.09.2026 | BCM | |
| Recovery strategy | Per time-critical process | under revision | BCM | |
| Emergency operation and recovery plans | 12 of 17 processes | 12.08.2026 | Business units | |
| Exercise records | 11 tests and exercises | 15.09.2026 | BCM | |
| Management review | Review of the BCMS | planned 02/2027 | Management |
Policy, resources, decisions in an emergency, management review.
Business impact analysis, strategy, plans, exercise planning and evaluation.
System recovery, technical tests, fallback solutions.
Emergency operating procedures, dependencies, suppliers' ability to recover.
CRISAM® does not treat business continuity in isolation, but as part of an integrated management system. Risks, controls, measures and tests are managed together.
CRISAM® supports both standards and provides practical checklists and question sets.
Control objectives and assessment criteria for establishing and operating a BCMS are included, complemented by regular content updates.
Integration with adjacent management systems such as ISMS, risk management or ICS creates one shared model instead of three repositories. How CRISAM® maps BCM is described under Business Continuity Management.
Both describe a business continuity management system, but with different aims. ISO 22301 is an international standard and certifiable. BSI Standard 200-4 provides practical guidance for building and establishing a BCMS in your own institution, and provides a mapping to ISO 22301:2019 to demonstrate compatibility. So the two standards are not mutually exclusive.
| Criterion | ISO 22301 | BSI Standard 200-4 |
|---|---|---|
| Publisher | International Organization for Standardization | German Federal Office for Information Security (BSI) |
| Edition | ISO 22301:2019, second edition, October 2019 | Modernized version, available as a document from the BSI |
| Nature | Requirements standard, certifiable | Guidance with a staged model, not certifiable on its own |
| Entry point | The complete management system from the start | Three stages: Reactive BCMS, Developing BCMS and Standard BCMS |
| Relationship to each other | The international point of reference | The requirements catalog includes a mapping to ISO 22301:2019 |
| Typical driver | Customers, tenders, international group requirements | Public-sector clients, public administration, proximity to IT-Grundschutz |
| Mapping in CRISAM® | BCMS Knowledge Pack with control objectives and assessment criteria | The same content, additionally mapped to the BSI standard |
If you come from IT-Grundschutz, you will find the familiar structure in BSI Standard 200-4 and can get started via the stages. If you need to provide evidence internationally, you need certification to ISO 22301. In both cases, business impact analysis, dependencies and exercises stay the same. An overview of all frameworks covered by CRISAM® is available under Standards and frameworks.
The first step depends on where you stand today.
Then you start with the business impact analysis. Only once critical processes, resources and dependencies are recorded can you say whether the existing plans match the required times.
Then the comparison takes center stage. Required and actual recovery times sit side by side, the deviation is assessed and turned into measures.
Then you add business continuity without introducing a second system. Processes, assets and risks are already modeled, and the BCM view builds on them.
For this you need the CRISAM® GRC Platform, the CRISAM® BCMS Module and the BCMS Knowledge Pack. In the demo, we discuss your starting point and show which of these you already have in place.
ISO 22301 is the international standard for business continuity management systems. It provides a framework that organizations use to plan, establish, operate, monitor, review, maintain and improve a documented management system in order to protect against disruptive events, reduce their likelihood and ensure recovery. It is certifiable.
The current edition is ISO 22301:2019, the second edition, published in October 2019. In Germany, BSI Standard 200-4 sits alongside it and provides practical guidance for building a business continuity management system.
Both describe a business continuity management system, but with different aims. ISO 22301 is an international standard and certifiable. BSI Standard 200-4 provides practical guidance for building and establishing a BCMS in your own institution, and provides a mapping to ISO 22301:2019 to demonstrate compatibility. So the two standards are not mutually exclusive.
The business impact analysis determines for each process what the consequences of an outage are, at what point these consequences become unacceptable and which resources are needed for recovery. It is the basis for the recovery strategy. In CRISAM®, critical business processes, resources and dependencies are recorded centrally, and business impact analyses and risk analyses form the foundation for reliable recovery strategies.
The recovery time objective (RTO) specifies how long a process may be down. The recovery point objective (RPO) specifies how much data may be lost in an emergency. Both values are defined in the business impact analysis and verified in testing. What matters is the deviation between the required values and those actually achieved.
NIS2 names business continuity and backup management as one of the state-of-the-art areas of measures. DORA requires financial entities to test their digital operational resilience regularly. In addition, there are requirements from customer contracts and from supervisory authorities. ISO 22301 itself is voluntary, but is frequently required as evidence.
What matters is whether analysis, plans, exercises and evidence are linked in one shared model. CRISAM® records critical processes, resources and dependencies centrally, provides predefined content, control objectives and assessment criteria, supports relevant standards such as ISO 22301 and BSI 200-4 and delivers standardized reports as well as KPI-based dashboards on maturity, status and deviations.
By documenting scope, participants, target time, result and the measures derived from them. CRISAM® supports audits, emergency tests and exercises and makes it easier to provide audit-proof evidence to auditors, customers and other stakeholders. An exercise without evaluation is not evidence.
The information on the standard and the BSI standard on this page comes from the following sources.
The information reflects the status of the sources cited as of the review date stated above.
In the demo, we walk through your case: critical processes, business impact analysis, the deviation between required and actual recovery times, and the final report.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information