CEK-18 Key Archival
Hold archived keys in a secure repository that grants access on a least privilege basis.
4
artefacts
2
held by a system
0
at each review
easy
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- The archive repository and its security configuration · Source control / CI pipeline
- Access logs for the archive · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Access control list for the archive with justification per holder · Policy repository / GRC workspace
- Procedure covering when and how a key is retrieved from archive · Policy repository / GRC workspace
First move
Automate the pull from your Source control / CI pipeline. Pull-request approvals, pipeline test results and deployment records from source control, per release.
Common gaps auditors find
- Archive access granted to the whole cryptography team by default
- Archive held in general file storage rather than a controlled repository
- No access logging, so retrieval cannot be reviewed
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