What this control covers
The entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and monitors environmental protections, software, data backup processes, and recovery infrastructure to meet its objectives.
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
Use Backup and DR Service for VM/DB and managed snapshot policies for disks; replicate critical GCS to a different region + project under separate IAM.
Google Workspace
Google Vault retention rules cover Gmail/Drive/Chat; combine with periodic third-party backups (e.g., Spanning, Backupify) for full restore-by-user.
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: Management of Backup, Recovery, and Environmental Controls (Original component: Availability).
Quick checklist
- Risk — Objectives / Controls
- Business — Objectives / Controls
- Management — Objectives / Controls
- Data — Objectives / Controls
Related articles on this site
- Ensure Backup Data in Recovery Services Vaults Is Encrypted Using Customer-Managed Keys (CMK)
- NIST 800-171 3.4.8 Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.
- NIST 800-171 3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
- CMMC 2.0 CM.3.069 Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.