The entity must set both how often periodic POI device inspections occur and what type of inspection is done through its targeted risk analysis, carried out in line with every element of Requirement 12.3.1. The guidance names factors such as the device's location and whether it is attended or unattended, notes that unsupervised devices in public areas might be inspected more often than those in secure or supervised areas, and advises consulting vendor documentation. Applicability: deployed card-present POI devices. Objective under the customized approach: how often POI devices get inspected reflects the risk the entity faces. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
PCI DSS 4.0 9.5.1.2.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.
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.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.