CEK-09 Encryption and Key Management Audit
Subject the key management platform, together with its governing policy and process, to audit at a frequency proportionate to its risk exposure, no less than yearly and again after any security event.
4
artefacts
0
held by a system
2
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
- Audit reports covering key management systems from the last twelve months · Key management / PKI
- Evidence of an audit triggered by a security event · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The frequency decision and the risk exposure it was based on · Policy repository / GRC workspace
- Findings and their remediation · 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
- Annual audit scoped to policy documents without examining the key management system itself
- No audit after a security event that touched cryptographic material
- Frequency set by convenience rather than risk
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 sheetCEK-08 CSC Key Management Capability · CEK-10 Key Generation