DSP-04 Data Classification
Assign each dataset a classification reflecting its type and sensitivity.
4
artefacts
0
held by a system
2
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 classification drives handling, such as differing controls by level · Data governance / DLP tooling
- Review records for reclassification · Data governance / DLP tooling
governing documentDocuments that govern the control
- The classification scheme with defined levels and criteria · Policy repository / GRC workspace
- Classification values recorded against datasets · 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
- Scheme published but most data left unclassified
- Classification assigned without any control difference between levels
- Datasets classified at creation and never reassessed when their content changed
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