A.5.12 Classification of information
Classify information by confidentiality, integrity, availability and interested-party requirements.
15
artefacts
0
held by a system
5
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
- Risk assessment report that maps classification levels to impact criteria · Data governance / DLP tooling
- Sample classification decision records for high‑risk assets · Data governance / DLP tooling
- Configuration screenshots of automated labeling tool · Cloud console / configuration management
- Quarterly review report verifying classification accuracy against current business needs · Data governance / DLP tooling
- Attendance logs for information classification awareness sessions · SIEM / log platform
governing documentDocuments that govern the control
- Information Classification Policy document · Policy repository / GRC workspace
- Policy approval meeting minutes · Policy repository / GRC workspace
- Version control change log for the policy · Policy repository / GRC workspace
- Classification matrix linking confidentiality, integrity, and availability levels to data types · Policy repository / GRC workspace
- Labeling standards handbook describing visual tags and naming conventions · Policy repository / GRC workspace
- Examples of labeled documents (e.g., confidential, internal, public) · Policy repository / GRC workspace
- Asset inventory spreadsheet with a classification column for each record · Policy repository / GRC workspace
- Data flow diagram annotated with classification levels for data stores and flows · Policy repository / GRC workspace
- Training slide deck covering classification criteria and labeling procedures · HR system / LMS
- Signed employee acknowledgment forms confirming understanding of classification policy · HR system / LMS
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 levels not aligned with business impact
- Inconsistent labeling across departments
- Missing periodic review of classifications
- Unclear ownership for classification decisions
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