CEK-13 Key Revocation
Revoke and remove keys before the end of their cryptoperiod when a key is compromised or the holder leaves the organisation, through a defined and evaluated process.
4
artefacts
2
held by a system
0
at each review
easy
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Revocation records tied to compromise events and leaver events · Identity provider / directory
- Evidence revocation is linked to the joiner mover leaver process · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- The revocation procedure with trigger conditions · Policy repository / GRC workspace
- Verification that a revoked key no longer works · Document repository
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
Common gaps auditors find
- Leaver process does not trigger key revocation
- Revocation recorded but the key remains usable in some systems
- No verification step, so revocation is assumed rather than proven
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