# Business Continuity And Disaster Recovery Policy

- Source: https://support.icompaas.com/compliance/policy-docs/business-continuity-and-disaster-recovery-policy
- Section: [Compliance](https://support.icompaas.com/compliance) › [Policy Documents](https://support.icompaas.com/compliance/policy-docs) › All policy documents
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Policy Document**·4 mapped controls

## What this policy is

Sets the framework for keeping critical business processes operating during disruption (BC) and restoring IT services after major incidents (DR). The umbrella policy that BC plans, DR plans, and crisis-management runbooks all derive from.

## Why every organization needs one

Regulators, large customers, and cyber insurers all require evidence that the organization can withstand and recover from disruption. The policy is the first artefact they ask for.

## What a competent Business Continuity And Disaster Recovery Policy typically contains

-   Purpose and scope
-   Roles and responsibilities
-   Definitions
-   Business-impact analysis methodology
-   Critical-process inventory + tolerable outage targets
-   Plan ownership and test cadence
-   Crisis-communication chain
-   Review cadence (typically annual) and version control
-   Approval, sign-off and effective date

## How iCompaas tracks this policy

The icompaas policy-doc producer manages this document through an 8-state lifecycle: `draft` → `generated` → `internal_qa` → `customer_review` → `in_review` → `approved` → `signed` (with `rejected` as a terminal side-state). The producer publishes a `policy_doc_business_continuity_and_disaster_recovery_policy_signed` compliance finding once at least one document of this kind reaches the `signed` state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).

## Compliance frameworks that reference this policy

The icompaas [compliance controls library](https://support.icompaas.com/compliance) links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.

| Framework | Control | Title | Component |
| --- | --- | --- | --- |
| ISO/IEC 27001:2022 | [A.5.29](https://support.icompaas.com/compliance/iso-27001-2022/a-5-29-information-security-during-disruption) | [Information security during disruption](https://support.icompaas.com/compliance/iso-27001-2022/a-5-29-information-security-during-disruption) | Organizational controls |
| ISO/IEC 27001:2022 | [A.5.30](https://support.icompaas.com/compliance/iso-27001-2022/a-5-30-ict-readiness-for-business-continuity) | [ICT readiness for business continuity](https://support.icompaas.com/compliance/iso-27001-2022/a-5-30-ict-readiness-for-business-continuity) | Organizational controls |
| ISO/IEC 27001:2022 | [A.7.5](https://support.icompaas.com/compliance/iso-27001-2022/a-7-5-protecting-against-physical-and-environmental-threats) | [Protecting against physical and environmental threats](https://support.icompaas.com/compliance/iso-27001-2022/a-7-5-protecting-against-physical-and-environmental-threats) | Physical controls |
| ISO/IEC 27001:2022 | [A.7.11](https://support.icompaas.com/compliance/iso-27001-2022/a-7-11-supporting-utilities) | [Supporting utilities](https://support.icompaas.com/compliance/iso-27001-2022/a-7-11-supporting-utilities) | Physical controls |

4 controls across 1 framework reference this policy.

## About this page

This article is part of the iCompaas [Policy Documents](https://support.icompaas.com/compliance/policy-docs) library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): SOC 2 auditors test that policies like this one exist, are approved, and are reviewed on schedule; the guide lists the full set.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 clause 5.2 and Annex A.5.1 require a documented, approved policy set; the guide shows how it fits the ISMS.