---
tool_id: WACK-TOOL-0069
concept_id: WACK-CONCEPT-0009
playbook_content_id: WACK-CONTENT-0149
status: draft
technical_review: pending
artifact_type: working_worksheet
---

# Guest Wi-Fi and Payment Network Story

> Replace labels such as guest and payment with a testable description of devices, connections, administration, and separation.

**Expected output:** A network story showing payment devices, guest access, infrastructure, management paths, provider roles, observed separation, exceptions, and change triggers.  
**Working time:** 50 minutes  
**Derived from:** WACK-CONTENT-0149

## Working context

Organization / environment: __________________________________________  
Facilitator / owner: __________________________________________________  
Participants: _________________________________________________________  
Date: ____________________  Review trigger or next date: ______________

## 01 / Find — List networks and devices

Inventory payment devices, wireless names, network equipment, Internet connections, management tools, and provider access.

- [ ] **Which network does each payment device use?**

  Notes: ________________________________________________

- [ ] **Who administers the equipment?**

  Notes: ________________________________________________

## 02 / Map — Draw reachable paths

Map ordinary traffic, management access, shared infrastructure, remote support, and failure paths.

- [ ] **What shares the same infrastructure?**

  Notes: ________________________________________________

- [ ] **How is separation enforced?**

  Notes: ________________________________________________

## 03 / Explain — Describe observed separation

State configuration and test evidence rather than relying on network names or installer assurances.

- [ ] **What was inspected or tested?**

  Notes: ________________________________________________

- [ ] **Which path remains uncertain?**

  Notes: ________________________________________________

## 04 / Reduce — Remove avoidable adjacency

Retire unknown devices, unused services, shared administration, and unnecessary paths.

- [ ] **Which connection is not needed?**

  Notes: ________________________________________________

- [ ] **Which credential or service can be removed?**

  Notes: ________________________________________________

## 05 / Prove — Retain current network evidence

Keep diagrams, inventories, configuration, test results, provider records, and change history aligned.

- [ ] **Does the diagram match current equipment?**

  Notes: ________________________________________________

- [ ] **What change reopens testing?**

  Notes: ________________________________________________

## Completion check

- [ ] Every payment and network device is identifiable.
- [ ] Separation is supported by configuration and testing evidence.
- [ ] Provider and merchant network responsibilities are explicit.

## Decision and next action

Decision: _____________________________________________________________  
Owner: __________________________  Due date: ___________________________  
Evidence or artifact location: ________________________________________

---

_Working practitioner worksheet pending technical review. It does not determine PCI DSS compliance, replace the standard, or replace instructions from an assessor or compliance-accepting entity. The Cluster of Wack is an independent resource and is not affiliated with or endorsed by PCI SSC._