3.6.1.1 Documented description of cryptographic architecture
A documented description of the cryptographic architecture is maintained, including algorithms, protocols, keys, key strengths, expiry dates, and locations of cryptographic devices.
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Annual review attestation · Vendor register / contract repository
governing documentDocuments that govern the control
- Cryptographic architecture document with version · Policy repository / GRC workspace
- Key inventory with strength and expiry · Policy repository / GRC workspace
- HSM and KMS inventory · Policy repository / GRC workspace
- Algorithm justification · Policy repository / GRC workspace
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
- No architecture document
- Inventory missing legacy keys
- Strength below 112 bits accepted
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 Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse that include: • Access to keys is restricted to the fewest number of custodians necessary. · 3.6.1.2 Secret and private keys restricted to fewest custodians