IA-3 Device identification and authentication
Requires organization-defined devices or device types to be uniquely identified and authenticated before a local, remote or network connection is established, so that connectivity is granted to known devices rather than
4
artefacts
2
held by a system
1
at each review
easy
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Network access control or certificate based authentication configuration · Identity provider / directory
- Logs showing unknown devices denied connection · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Certificate or credential issuance and revocation records for devices · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Defined list of devices or device types requiring authentication and the connection types covered · Policy repository / GRC workspace
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
Common gaps auditors find
- Device authentication applied to laptops while printers, cameras and operational technology connect freely
- Shared pre-shared key used across all devices, giving no unique identity
- Wired ports left open without any 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 sheetIA-2 Identification and authentication of organizational users · IA-4 Identifier management