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

9.2.2 Controls on publicly accessible network jacks

Physical controls, logical controls, or a mix of the two must be applied within the facility to stop publicly accessible network jacks from being used. The guidance offers examples such as disabling jacks in public or visitor-accessible areas and enabling them only when network access is explicitly approved, or escorting visitors at all times wherever active jacks exist, and says whatever approach is used should stop any person or device lacking explicit authorization from connecting. Applicability: all entities. Objective under the customized approach: unauthorized devices cannot connect to the network of the entity from public areas of the facility.

Source: PCI DSS v4.0.1, 9.2.2. 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.

5
artefacts
1
held by a system
2
at each review
hard
to go live
Physical access / facilities
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

  • Switch configuration showing unused or public ports disabled or placed on an isolated VLAN · Physical access / facilities

periodic reviewEvidence produced at each review

  • Network access control (802.1X) configuration and port authorization records · Physical access / facilities
  • Walkthrough observation notes of public-area jacks · Physical access / facilities

governing documentDocuments that govern the control

  • Inventory of network ports in lobbies, meeting rooms and other public or visitor areas · Policy repository / GRC workspace
  • Visitor escort procedure covering areas with live network jacks · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Physical access / facilities on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

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.2.1.1 Monitoring of entry to sensitive areas · 9.2.3 Physical protection of network hardware and lines