CEK-01 Encryption and Key Management Policy and Procedures
Keep approved cryptography, encryption and key management policies and procedures, communicate them to the teams that operate cryptography, and review them at least annually.
4
artefacts
0
held by a system
2
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 record · Document repository
- Evidence of communication to engineering and operations teams · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The approved cryptography and key management policy with approver and date · Policy repository / GRC workspace
- The approved algorithm and key length standard the policy references · 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
- Policy naming algorithms that are now deprecated
- Annual review missed
- Key management procedures held by one engineer and not documented
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 sheetCCC-09 Change Restoration · CEK-02 CEK Roles and Responsibilities