What evidence do auditors commonly ask for on DCS-07 Assets Cataloguing and Tracking?

Configuration management database or asset register covering all sites; Access control list and audit log for the asset tracking system; Reconciliation reports between the register and discovery scans or physical counts; Records of the periodic catalogue review; Asset location history for a sample of devices moved between sites.

What is the most common gap auditors find on DCS-07?

Register held in a spreadsheet anyone can edit

CSA CCM v4.1 · DCS - Datacenter Security

`DCS-07` Assets Cataloguing and Tracking

Every relevant physical or logical asset held at any service provider site is recorded and tracked in a system that is itself protected. The catalogue is revisited every year, and sooner after a significant change.

Source: CSA CCM v4.1, DCS-07. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

artefacts

held by a system

at each review

moderate

to go live

Identity provider / directory

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Access control list and audit log for the asset tracking system · Identity provider / directory
Asset location history for a sample of devices moved between sites · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

Records of the periodic catalogue review · Document repository

governing documentDocuments that govern the control

Configuration management database or asset register covering all sites · Policy repository / GRC workspace
Reconciliation reports between the register and discovery scans or physical counts · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Register held in a spreadsheet anyone can edit
Secondary or edge sites not represented in the catalogue
No reconciliation, so the register drifts from what is actually installed

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

DCS-06 Assets Classification · DCS-08 Controlled Physical Access Points