THREATNOIR
Subscribe
NIST SP 800-53 Rev. 5 · IA-3

Device Identification and Authentication

US National Institute of Standards and Technology (NIST) · cited in 26 of our lessons

Explanation

What it asks for. Defined devices or types of devices must be uniquely identified and authenticated before a local, remote or network connection is established.

In practice. Doing this well means network access control with certificate-based authentication such as 802.1X, device certificates for VPN and zero trust access, and conditional access policies that check device identity and compliance. Auditors expect device authentication configurations, certificate management records and reports showing unauthenticated devices are blocked or quarantined. A device inventory makes it possible to spot devices that should not be there.

Common gaps. Many networks still allow any device that is plugged in to connect. Printers, IoT and operational technology devices are commonly exempted without compensating controls. Device certificates are also sometimes issued without a process to revoke them when devices are lost or retired.

Open SP 800-53 at NIST
The official text
Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection: local; remote; network] connection. Discussion: Devices that require unique device-to-device identification and authentication are defined by type, device, or a combination of type and device. Organization-defined device types include devices that are not owned by the organization. Systems use shared known information (e.g., Media Access Control [MAC], Transmission Control Protocol/Internet Protocol [TCP/IP] addresses) for device identification or organizational authentication solutions (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1x and Extensible Authentication Protocol [EAP], RADIUS server with EAP-Transport Layer Security [TLS] authentication, Kerberos) to identify and authenticate devices on local and wide area networks. Organizations determine the required strength of authentication mechanisms based on the security categories of systems and mission or business requirements. Because of the challenges of implementing device authentication on a large scale, organizations can restrict the application of the control to a limited number/type of devices based on mission or business needs.

From NIST SP 800-53 Rev. 5, a work of the US government in the public domain.

Lessons that cite it

Real incidents where this item mattered: the latest 12 of 26.