What evidence do auditors commonly ask for on CEK-10 Key Generation?

Key generation procedure naming the libraries, algorithm strengths and RNG used; KMS or HSM configuration for key generation; Validation certificates of the random number generator or module; Observed or logged key generation event in a test tenant.

What is the most common gap auditors find on CEK-10?

Keys generated in application code with unvetted libraries

CSA CCM v4.1 · CEK - Cryptography, Encryption & Key Management

`CEK-10` Key Generation

Cryptographic keys are generated with industry-accepted cryptographic libraries, with the strength of the algorithm and the source of random numbers stated.

Source: CSA CCM v4.1, CEK-10. 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.

artefacts

held by a system

at each review

easy

to go live

Key management / PKI

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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 or HSM configuration for key generation · Key management / PKI
Observed or logged key generation event in a test tenant · Document repository

periodic reviewEvidence produced at each review

Validation certificates of the random number generator or module · Backup / DR tooling

governing documentDocuments that govern the control

Key generation procedure naming the libraries, algorithm strengths and RNG used · Policy repository / GRC workspace

First move

Automate the pull from your Key management / PKI. Key inventory, rotation dates and certificate expiry from the KMS or PKI.

Common gaps auditors find

Keys generated in application code with unvetted libraries
RNG source not documented
Key strength below the approved list

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

CEK-09 Encryption and Key Management Audit · CEK-11 Key Purpose