DP-6 Use a secure key management process
Document and implement an enterprise cryptographic key management standard covering the key lifecycle, with keys generated, distributed and stored in a secured key vault service and rotated on a defined schedule.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Rotation records and evidence of retiring superseded keys · Key management / PKI
governing documentDocuments that govern the control
- Cryptographic key management standard · Policy repository / GRC workspace
- Key inventory with owner, algorithm, purpose and expiry · Policy repository / GRC workspace
- Key vault configuration and access policy · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- keys held in application configuration rather than a vault
- no rotation schedule so keys live indefinitely
- key inventory incomplete so orphan keys persist
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-5 Use customer-managed key option in data at rest encryption when required · DP-7 Use a secure certificate management process