CEK-11 Key Purpose
Provision each secret and private key for a single defined purpose and manage it accordingly.
4
artefacts
0
held by a system
3
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 keys are not reused across purposes or environments · Cloud console / configuration management
- Provisioning records tying a key to its purpose at creation · Identity provider / directory
- Detection or review that catches purpose reuse · Document repository
governing documentDocuments that govern the control
- Key inventory showing the declared purpose of each key · 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
- One key shared across signing and encryption
- Production and non-production sharing keys
- Purpose recorded at creation but never checked afterwards
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 sheet