CEK-10 Key Generation
Generate keys only through accepted cryptographic libraries, and record for each key the strength selected and the source of randomness it was produced from.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Key ceremony or generation records for recent keys · Document repository
- Evidence of the random number generator in use and its suitability · Backup / DR tooling
governing documentDocuments that govern the control
- Key generation procedure naming the library, algorithm strength and entropy source · Policy repository / GRC workspace
- The library version and its accepted status · Document repository
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
- Entropy source undocumented, so key quality cannot be assessed
- Keys generated on developer workstations outside the defined procedure
- Algorithm strength recorded for new keys but unknown for legacy ones
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-09 Encryption and Key Management Audit · CEK-11 Key Purpose