3.6.1.3 Access to cryptographic keys restricted
Access to cleartext cryptographic key components is restricted to the fewest custodians necessary.
5
artefacts
1
held by a system
1
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
- Logs of key access events · SIEM / log platform
periodic reviewEvidence produced at each review
- Quarterly access review · Identity provider / directory
governing documentDocuments that govern the control
- Approved custodian register · Policy repository / GRC workspace
- Access control on KMS or HSM · Policy repository / GRC workspace
- Job description references · 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
- Shared admin accounts with key access
- No access logging
- No review cadence
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.2 Secret and private keys restricted to fewest custodians · 3.6.1.4 Cryptographic keys stored in fewest possible locations