Personnel working in POI environments must receive training to recognise attempted tampering with, or replacement of, POI devices, and the training must cover: checking the identity of any third party who says they are repair or maintenance staff before letting them modify or troubleshoot devices; procedures ensuring no device is installed, returned or replaced unless it has first been verified; being alert to suspicious behaviour around devices; and reporting suspicious behaviour and signs of tampering or substitution to the appropriate personnel. Applicability: personnel in environments with deployed card-present POI devices. Objective under the customized approach: personnel understand the attacks made on POI devices and the technical and procedural countermeasures the entity uses, and know how to get help and guidance when needed.
This control maps to 24 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.
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.
PCI DSS 4.0 9.5.1.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.
The graph holds this control, the 24 it maps to, and the evidence behind each claim, over MCP and REST.