EvidenceSheet
PCI DSS v4.0.1 · Req 9: Restrict Physical Access

9.5.1 Protection of POI devices from tampering

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.

Source: PCI DSS v4.0.1, 9.5.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
artefacts
0
held by a system
0
at each review
hard
to go live
HR system / LMS
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • POI device protection policy and procedures covering inventory, inspection and training · HR system / LMS
  • Scope statement identifying which card-present devices are covered and which are excluded · Policy repository / GRC workspace
  • Evidence linking the procedure to the device list, inspection records and training records · HR system / LMS
  • Store or site operating procedures describing tamper response · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

9.4.7 Destruction of electronic media · 9.5.1.1 Current register of POI devices