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

NIST SP 800-171 Rev 3 03.05.01: User Identification and Authentication

Uniquely identify and authenticate system users and associate that unique identification with processes acting on behalf of those users.

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

What else in your programme already covers this

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

C5 (Germany) · 3 controls

  • C5-IDM-02 Granting and change of user accounts and access rights
  • C5-IDM-09 Authentication mechanisms
  • C5-OPS-15 Logging and Monitoring - Accountability

CMMC 2.0 · 3 controls

FedRAMP High · 3 controls

  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(5) Identification and Authentication (Organizational Users) | Individual Authentication with Group Authentication (IA-2(5))
  • IA-8 Identification and Authentication (Non-Organizational Users)

FedRAMP Moderate · 3 controls

  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(5) Identification and Authentication (Organizational Users) | Individual Authentication with Group Authentication (IA-2(5))
  • IA-8 Identification and Authentication (Non-Organizational Users)

HIPAA Security Rule · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

PCI DSS 4.0 · 3 controls

  • 8.2.1 8.2.1 Unique ID assigned to every user
  • 8.2.2 8.2.2 Shared and generic IDs only by exception
  • 8.3.1 8.3.1 Access authenticated with at least one factor
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-13 Prefer Strong Authentication Where Possible
  • ASD37-20 Multi-factor authentication (Essential)
  • ASD37-21 Disable local administrator accounts (Excellent)
  • IM-1 Use centralized identity and authentication system
  • IM-6 Use strong authentication controls

CIS Controls v8 · 2 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-6.7 Centralize Access Control

ISO 27001:2022 · 2 controls

  • 5.16 Identity management
  • 8.5 Secure authentication

ISO 27002:2022 · 2 controls

  • 5.16 Identity management
  • 8.5 Secure authentication
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • NIST-CSF-PR.AA-03 Users, services, and hardware are authenticated

NIST SP 800-161 Rev 1 · 2 controls

  • 161R1-IA-2 Identification and Authentication (Organizational Users)
  • 161R1-IA-8 Identification and Authentication (Non-Organizational Users)

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-IA-2 IA-2 Identification and Authentication (Organizational Users)
  • NIST800-IA-8 IA-8 Identification and Authentication (Non-organizational Users)

UK Cyber Essentials · 2 controls

  • CE-AC.2 Authenticate Users Before Granting Access
  • CE-SC.4 Authenticate Users Before Access
  • E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

NIST SP 800-172 · 1 control

  • 3.5.3e Prohibit Connection of Unknown or Unverified System Components

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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.01 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.

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.

Query this from an agent

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