PCI DSS 4.0
Req 9: Restrict Physical Access

PCI DSS 4.0 9.2.3: 9.2.3 Physical protection of network hardware and lines

Within the facility, physical access must be limited for wireless access points, gateways, networking and communications hardware, and telecommunication lines. The guidance explains that securing this equipment stops malicious people from reaching network resources, attaching their own devices to wired networks to reach the CDE or connected systems, or intercepting traffic. Applicability: all entities. Customized approach objective: people without authorization cannot get physical access to networking equipment.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 52 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.

ISO 27001:2022 · 5 controls

  • 5.16 Identity management
  • 5.23 Information security for use of cloud services
  • 8.16 Monitoring activities
  • 8.2 Privileged access rights
  • 8.5 Secure authentication

ISO 27701:2019 · 5 controls

  • 5.3.3 Organizational roles, responsibilities and authorities
  • 6.3.1 Internal organization
  • 6.6.2 User access management
  • 6.8.2 Equipment
  • 6.9.4 Logging and monitoring

SOC 2 · 5 controls

  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • 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
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

CIS Controls v8 · 4 controls

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.5 Require MFA for Administrative Access
  • CIS-6.8 Define and Maintain Role-Based Access Control
  • CIS-8.5 Collect Detailed Audit Logs

HIPAA Security Rule · 4 controls

ISO 27002:2022 · 4 controls

  • 5.23 Information security for use of cloud services
  • 8.15 Logging
  • 8.16 Monitoring activities
  • 8.2 Privileged access rights
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • 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 SP 800-53 Rev 5 · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

NIST SP 800-171 Rev 3 · 2 controls

  • ANSSI-HYG-26 Control and Protect Access to Server Rooms and Technical Areas

C5 (Germany) · 1 control

  • CFTC-SS-6 Physical Security and Environmental Controls Category

CMMC 2.0 · 1 control

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

ISO 27018:2019 · 1 control

  • 9.2.3 Management of privileged access rights
  • P2-7.1.4 P2-7.1.4 Multi-factor entry to telecom rooms outside the data centre

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.2.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.

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.

Query this from an agent

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