NIST SP 800-171 Rev 3
03.05 IA (Identification and Authentication)

NIST SP 800-171 Rev 3 03.05.02: Device Identification and Authentication

Uniquely identify and authenticate devices before establishing a connection.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 17 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

Azure Security Benchmark · 2 controls

  • IM-4 Authenticate server and services
  • IM-7 Restrict resource access based on conditions

CMMC 2.0 · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

  • 161R1-IA-3 Device Identification and Authentication
  • 161R1-IA-9 Service Identification and Authentication

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-07 Authorise Network Connection Only for Managed Equipment

AWS Well-Architected Security Pillar · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CIS Controls v8 · 1 control

  • CIS-13.9 Deploy Port-Level Access Control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

FedRAMP High · 1 control

  • IA-3 Device Identification and Authentication

FedRAMP Moderate · 1 control

  • IA-3 Device Identification and Authentication

ISO 27001:2022 · 1 control

  • 5.16 Identity management

NIST Cybersecurity Framework 2.0 · 1 control

NIST SP 800-172 · 1 control

  • 3.5.1e Identification of Systems, Components, and Devices

NIST SP 800-53 Rev 5 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in 03.05 IA (Identification and Authentication)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.05.02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

If you hold PCI DSS 4.071.1% covered · 28 gapsIf you hold C5 (Germany)68% covered · 31 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.164.9% covered · 34 gapsIf you hold ISO 27001:202262.9% covered · 36 gapsIf you hold CIS Controls v853.6% covered · 45 gapsIf you hold NIST SP 800-161 Rev 152.6% covered · 46 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 17 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-171 Rev 3 controls