PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.2.4: 8.2.4 User ID lifecycle changes authorized

Any addition, deletion or modification of a user ID, an authentication factor or another identifier object must be: authorized with appropriate approval; and carried out with only the privileges stated on the documented approval. The guidance stresses detecting IDs created or changed outside the normal process, since attackers often escalate an existing account or create new IDs. Applicability: covers every user account, whether held by employees, contractors, consultants, temporary staff or third-party vendors. Objective under the customized approach: no lifecycle event affecting a user ID or authentication factor can occur without appropriate authorization.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 56 controls across 19 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 · 8 controls

  • AC-2 Account Management
  • AC-2(1) Automated System Account Management
  • AC-2(4) Automated Audit Actions
  • AC-2(7) Privileged User Accounts
  • 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 · 8 controls

  • AC-2 Account Management
  • AC-2(1) Automated System Account Management
  • AC-2(4) Automated Audit Actions
  • AC-2(7) Privileged User Accounts
  • 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)

NIST SP 800-53 Rev 5 · 5 controls

ISO 27001:2022 · 4 controls

  • 5.16 Identity management
  • 5.18 Access rights
  • 8.2 Privileged access rights
  • 8.32 Change management

ISO 27002:2022 · 4 controls

  • 5.16 Identity management
  • 5.18 Access rights
  • 6.5 Responsibilities after termination or change of employment
  • 8.2 Privileged access rights

SOC 2 · 4 controls

  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

CIS Controls v8 · 3 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-5.6 Centralize Account Management
  • CIS-6.1 Establish an Access Granting Process

HIPAA Security Rule · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

CMMC 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • ANSSI-HYG-06 Organise Joiner, Leaver and Role Change Procedures
  • PA-3 Manage lifecycle of identities and entitlements

C5 (Germany) · 1 control

  • C5-IDM-02 Granting and change of user accounts and access rights

ISO 27701:2019 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-AC.1 User Account Approval Process

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

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.

Query this from an agent

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