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.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DP-4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Encryption configuration inventory · Policy repository / GRC workspace
- Key Vault key inventory · Policy repository / GRC workspace
- CMK rotation schedule · Document repository
- Disk encryption status · Document repository
First move
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