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

PCI DSS 4.0 7.3.3: 7.3.3 Access control default deny all

The access control systems must be configured to deny all access by default, so that nobody receives access unless a rule specifically grants it. The guidance warns that some products ship with an allow-all default that permits access until a deny rule is written, so checking the default configuration matters. Customized approach objective: privileges and access rights are forbidden unless explicitly permitted.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

CIS Controls v8 · 3 controls

  • CIS-13.9 Deploy Port-Level Access Control
  • CIS-3.3 Configure Data Access Control Lists
  • CIS-6.7 Centralize Access Control

NIST SP 800-53 Rev 5 · 3 controls

CMMC 2.0 · 2 controls

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

FedRAMP High · 2 controls

  • AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions
  • SC-7(5) Deny by Default Allow by Exception

FedRAMP Moderate · 2 controls

  • AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions
  • SC-7(5) Deny by Default Allow by Exception

ISO 27701:2019 · 2 controls

  • 6.6.1 Business requirements of access control
  • 6.6.4 System and application access control

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

AWS Well-Architected Security Pillar · 1 control

  • SEC03-BP05 Define permission guardrails for your organization

Azure Security Benchmark · 1 control

  • ASBv3-PA-7 Follow just enough administration (least privilege) principle

C5 (Germany) · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.3 Information access restriction

ISO 27002:2022 · 1 control

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-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-66 Rev 2 · 1 control

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.3.3 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 28 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls