EvidenceSheet

5.13 Labelling of information

Requires a matching set of information labelling procedures to be developed and implemented, so that information carries markings consistent with the classification scheme the organisation has adopted.

5
artefacts
1
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

  • Technical labelling configuration where automated, such as document classification tooling, and its rule set · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Evidence labelling extends to information shared with third parties · Vendor register / contract repository
  • Awareness and training evidence showing personnel know how to label · HR system / LMS

governing documentDocuments that govern the control

  • The labelling procedures showing how labels are applied for each medium, covering documents, email, physical media, screens and system records · Policy repository / GRC workspace
  • Samples of labelled information from live systems, in each classification level in use · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

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

5.12 Classification of information · 5.14 Information transfer