PCI DSS 4.0
Req 7: Restrict Access by Need to Know

PCI DSS 4.0 7.2.1: 7.2.1 Access control model defined

The entity must define an access control model that governs how access is granted. The model must provide: access that fits what the entity needs for its business and for access; access to data resources and system components based on each user's job classification and functions; and only the least privileges (for example user versus administrator) needed to carry out a job function. The guidance describes typical model elements (the resources to protect, the job functions needing access to them, and the activities each function performs, such as read, write or query), names role-based and attribute-based models as options, and suggests separation of duties as a design consideration. Objective under the customized approach: access requirements are set by job function following the principles of need to know and least privilege.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 53 controls across 25 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CMMC 2.0 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-3.3 Configure Data Access Control Lists
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.7 Centralize Access Control
  • CIS-6.8 Define and Maintain Role-Based Access Control

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

Azure Security Benchmark · 3 controls

  • ASBv3-GS-6 Define and implement identity and privileged access strategy
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • IM-7 Restrict resource access based on conditions

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

ISO/IEC 42001:2023 · 3 controls

  • 6.1.2 AI risk assessment
  • 7.5.3 Control of documented information
  • 8.4 AI system impact assessment

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

AWS Well-Architected Security Pillar · 2 controls

C5 (Germany) · 2 controls

FedRAMP High · 2 controls

  • AC-3 Access Enforcement
  • AC-6 Least Privilege

FedRAMP Moderate · 2 controls

  • AC-3 Access Enforcement
  • AC-6 Least Privilege

HIPAA Security Rule · 2 controls

ISO 27701:2019 · 2 controls

  • 6.6 Access control
  • 6.6.1 Business requirements of access control

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

NIS2 Directive · 1 control

  • Art.21.2.i Human resources security, access control policies and asset management

NIST Cybersecurity Framework 2.0 · 1 control

  • 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 SP 800-161 Rev 1 · 1 control

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

PCI 3DS Core Security Standard · 1 control

  • P1-5.1.2 P1-5.1.2 Roles and responsibilities defined for groups and accounts

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Req 7: Restrict Access by Need to Know

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 7.2.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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 53 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls