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