PCI DSS 4.0
Req 9: Restrict Physical Access

PCI DSS 4.0 9.4.4: 9.4.4 Management approval for media leaving facility

Management must approve every movement of media with cardholder data outside the facility, including media handed out to individuals. The guidance explains that without firm approval before media leaves secure areas, it may not be tracked or protected and its whereabouts may be lost. Applicability: the approver should hold sufficient management authority to grant the approval, but their job title does not have to include the word manager. Objective under the customized approach: media stays inside a facility unless accountable personnel approve its removal.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 36 controls across 14 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 27701:2019 · 6 controls

  • 6.15.2 Information security reviews
  • 6.5.3 Media handling
  • 6.6.2 User access management
  • 6.8.2 Equipment
  • 6.9.4 Logging and monitoring
  • 6.9.5 Control of operational software

CIS Controls v8 · 5 controls

  • CIS-2.5 Allowlist Authorized Software
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.5 Require MFA for Administrative Access
  • CIS-8.2 Collect Audit Logs
  • CIS-8.8 Collect Command-Line Audit Logs
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • 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.PS-05 Installation and execution of unauthorized software are prevented

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

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

FedRAMP High · 2 controls

  • AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions
  • CM-7(2) Prevent Program Execution

FedRAMP Moderate · 2 controls

  • AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions
  • CM-7(2) Prevent Program Execution

NIST SP 800-161 Rev 1 · 2 controls

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.18 Use of privileged utility programs

ISO 27002:2022 · 1 control

  • 8.18 Use of privileged utility programs

ISO 27018:2019 · 1 control

  • 9.4.4 Use of privileged utility programs

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