3.7.1 Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data
Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data.
5
artefacts
1
held by a system
1
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
- HSM key generation logs · Key management / PKI
periodic reviewEvidence produced at each review
- Sample generation evidence · Document repository
governing documentDocuments that govern the control
- Documented key generation procedure · Policy repository / GRC workspace
- Entropy source documentation · Document repository
- Key strength approval · Document repository
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
- Keys generated on commodity hosts
- Insufficient entropy
- No procedure document
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.6.1.4 Cryptographic keys stored in fewest possible locations · 3.7.2 Secure key distribution