3.7.5 Retirement or replacement of keys
Key management policies and procedures address retirement, replacement, or destruction of keys when integrity has been weakened or keys are suspected of compromise.
5
artefacts
1
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Destruction logs from HSM · Key management / PKI
periodic reviewEvidence produced at each review
- Replacement evidence · Document repository
- Compromise event response records · Document repository
- Custodian sign-off · Document repository
governing documentDocuments that govern the control
- Retirement procedure document · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Key management / PKI on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Retired keys not destroyed
- No procedure for compromise
- Old keys still accepted
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 sheet3.7.4 Cryptoperiod and key changes · 3.7.6 Manual cleartext key operations use split knowledge