PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.2.6: 8.2.6 Inactive accounts removed within 90 days

A user account must be disabled or removed once it has gone unused for 90 days. The guidance explains that unused accounts are attractive targets because changes to them, such as a new password, tend to go unnoticed, and advises that where an extended absence such as a leave of absence is expected, the account be disabled when the absence begins rather than after 90 days. Objective under the customized approach: inactive user accounts cannot be used.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

SOC 2 · 5 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
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • ASBv3-LT-2 Enable threat detection for identity and access management
  • ASBv3-PA-4 Review and reconcile user access regularly

ISO 27001:2022 · 2 controls

  • 5.16 Identity management
  • 5.18 Access rights

NIST SP 800-53 Rev 5 · 2 controls

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

C5 (Germany) · 1 control

  • C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins

CIS Controls v8 · 1 control

CMMC 2.0 · 1 control

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

ISO 27002:2022 · 1 control

  • 5.16 Identity management

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
  • P1-5.2.4 P1-5.2.4 Account misuse prevented

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