Point-of-interaction devices that read card data through direct physical contact with the card form factor must be protected against tampering and unauthorized substitution, including by: keeping a list of POI devices; inspecting the devices periodically for signs of tampering or substitution; and training personnel to recognise suspicious behaviour and report tampering or unauthorized device substitution. Applicability: covers POI devices deployed for card-present transactions where the card is swiped, tapped or dipped. It does not apply to parts that serve solely for keying in a PAN manually, or to commercial off-the-shelf devices such as merchant-owned smartphones or tablets built for mass-market distribution. Customized approach objective: procedures for safeguarding and managing POI devices are defined, and personnel follow the expectations, controls and oversight set for them.
This control maps to 31 controls across 11 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 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 31 it maps to, and the evidence behind each claim, over MCP and REST.