SEC07-BP03 Automate identification and classification
Use Macie, Glue, Comprehend and lifecycle automation to continuously discover and classify data without relying on manual surveys.
Source: AWS Well-Architected Security Pillar, SEC07-BP03. 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 AWS Well-Architected Security Pillar in the compliance library.
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
- Discovery coverage metrics · Data governance / DLP tooling
periodic reviewEvidence produced at each review
- Macie job schedule and findings · Data governance / DLP tooling
governing documentDocuments that govern the control
- Automated tagging Lambda · Policy repository / GRC workspace
First move
Common gaps auditors find
- Macie disabled or unfunded
- manual annual classification only
- new data stores undiscovered
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 sheetSEC07-BP02 Apply data protection controls based on data sensitivity · SEC07-BP04 Define scalable data lifecycle management