DP-4 Enable data at rest encryption by default
Encrypt data at rest using platform-managed or customer-managed keys for all storage services with documented key management.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Encryption configuration inventory · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Key Vault key inventory · Policy repository / GRC workspace
- CMK rotation schedule · Document repository
- Disk encryption status · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Unmanaged disks without encryption
- Key rotation not scheduled
- Key Vault access overly permissive
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetDP-3 Encrypt sensitive data in transit · DP-5 Use customer-managed key option in data at rest encryption when required