CEK-17 Key Deactivation
Deactivate each key at its expiry date through a defined and evaluated process rather than leaving expired keys usable.
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
- Deactivation records for keys that have passed expiry · Document repository
- Evidence an expired key is technically unusable · Document repository
governing documentDocuments that govern the control
- The deactivation procedure and its trigger on expiry date · Policy repository / GRC workspace
- Key inventory showing expiry dates and current state · 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
- Expiry dates recorded but nothing acts on them
- Expired keys still accepted by systems for compatibility
- Deactivation done manually and inconsistently across key stores
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