DCS-06 Assets Cataloguing and Tracking
Hold every relevant physical and logical asset across all provider sites in a catalogue kept inside a secured tracking system.
4
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
- Coverage evidence across all sites · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The asset catalogue and the system holding it · Policy repository / GRC workspace
- Access controls on the catalogue itself · Policy repository / GRC workspace
- Reconciliation between the catalogue and a physical or discovery check · 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
- Catalogue held in an open spreadsheet rather than a secured system
- One site maintained diligently and others omitted
- No reconciliation, so the catalogue drifts from reality
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 sheetDCS-05 Assets Classification · DCS-07 Controlled Access Points