DP-7 Use a secure certificate management process
Document and implement an enterprise certificate management standard covering the certificate lifecycle and certificate policies, so certificates used by critical services are tracked and renewed.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DP-7. 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
- Certificate inventory with expiry dates and owners · Key management / PKI
- Automated renewal configuration or renewal calendar · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Record of expiry-driven outages and their remediation · Document repository
governing documentDocuments that govern the control
- Certificate management standard and certificate policy · Policy repository / GRC workspace
First move
Common gaps auditors find
- certificates tracked in a spreadsheet that drifts
- renewal handled reactively after an outage
- self-signed certificates in production with no policy exception
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-6 Use a secure key management process · DP-8 Ensure security of key and certificate repository