CEK-04 Encryption Algorithm
Select encryption algorithms that suit the classification of the data, the risk it carries and the practical usability of the technology, rather than applying one algorithm everywhere.
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
- Evidence systems use the algorithm their data classification requires · Data governance / DLP tooling
- Review record showing the selection was revisited as cryptographic guidance changed · Document repository
governing documentDocuments that govern the control
- The approved algorithm standard mapped to data classification levels · Policy repository / GRC workspace
- The rationale recorded for each selection · 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
- A single algorithm applied to all data regardless of classification
- Legacy algorithms retained for compatibility with no documented risk acceptance
- Selection never revisited as published guidance moved on
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-03 Data Encryption · CEK-05 Encryption Change Management