3.7.2 Secure key distribution
Key management policies and procedures address secure distribution of cryptographic keys.
5
artefacts
1
held by a system
0
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
- Wrapped key transport logs · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Key distribution procedure · Policy repository / GRC workspace
- Out-of-band channel documentation · Document repository
- Custodian receipts · Document repository
- Test of mechanism · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- Keys emailed in cleartext
- No wrapping
- No record of distribution
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.1 Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data · 3.7.3 Secure key storage