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.
5
artefacts
2
held by a system
0
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
- Network restriction configuration on the vault · Cloud console / configuration management
- Vault audit logging enabled and forwarded · SIEM / log platform
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 backup and soft-delete or purge protection settings · Policy repository / GRC workspace
- Alerting on anomalous vault access · Policy repository / GRC workspace
First move
Start with the 2 of 5 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
- 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