What evidence do auditors commonly ask for on DCS-09 Equipment Identification?

Network access control configuration showing device certificate or hardware identity checks (for example 802.1X); List of equipment approved for connection with its identifiers; Device certificate issuance and revocation records; Logs of connection attempts rejected for unknown equipment; Procedure for maintaining the approved equipment list.

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

MAC address filtering relied on as the only identity check

CSA CCM v4.1 · DCS - Datacenter Security

`DCS-09` Equipment Identification

Equipment identity is used as a way of authenticating connections.

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

easy

to go live

Endpoint management (MDM / EDR)

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

Network access control configuration showing device certificate or hardware identity checks (for example 802.1X) · Endpoint management (MDM / EDR)
Device certificate issuance and revocation records · Endpoint management (MDM / EDR)
Logs of connection attempts rejected for unknown equipment · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

List of equipment approved for connection with its identifiers · Policy repository / GRC workspace
Procedure for maintaining the approved equipment list · Policy repository / GRC workspace

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

MAC address filtering relied on as the only identity check
Approved device list not updated when equipment is retired
Management networks exempted from device authentication

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-08 Controlled Physical Access Points · DCS-10 Secure Area Authorization