CEK-20 Key Recovery
Processes, procedures and technical measures are defined, implemented and evaluated to weigh the risk to operational continuity against the risk of exposure of the keying material, and of the data protected by it, if control of that material is lost, taking legal and regulatory requirements into account.
Source: CSA CCM v4.1, CEK-20. 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
- Key escrow or backup configuration · Backup / DR tooling
periodic reviewEvidence produced at each review
- Key recovery procedure and risk assessment · Policy repository / GRC workspace
- Records of recovery tests · Document repository
- Decision records weighing continuity against exposure · Document repository
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Keys unrecoverable after loss, risking data loss
- Recovery copies held with weaker protection
- Recovery never tested
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