What evidence do auditors commonly ask for on SEC07-BP02 Apply data protection controls based on data sensitivity?

Per-class handling guidance naming approved services and configurations; Policy-as-code or guardrails enforcing the per-class configuration; Exception register for data held outside approved locations; Evidence of periodic checks that controls match classification.

What is the most common gap auditors find on SEC07-BP02?

single protection level applied to all data regardless of sensitivity

AWS Well-Architected Security Pillar · Data Protection

`SEC07-BP02` Apply data protection controls based on data sensitivity

Apply protection controls proportionate to each defined sensitivity level, with published guidance on approved storage services, locations and required configuration per class.

Source: AWS Well-Architected Security Pillar, SEC07-BP02. 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.

artefacts

held by a system

at each review

easy

to go live

Cloud console / configuration management

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Per-class handling guidance naming approved services and configurations · Cloud console / configuration management
Policy-as-code or guardrails enforcing the per-class configuration · Cloud console / configuration management

periodic reviewEvidence produced at each review

Evidence of periodic checks that controls match classification · Data governance / DLP tooling

governing documentDocuments that govern the control

Exception register for data held outside approved locations · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

single protection level applied to all data regardless of sensitivity
guidance published but not enforced by any guardrail
sensitive data found in stores approved only for lower classes

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

SEC07-BP01 Understand your data classification scheme · SEC07-BP03 Automate identification and classification