DP-5 Use customer-managed key option in data at rest encryption when required
Where regulation requires it, define the use cases and service scope for customer-managed keys and implement data at rest encryption using them.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DP-5. 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
- Key vault configuration backing those keys · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Documented determination of where customer-managed keys are required and why · Document repository
- Service scope list showing which stores use customer-managed keys · Policy repository / GRC workspace
- Rotation and revocation procedure · Policy repository / GRC workspace
First move
Common gaps auditors find
- customer-managed keys applied everywhere with no rationale, adding operational risk
- requirement asserted but the store still uses platform-managed keys
- no tested procedure for key revocation
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-4 Enable data at rest encryption by default · DP-6 Use a secure key management process