Device Identification and Authentication
LOW ✓ MODERATE ✓ HIGHRequirements NIST SOURCE
Uniquely identify and authenticate [devices and/or types of devices] before establishing a [one of: local; remote; network] connection.
Discussion (NIST Supplemental Guidance)
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.
Enhancements NIST SOURCE
IA-3(1) Cryptographic Bidirectional Authentication LOW MODERATE HIGH
Authenticate [devices and/or types of devices] before establishing [one of: local; remote; network] connection using bidirectional authentication that is cryptographically based.
Discussion
A local connection is a connection with a device that communicates without the use of a network. A network connection is a connection with a device that communicates through a network. A remote connection is a connection with a device that communicates through an external network. Bidirectional authentication provides stronger protection to validate the identity of other devices for connections that are of greater risk.
IA-3(2) Cryptographic Bidirectional Network Authentication WITHDRAWN
Withdrawn. Incorporated into IA-3(1).
IA-3(3) Dynamic Address Allocation LOW MODERATE HIGH
- (a) Where addresses are allocated dynamically, standardize dynamic address allocation lease information and the lease duration assigned to devices in accordance with [organization-defined lease information and lease duration] ; and
- (b) Audit lease information when assigned to a device.
Discussion
The Dynamic Host Configuration Protocol (DHCP) is an example of a means by which clients can dynamically receive network address assignments.
IA-3(4) Device Attestation LOW MODERATE HIGH
Handle device identification and authentication based on attestation by [configuration management process].
Discussion
Device attestation refers to the identification and authentication of a device based on its configuration and known operating state. Device attestation can be determined via a cryptographic hash of the device. If device attestation is the means of identification and authentication, then it is important that patches and updates to the device are handled via a configuration management process such that the patches and updates are done securely and do not disrupt identification and authentication to other devices.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for IA-3 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- devices and/or types of devices to be uniquely identified and authenticated before establishing a connection are defined;
- one or more of the following PARAMETER VALUES is/are selected: {local; remote; network};
- <IA-03_ODP[01] devices and/or types of devices> are uniquely identified and authenticated before establishing a <IA-03_ODP[02] SELECTED PARAMETER VALUES> connection.
Examine
[SELECT FROM: Identification and authentication policy; system security plan; procedures addressing device identification and authentication; system design documentation; list of devices requiring unique identification and authentication; device connection reports; system configuration settings and associated documentation; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with operational responsibilities for device identification and authentication; organizational personnel with information security responsibilities; system/network administrators; system developers].
Test
[SELECT FROM: Mechanisms supporting and/or implementing device identification and authentication capabilities].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for IA-3. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Identification and authentication policy
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- Mechanisms supporting and/or implementing device identification and authentication capabilities
Other Records
- procedures addressing device identification and authentication
- list of devices requiring unique identification and authentication
- device connection reports
- other relevant documents or records