DCS-08 Equipment Identification
Authenticate connections using equipment identity, so a device must be recognised before it is allowed to connect.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration showing device authentication, such as certificate based network access control · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Records of connection attempts refused for unrecognised equipment · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- The device identity register · Policy repository / GRC workspace
- Coverage across the network segments where it is required · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Device authentication enabled on one segment and absent elsewhere
- Fallback to open access when device authentication fails
- Device identity register not maintained, so stale devices remain trusted
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-07 Controlled Access Points · DCS-09 Secure Area Authorization