3.7.4 Cryptoperiod and key changes
Key management policies and procedures address cryptographic key changes for keys that have reached the end of their cryptoperiod.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Rotation log with dates · SIEM / log platform
- Automated rotation configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Re-encryption evidence · Document repository
governing documentDocuments that govern the control
- Cryptoperiod documented per key · Document repository
- Post-rotation validation · Document repository
First move
Start with the 2 of 5 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- No cryptoperiod defined
- Keys never rotated
- Rotation evidence missing
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.3 Secure key storage · 3.7.5 Retirement or replacement of keys