3.6.1.4 Cryptographic keys stored in fewest possible locations
Cryptographic keys are stored in the fewest possible locations.
5
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- HSM consolidation evidence · Key management / PKI
- Annual review · Document repository
governing documentDocuments that govern the control
- Key storage location inventory · Policy repository / GRC workspace
- Architecture diagram · Policy repository / GRC workspace
- Justification for each location · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Keys copied across hosts
- No inventory
- Legacy copies not retired
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.3 Access to cryptographic keys restricted · 3.7.1 Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data