CEK-02 CEK Roles and Responsibilities
Name who is accountable for each part of cryptography, encryption and key management, and put those responsibilities into practice.
4
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 the named holders perform the duty, such as signed key ceremony records · Identity provider / directory
governing documentDocuments that govern the control
- A responsibility matrix covering key generation, custody, rotation, revocation and destruction · Policy repository / GRC workspace
- Named individuals or roles against each responsibility · Policy repository / GRC workspace
- Backup or deputy 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
- Responsibilities assigned to a team name with no individual accountable
- Key custodian left the organisation and was never replaced
- Matrix documented but the work is actually done by someone else
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 sheetCEK-01 Encryption and Key Management Policy and Procedures · CEK-03 Data Encryption