PCI DSS 4.0
Req 9: Restrict Physical Access

PCI DSS 4.0 9.3.2: 9.3.2 Visitor access procedures for the CDE

Procedures must be in operation for approving and administering visitor access to the CDE, including that: visitors receive authorization before they enter; visitors are escorted throughout their time in the CDE; visitors are plainly identified and issued a badge or other identification that has an expiry; and the visitor badge or identification visibly sets visitors apart from personnel. Applicability: all entities. Customized approach objective: the rules governing visitors entering the CDE are set and enforced, and visitors cannot go beyond the physical access they were authorized for while inside the CDE.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 5 controls

  • MA-5 Maintenance Personnel
  • PE-2 Physical Access Authorizations
  • PE-3 Physical Access Control
  • PE-6 Monitoring Physical Access
  • PE-8 Visitor Access Records

FedRAMP Moderate · 5 controls

  • MA-5 Maintenance Personnel
  • PE-2 Physical Access Authorizations
  • PE-3 Physical Access Control
  • PE-6 Monitoring Physical Access
  • PE-8 Visitor Access Records

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

CMMC 2.0 · 4 controls

ISO 27002:2022 · 4 controls

  • 7.1 Physical security perimeters
  • 7.2 Physical entry
  • 7.3 Securing offices, rooms and facilities
  • 7.6 Working in secure areas

ISO 27001:2022 · 3 controls

  • 7.2 Physical entry
  • 7.3 Securing offices, rooms and facilities
  • 7.6 Working in secure areas

C5 (Germany) · 2 controls

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

ISO 27701:2019 · 2 controls

  • 6.8 Physical and environmental security
  • 6.8.1 Secure areas

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-PE-3 PE-3 Physical Access Control
  • SP800-53-PE Physical and Environmental Protection Family

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk

SOC 2 · 1 control

  • SOC2-CC6.4 CC6.4 Restricting physical access to facilities and assets

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 9: Restrict Physical Access

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

PCI DSS 4.0 9.3.2 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 45 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls