CEK-14 Key Destruction
Destroy keys held outside a secure environment and revoke keys held in hardware security modules once they are no longer needed, through a defined and evaluated process.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Data governance / DLP tooling
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
- Destruction records with method, date and witness · Data governance / DLP tooling
- HSM revocation records · Key management / PKI
- Evidence of periodic review identifying keys no longer needed · Data governance / DLP tooling
governing documentDocuments that govern the control
- The key destruction and revocation procedure distinguishing HSM-held from externally held keys · 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 marked obsolete but never actually destroyed
- Destruction unwitnessed and unrecorded
- Copies of keys in backups outlive the destruction event
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 sheet