9.5.1 POI device protection
Point-of-interaction (POI) devices that capture payment card data are protected from tampering and unauthorized substitution.
5
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Inspection checklist and completed inspections · Policy repository / GRC workspace
- Training records for POI staff · HR system / LMS
governing documentDocuments that govern the control
- POI device inventory with make, model, serial, location · Policy repository / GRC workspace
- Sample tamper-evident seals or photos · Policy repository / GRC workspace
- Procedure for suspected tampering · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- POI inventory incomplete
- Inspections skipped
- No staff training
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 sheet9.4.7 Electronic media destruction · 9.5.1.1 POI inventory maintained