# BSI C5 BCM-02 — Business impact analysis policies and instructions

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_bcm02_6f977e2ef4-bsi-c5-bcm-02-business-impact-analysis-policies-and-instructions
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Business Continuity Management](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_businesscontinuitymanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control BCM-02 · Priority: high · Component: Business Continuity Management

### What this control covers

Documents impact analysis policies per SP-01, identifying critical services, threats, and RTO/RPO targets based on risk analysis. Ensures planning for disruptions, protecting cloud customer data availability and service continuity effectively.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Business impact analysis policies and instructions.

### Quick checklist

-   Risk — Cloud Customer Data / Business Continuity
-   Data — Cloud Customer Data / Business Continuity
-   Policy — Cloud Customer Data / Business Continuity
-   Business — Cloud Customer Data / Business Continuity

### Related articles on this site

-   [Ensure locked immutability policies are used for containers storing business-critical blob data](https://support.icompaas.com/support/solutions/articles/62000234816-ensure-locked-immutability-policies-are-used-for-containers-storing-business-critical-blob-data)
-   [Ensure storage for critical data are encrypted with Customer Managed Key](https://support.icompaas.com/support/solutions/articles/62000219790-ensure-storage-for-critical-data-are-encrypted-with-customer-managed-key)
-   [Ensure Critical Data is Encrypted with Customer Managed Keys (CMK)](https://support.icompaas.com/support/solutions/articles/62000233913-ensure-critical-data-is-encrypted-with-customer-managed-keys-cmk-)
-   [Microsoft Cloud Security Posture Management (CSPM)](https://support.icompaas.com/support/solutions/articles/62000234105-microsoft-cloud-security-posture-management-cspm-)

## 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): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.