CEK-03 Data Encryption
Apply cryptographic protection to stored data and to data moving across networks, using libraries that hold certification against an approved standard.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration evidence showing encryption enabled at rest and in transit per system · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- The certification of the cryptographic libraries or modules in use, such as a validation certificate · Document repository
- Inventory of data stores and transport paths with their encryption status · Policy repository / GRC workspace
- Exceptions where encryption is not applied and the risk acceptance behind them · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Encryption at rest claimed from a provider default without verification per data store
- Uncertified or self-built cryptographic implementations in use
- Internal traffic left unencrypted because it is considered a trusted network
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-02 CEK Roles and Responsibilities · CEK-04 Encryption Algorithm