SC.L2-3.13.10 Key Management
Establish and manage the cryptographic keys used by cryptography employed in organizational systems, across their life cycle.
3
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
- Evidence of key rotation and secure storage · Key management / PKI
governing documentDocuments that govern the control
- Key management procedure covering generation, distribution, storage, rotation and destruction · Policy repository / GRC workspace
- Key inventory and custodian assignments · 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
- Keys generated and then never rotated or inventoried
- Private keys stored alongside the data they protect
- Key custodianship undefined so departures leave keys orphaned
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 sheetSC.L2-3.13.9 Connections Termination · SC.L2-3.13.11 CUI Encryption