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.
4
artefacts
1
held by a system
1
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
- 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
- Certificate inventory with expiry dates and owners · Policy repository / GRC workspace
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
- 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