CEK-08 Service Customer Key Management Capability
A service provider gives its service customers the ability to control and administer the keys that encrypt their data.
Source: CSA CCM v4.1, CEK-08. 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 configuration showing customer key ownership and control · Key management / PKI
- HSM validation certificates · Key management / PKI
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Product documentation of customer-managed or bring-your-own key options · Document repository
- Customer guidance on key management responsibilities · Policy repository / GRC workspace
First move
Common gaps auditors find
- Customer-managed keys offered for some services only
- Provider retains unrestricted access to customer keys
- Shared responsibility for keys not documented for customers
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-07 Encryption Risk Management · CEK-09 Encryption and Key Management Audit