7.2.2 User access assigned by job function and least privilege

Access for every user, including privileged users, must be assigned on the basis of the user's job classification and function, and restricted to the least privileges needed to perform that person's responsibilities. The guidance explains that once role needs are defined under 7.2.1, individuals can be granted access by placing them in the matching roles, gives the example that a database or backup administrator should not hold the full privileges of a systems administrator, and suggests entities may consider privileged access management that grants elevated rights only when needed and removes them afterwards. Objective under the customized approach: access to systems and data is confined to what each job function needs, as set out in the related access roles.

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