What evidence do auditors commonly ask for on 8.4.1 MFA for non-console administrative CDE access?

MFA configuration for jump hosts, bastions, PAM and admin consoles into the CDE; List of administrative access paths into the CDE with the MFA control on each; Observation record of an administrator logging in with MFA; MFA enrolment report for all administrative accounts.

What is the most common gap auditors find on 8.4.1?

Direct SSH or RDP to CDE servers bypasses the MFA-protected jump host

PCI DSS v4.0.1 · Req 8: Identify and Authenticate Users

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

Source: PCI DSS v4.0.1, 8.4.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

artefacts

held by a system

at each review

easy

to go live

Identity provider / directory

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

MFA configuration for jump hosts, bastions, PAM and admin consoles into the CDE · Identity provider / directory
MFA enrolment report for all administrative accounts · Identity provider / directory

periodic reviewEvidence produced at each review

Observation record of an administrator logging in with MFA · Identity provider / directory

governing documentDocuments that govern the control

List of administrative access paths into the CDE with the MFA control on each · Policy repository / GRC workspace

First move

Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.

Common gaps auditors find

Direct SSH or RDP to CDE servers bypasses the MFA-protected jump host
Cloud console administrators not enrolled in MFA
Second factor is another password, which is not MFA

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

8.3.11 Tokens, smart cards and certificates individually assigned · 8.4.2 MFA for all non-console CDE access