TMA-COCKROACHDB-5.2
Periodically Test Backup Recovery Procedures
Description
Self-hosted CockroachDB deployments must regularly test backup recovery procedures to ensure that backups can be successfully restored, data integrity is preserved, and security controls remain effective during restoration. CockroachDB provides multiple backup and restore features, including full and incremental backups, encrypted backups, and backup validation tools.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
Confirm documented restore procedures exist (backup locations, RESTORE of cluster/database/table into a non-production recovery cluster, decryption with the passphrase/KMS key). Review restore-test records: tests must run on a regular schedule and after changes to backup configuration, encryption, KMS keys, IAM or major upgrades, with data validation and measured RTO/RPO.
How it is fixed
Fix method: Guidance or infrastructure patch
1. Define a restore testing schedule Establish a policy requiring restore or backup validation testing at a regular cadence and after key changes, such as: - Changes to backup configuration or destinations. - Changes to backup encryption (for example, enabling encrypted backups or changing KMS configuration). - KMS key rotation or changes to encryption keys. - IAM or credential changes affecting access to backup storage or KMS.
Properties
- Operating systems
- Any
- Tags
- cockroachdbbackup
- Reference
- CIS CockroachDB v25.x Benchmark v1.0.0 - 5.2 Periodically Test Backup Recovery Procedures