EvidenceSheet

5.9 Inventory of information and other associated assets

Requires an inventory of information and of the other assets associated with it to be developed and kept current, and requires that inventory to record ownership of each entry.

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

none for this control

periodic reviewEvidence produced at each review

  • The recorded owner for each entry, and evidence owners have accepted the role · Identity provider / directory

governing documentDocuments that govern the control

  • The inventory of information and associated assets, showing scope across hardware, software, services, information stores and cloud tenancies · Policy repository / GRC workspace
  • The process and cadence for keeping the inventory current, including additions and retirements · Policy repository / GRC workspace
  • Reconciliation evidence between the inventory and an independent source such as network discovery, endpoint management or the finance asset register · Policy repository / GRC workspace
  • Evidence that information assets, not only equipment, are inventoried, including data sets and repositories · 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

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.8 Information security in project management · 5.10 Acceptable use of information and other associated assets