PCI DSS 4.0
Req 9: Restrict Physical Access

PCI DSS 4.0 9.5.1.1: 9.5.1.1 Current register of POI devices

The entity must keep a current register of its POI devices that records: the device make and model; where the device is located; and the device serial number or another means of uniquely identifying it. The testing procedures check that the list is updated whenever devices are added, moved or decommissioned. The guidance notes it can be kept in a device management system or in manual records, and for devices used on the road the location may include the person the device is assigned to. Applicability: deployed card-present POI devices. Objective under the customized approach: each POI device's identity and location are always on record and known.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

SOC 2 · 4 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • 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.4 CC6.4 Restricting physical access to facilities and assets

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

ISO 27001:2022 · 2 controls

  • 5.9 Inventory of information and other associated assets
  • 7.8 Equipment siting and protection

CIS Controls v8 · 1 control

  • CIS-1.1 Establish and Maintain Detailed Enterprise Asset Inventory

FedRAMP High · 1 control

  • CM-8 System Component Inventory

FedRAMP Moderate · 1 control

  • CM-8 System Component Inventory

ISO 27002:2022 · 1 control

  • 5.9 Inventory of information and other associated assets

ISO 27701:2019 · 1 control

  • 6.5.1 Responsibility for assets

NIST Cybersecurity Framework 2.0 · 1 control

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-53 Rev 5 · 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 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.5.1.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 17 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls