CEK-16 Key Suspension
Processes, procedures and technical measures are defined, implemented and evaluated so that any move of a key into or out of a suspended state is monitored, reviewed and approved, taking legal and regulatory requirements into account.
Source: CSA CCM v4.1, CEK-16. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Logs of key state transitions with approvals · SIEM / log platform
- Monitoring alerts on key state changes · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Procedure for suspending and reinstating keys · Policy repository / GRC workspace
- Access permissions for state changes · Policy repository / GRC workspace
First move
Common gaps auditors find
- State changes not approved
- No monitoring of suspended keys
- Anyone with KMS admin can suspend keys
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