SEC08-BP02 Enforce encryption at rest
Ensure all data stores encrypt data at rest using KMS keys, enforce by default through account settings, SCPs and Config rules.
5
artefacts
1
held by a system
0
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
- Config rules for unencrypted resources · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- S3 default encryption settings · Document repository
- EBS encryption by default · Document repository
- RDS encryption status · Document repository
- SCP denying unencrypted creation · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- S3 buckets without encryption
- EBS volumes unencrypted
- RDS snapshots unencrypted
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 sheetSEC08-BP01 Implement secure key management · SEC08-BP03 Automate data at rest protection