PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.4.1: 8.4.1 MFA for non-console administrative CDE access

Personnel with administrative access who reach the CDE through any non-console connection must use MFA. The guidance defines that using the same factor twice, such as two passwords, does not count as MFA. Applicability: covers every person holding administrative or elevated privileges who reach the CDE over a non-console connection, meaning logical access across a network interface rather than a direct physical connection. Objective under the customized approach: nobody can obtain administrative access into the CDE using a single factor alone.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 44 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 · 6 controls

  • AC-17(4) Privileged Commands and Access
  • CM-5 Access Restrictions for Change
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(8) Access to Accounts Replay Resistant
  • IA-5(2) Public Key-Based Authentication
  • SC-23 Session Authenticity

FedRAMP Moderate · 6 controls

  • AC-17(4) Privileged Commands and Access
  • CM-5 Access Restrictions for Change
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(8) Access to Accounts Replay Resistant
  • IA-5(2) Public Key-Based Authentication
  • SC-23 Session Authenticity

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • 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

CMMC 2.0 · 3 controls

  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-13 Prefer Strong Authentication Where Possible

C5 (Germany) · 2 controls

CIS Controls v8 · 2 controls

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.5 Require MFA for Administrative Access

ISO 27001:2022 · 2 controls

  • 8.2 Privileged access rights
  • 8.5 Secure authentication

ISO 27002:2022 · 2 controls

  • 8.2 Privileged access rights
  • 8.5 Secure authentication

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
  • E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2
  • ASD37-20 Multi-factor authentication (Essential)
  • IM-6 Use strong authentication controls

HIPAA Security Rule · 1 control

  • 164.312(d) Person or Entity Authentication (Standard)

NIS2 Directive · 1 control

  • Art.21.2.j Multi-factor or continuous authentication, secured communications and secured emergency communications

NIST SP 800-172 · 1 control

  • 3.5.3e Prohibit Connection of Unknown or Unverified System Components
  • 164.312(d) Person or Entity Authentication (Standard)
  • P2-4.2.1 P2-4.2.1 Multi-factor for all non-console personnel access

UK Cyber Essentials · 1 control

  • CE-AC.7 MFA for Administrative Accounts

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

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