3.6.1.2 Secret and private keys restricted to fewest custodians
Secret and private keys used to protect stored account data are stored in encrypted form, within a secure cryptographic device, or as key components, with access restricted to the fewest custodians necessary.
5
artefacts
3
held by a system
1
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Custodian list and access logs · SIEM / log platform
- HSM access logs · Key management / PKI
- Split knowledge configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Periodic access review · Identity provider / directory
governing documentDocuments that govern the control
- Key encryption key documentation · Policy repository / GRC workspace
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- Wide custodian access
- Keys stored without wrapping
- No access review
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.1 Documented description of cryptographic architecture · 3.6.1.3 Access to cryptographic keys restricted