DP-8 Ensure security of key and certificate repository
Harden the key vault service itself through access control, network restriction, logging, monitoring and backup so keys and certificates stay protected.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DP-8. 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
- Network restriction configuration on the vault · Cloud console / configuration management
- Vault backup and soft-delete or purge protection settings · Backup / DR tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Key vault access policy or role assignments with least privilege · Policy repository / GRC workspace
- Vault audit logging enabled and forwarded · Policy repository / GRC workspace
- Alerting on anomalous vault access · Policy repository / GRC workspace
First move
Common gaps auditors find
- vault reachable from any network
- broad access granted to application service principals
- vault logs not collected so key access is unauditable
- purge protection disabled allowing irreversible deletion
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-7 Use a secure certificate management process · DS-1 Conduct threat modeling