What this policy is
Specifies what data is backed up, how often, how long backups are retained, where they live (geographically and physically), and how frequently restore drills are performed.
Why every organization needs one
An untested backup is a hope, not a control. The policy is what forces the organization to actually exercise the restore path before they need it.
What a competent Backup And Recovery Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Data-set inventory and RPO/RTO per set
- Backup frequency, retention, and location (3-2-1 rule)
- Encryption of backups at rest
- Restore-drill schedule and acceptance criteria
- 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_backup_and_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 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.33 | Protection of records | Organizational controls |
| ISO/IEC 27001:2022 | A.8.13 | Information backup | Technological controls |
| ISO/IEC 27701:2025 | A.3.14 | Protection of records | Security considerations |
| ISO/IEC 27701:2025 | A.3.24 | Information backup | Security considerations |
4 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents 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.