EvidenceSheet

11.2.2 Inventory of authorized wireless access points

The entity keeps an up-to-date inventory of the wireless access points it has authorized, and each entry carries a documented business justification. Guidance (purpose): the inventory helps administrators respond quickly when rogue devices are detected. Guidance (good practice): also record known neighbouring access points that appear in scans but are not attached to the entity's network, noting how it was confirmed they can be disregarded, and handle any rogue access point posing a threat to the CDE under the Requirement 12.10.1 incident response plan. Objective under the customized approach: rogue wireless access points cannot be confused with authorized ones.

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

4
artefacts
0
held by a system
0
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. 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

  • Authorized wireless access point inventory with location, MAC/BSSID, SSID and owner · Policy repository / GRC workspace
  • Business justification recorded for every authorized access point · Policy repository / GRC workspace
  • List of known neighbouring access points with the reasoning for excluding them · Policy repository / GRC workspace
  • Evidence the inventory is compared against wireless scan results · 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

11.2.1 Detect authorized and rogue wireless access points · 11.3.1 Quarterly internal vulnerability scans