EvidenceSheet

5.10 Acceptable use of information and other associated assets

Requires rules for acceptable use, and procedures for handling information and its associated assets, to be identified, documented and put into effect.

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

  • Records of monitoring or exception handling where the rules were breached · SIEM / log platform

periodic reviewEvidence produced at each review

  • Evidence rules were communicated and accepted by personnel and by third parties given access · Vendor register / contract repository

governing documentDocuments that govern the control

  • The acceptable use rules, covering personal use, removable media, cloud storage, email, messaging and use of artificial intelligence services where relevant · Policy repository / GRC workspace
  • Handling procedures per classification level, covering storage, transmission, printing, sharing and destruction · Policy repository / GRC workspace
  • Technical enforcement evidence where the rules are enforced by tooling, such as removable media policy or upload restriction · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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.9 Inventory of information and other associated assets · 5.11 Return of assets