6.5.2 Information classification
The information classification scheme must explicitly account for personal data, including its type and any special categories, so the organization knows what it processes, where it is stored and which systems it flows t
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
- Labelling guidance and evidence staff were told how to recognise personal data · Data governance / DLP tooling
- Awareness or competence records for the recognition training · HR system / LMS
governing documentDocuments that govern the control
- Classification scheme with personal data and special categories named as classes · Policy repository / GRC workspace
- Data map or flow documentation showing where each class is stored and how it moves · 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 scheme with confidential as its only relevant tier, which cannot distinguish personal data from commercial secrets
- Special categories not separated, so heightened obligations are invisible to the people handling the data
- Staff able to recite the classification labels but unable to identify personal data in front of them
- Storage and flow mapping stopping at the system boundary, missing exports and reports
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