SEC07-BP01 Understand your data classification scheme
Understand and document the classification scheme that applies to the data the workload processes, including handling requirements, storage locations, owners and the legal obligations attached to each 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 the scheme is communicated to builders · Data governance / DLP tooling
governing documentDocuments that govern the control
- Data classification policy with defined sensitivity levels · Policy repository / GRC workspace
- Data inventory for the workload mapped to classes, locations and owners · Policy repository / GRC workspace
- Legal and regulatory obligations mapped to each class · 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
- classification policy exists but no workload data is mapped to it
- no named data owner so handling decisions stall
- classification levels defined with no handling rules attached
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 sheetSEC06-BP05 Automate compute protection · SEC07-BP02 Apply data protection controls based on data sensitivity