PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.2.1: 8.2.1 Unique ID assigned to every user

Each user must be given a unique ID before being permitted to reach any system component or cardholder data. The guidance explains that unique identification keeps actions traceable to one person, supports individual accountability and an effective audit trail, and helps resolve and contain misuse. Applicability: not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction. Customized approach objective: every action by every user can be attributed to an individual.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 5 controls

  • AC-17 Remote Access
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-3 Device Identification and Authentication
  • IA-4 Identifier Management
  • IA-8 Identification and Authentication (Non-Organizational Users)

FedRAMP Moderate · 5 controls

  • AC-17 Remote Access
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-3 Device Identification and Authentication
  • IA-4 Identifier Management
  • IA-8 Identification and Authentication (Non-Organizational Users)

CMMC 2.0 · 4 controls

CIS Controls v8 · 3 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-5.6 Centralize Account Management

Azure Security Benchmark · 2 controls

  • IM-1 Use centralized identity and authentication system
  • IM-3 Manage application identities securely and automatically

C5 (Germany) · 2 controls

HIPAA Security Rule · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-IA-2 IA-2 Identification and Authentication (Organizational Users)
  • SP800-53-IA Identification and Authentication Family

NIST SP 800-66 Rev 2 · 2 controls

PCI 3DS Core Security Standard · 2 controls

  • P1-5.2.2 P1-5.2.2 Unique account ID per individual
  • P2-4.1.1 P2-4.1.1 Issuer and merchant user access to their own interfaces

UK Cyber Essentials · 2 controls

  • CE-AC.2 Authenticate Users Before Granting Access
  • CE-SC.4 Authenticate Users Before Access

ACSC Essential Eight · 1 control

  • E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)

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

  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles

AWS Well-Architected Security Pillar · 1 control

  • SEC02-BP04 Rely on a centralized identity provider

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

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

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

ISO 27001:2022 · 1 control

  • 5.16 Identity management

ISO 27002:2022 · 1 control

  • 5.16 Identity management

ISO 27701:2019 · 1 control

  • 6.6.2 User access management

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-171 Rev 3 · 1 control

  • 03.05.01 User Identification and Authentication

SOC 2 · 1 control

  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials

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 Req 8: Identify and Authenticate Users

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 8.2.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 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. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls