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.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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 of periodic checks that controls match classification · Data governance / DLP tooling
governing documentDocuments that govern the control
- Per-class handling guidance naming approved services and configurations · Document repository
- Policy-as-code or guardrails enforcing the per-class configuration · Policy repository / GRC workspace
- Exception register for data held outside approved locations · Policy repository / GRC workspace
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
- 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 sheetSEC07-BP01 Understand your data classification scheme · SEC07-BP03 Automate identification and classification