EvidenceSheet

5.11 Return of assets

Requires personnel and other relevant interested parties to return all organisational assets in their possession when employment, a contract or an agreement changes or ends.

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

  • The checklist or ticket used per departure, listing assets issued to that person from the inventory · Ticketing / ITSM

periodic reviewEvidence produced at each review

  • Signed confirmation of return, and records for assets not returned including the escalation taken · Document repository

governing documentDocuments that govern the control

  • The leaver and role change procedure showing asset return as a mandatory step · Policy repository / GRC workspace
  • Evidence covering information as well as equipment, such as return or deletion of documents held locally and on personal devices · Policy repository / GRC workspace
  • Reconciliation between assets issued in the inventory and assets recovered · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM 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.10 Acceptable use of information and other associated assets · 5.12 Classification of information