CEK-15 Key Activation
Processes, procedures and technical measures are defined, implemented and evaluated so that keys generated but not yet authorised for use are created in a pre-activated state, taking legal and regulatory requirements into account.
Source: CSA CCM v4.1, CEK-15. 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
- KMS key state settings for sampled keys · Key management / PKI
periodic reviewEvidence produced at each review
- Activation approval records · Document repository
governing documentDocuments that govern the control
- Key lifecycle procedure defining pre-activation and activation · Policy repository / GRC workspace
- Access permissions for key creation and activation · Policy repository / GRC workspace
First move
Common gaps auditors find
- Keys usable immediately on creation
- No approval to activate keys
- Key states not recorded
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