What evidence do auditors commonly ask for on DCS-17 Datacenter Metrics?

Defined datacenter security metric set with owners and thresholds (for example badge anomalies, environmental excursions, camera uptime); Monitoring dashboards or reports showing metric values over time; Metric reports sent to management or customers with recommended actions; Records of anomalies detected through the metrics and their follow-up; Metric definition review records.

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

Metrics collected but never reported to anyone who can act

CSA CCM v4.1 · DCS - Datacenter Security

`DCS-17` Datacenter Metrics

Security metrics for the datacenter are defined, tracked and reported so that datacenter assets and services stay protected.

Source: CSA CCM v4.1, DCS-17. 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

hard

to go live

Policy repository / GRC workspace

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

Monitoring dashboards or reports showing metric values over time · SIEM / log platform

periodic reviewEvidence produced at each review

Records of anomalies detected through the metrics and their follow-up · SIEM / log platform
Metric definition review records · Policy repository / GRC workspace

governing documentDocuments that govern the control

Defined datacenter security metric set with owners and thresholds (for example badge anomalies, environmental excursions, camera uptime) · Policy repository / GRC workspace
Metric reports sent to management or customers with recommended actions · 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

Metrics collected but never reported to anyone who can act
Metrics measure activity volume rather than security outcomes
No thresholds, so deviations are not flagged

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-16 Equipment Location · DCS-18 Datacenter Operations Resilience