PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.2.5: 8.2.5 Terminated users' access revoked immediately

Access for users who have been terminated must be revoked immediately. The testing procedures check both local and remote access lists for terminated IDs and confirm that any physical authentication factor, for example a token or smart card, has been deactivated or handed back. The guidance explains that a former employee or third party who keeps a working account, or an attacker who takes over an abandoned one, could reach cardholder data. Objective under the customized approach: accounts belonging to terminated users cannot be used.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 46 controls across 21 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-2(13) Disable Accounts for High-Risk Individuals
  • AC-2(3) Disable Accounts
  • AC-2(7) Privileged User Accounts
  • PS-4 Personnel Termination
  • PS-5 Personnel Transfer

FedRAMP Moderate · 5 controls

  • AC-2(13) Disable Accounts for High-Risk Individuals
  • AC-2(3) Disable Accounts
  • AC-2(7) Privileged User Accounts
  • PS-4 Personnel Termination
  • PS-5 Personnel Transfer

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • 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

ISO 27001:2022 · 3 controls

  • 5.11 Return of assets
  • 5.18 Access rights
  • 6.5 Responsibilities after termination or change of employment

ISO 27701:2019 · 3 controls

  • 6.4 Human resource security
  • 6.4.3 Termination and change of employment
  • 6.6.2 User access management

C5 (Germany) · 2 controls

  • C5-HR-05 Responsibilities in the event of termination or change of employment
  • C5-IDM-04 Withdraw or adjust access rights as the task area changes

CIS Controls v8 · 2 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-6.2 Establish an Access Revoking Process

HIPAA Security Rule · 2 controls

ISO 27002:2022 · 2 controls

  • 5.18 Access rights
  • 6.5 Responsibilities after termination or change of employment

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • ANSSI-HYG-06 Organise Joiner, Leaver and Role Change Procedures
  • ASD37-37 Personnel management (Very Good)
  • PA-3 Manage lifecycle of identities and entitlements

CMMC 2.0 · 1 control

NIS2 Directive · 1 control

  • Art.21.2.i Human resources security, access control policies and asset management

UK Cyber Essentials · 1 control

  • CE-AC.3 Remove or Disable Accounts When No Longer Required

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.5 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 46 it maps to, and the evidence behind each claim, over MCP and REST.