PCI DSS 4.0 8.4.2: 8.4.2 MFA for all non-console CDE access
Every form of non-console access into the CDE, not only administrative access, must be protected with MFA. Applicability: excludes system or application accounts that run automated functions, to point-of-sale terminal user accounts that are limited to a single card number per transaction, or to user accounts authenticated only with phishing-resistant factors. MFA is required separately for this access and for remote access under 8.4.3, so a user who connects remotely to the network and then into the CDE authenticates with MFA twice. It covers every kind of system component (cloud and hosted systems, on-premises applications, workstations, servers, endpoints and network security devices) and both direct network or system access and web-based access to applications. MFA may be applied at network or system/application level, not necessarily both. Objective under the customized approach: access into the CDE cannot be gained with a single authentication factor. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 43 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 8.4.2 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.