SEC08-BP01 Implement secure key management
Centralise key management in AWS KMS or CloudHSM, define key hierarchies, use customer managed keys for sensitive data and rotate keys on policy.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Key management / PKI
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- CloudHSM cluster configuration · Key management / PKI
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- KMS key inventory with rotation status · Policy repository / GRC workspace
- Key policies · Policy repository / GRC workspace
- Key owner mapping · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Key management / PKI); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- AWS managed keys only for sensitive data
- no rotation
- broad kms:* in key policies
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 sheetSEC07-BP04 Define scalable data lifecycle management · SEC08-BP02 Enforce encryption at rest