3.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.
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 neces
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Tabletop after action reports · Document repository
governing documentDocuments that govern the control
- Incident response plan · Policy repository / GRC workspace
- Playbook library · Document repository
- Examine team roster · Document repository
- Test detection to recovery flow · 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
- CUI specific incidents not exercised
- External notification timelines unclear
- Lessons learned not implemented
- Forensic capability not validated
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.5.1.3 Disk-level encryption key management · 3.6.1.1 Documented description of cryptographic architecture