PCI DSS 4.0 7.3.1: 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.
This control maps to 68 controls across 20 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-ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on the mission
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
NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 7.3.1 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.