What evidence do auditors commonly ask for on 7.3.1 Need-to-know access control system covers all components?

Inventory of system components mapped to the access control system that governs each; Vendor documentation for the directory, IAM or access control products used; Configuration screenshots or exports showing need-to-know restrictions applied; List of components outside central identity management with their local access controls.

What is the most common gap auditors find on 7.3.1?

Network devices or appliances rely on local accounts outside any access control system

PCI DSS v4.0.1 · Req 7: Restrict Access by Need to Know

`7.3.1` Need-to-know access control system covers all components

One or more access control systems must be in place that limit access according to each user's need to know and that cover every system component. The guidance explains that such systems automate the restriction of access and assignment of privileges, reducing the chance that a user is unknowingly given access to cardholder data. Customized approach objective: privileges and access rights are administered through mechanisms built for that purpose.

Source: PCI DSS v4.0.1, 7.3.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

moderate

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

Configuration screenshots or exports showing need-to-know restrictions applied · Identity provider / directory

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Inventory of system components mapped to the access control system that governs each · Policy repository / GRC workspace
Vendor documentation for the directory, IAM or access control products used · Policy repository / GRC workspace
List of components outside central identity management with their local access controls · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Network devices or appliances rely on local accounts outside any access control system
Some in-scope databases are not integrated with the central directory
Access control system inventory omits cloud management consoles

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

7.2.6 Query access to stored cardholder data restricted · 7.3.2 Access control system enforces role-based permissions