PCI DSS 4.0 7.2.5: 7.2.5 Application and system accounts least privilege
Every application and system account and its related access privileges must be assigned and managed so that: privileges are the least needed for the system or application to operate; and access is limited to those systems, processes or applications that have a specific need for the account. The guidance explains that a compromised service account gives an attacker whatever the account can reach, and suggests entities may consider a baseline that keeps such accounts out of privileged groups such as domain or local administrators or root, restricts the machines and hours they can be used, and removes VPN or remote access. Objective under the customized approach: the rights given to system and application accounts are confined to what that application or system needs to operate. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 89 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 7.2.5 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.