Skip to content
Access
PCI DSS segmentation

Keep registers apart from guests and staff

Payment systems often share a network with guests and staff. With Purple, identity decides which part of the network each person or device lands on.

Phones, laptops, tills, CCTV and TVs join through your access point. Cloud RADIUS checks each one and sends it to the open, secure or xPSK network by identity, each on its own VLAN; a leaver whose account is disabled is rejected.

Every deviceYour access pointsCloud RADIUSRejected: account disabled
Open
  • Captive portal sign-in
  • Consent recorded
  • BYOD onboarding lane
Secure
  • EAP-TLS from your MDM
  • Identity decides the VLAN
  • SecurePass and OpenRoaming
xPSK
  • A key per device
  • Own VLAN and bandwidth limit
  • Revoke one key alone
VLAN 10VLAN 20VLAN 40

Cloud RADIUS sends every device to the open, secure or xPSK network by identity, each on its own VLAN.

OpenVLAN 10SecureVLAN 20xPSKVLAN 40

The problem

One shared password next to the card machines

  • PCI DSS v4.0.1 Req 2.3.2

    Leavers mean re-keying everything

    Wireless keys must change when anyone who knows them leaves. With one shared key, that means everyone.

  • One flat network

    The whole estate is in scope

    Guests, staff and registers on one flat network put every device in front of your assessor.

  • Cyber Security Breaches Survey 2025

    Attacks are the norm

    The UK Cyber Security Breaches Survey 2025 found 43% of businesses breached or attacked (67% of medium, 74% of large).

The solution

Identity decides where each connection lands

Every connection is checked by Purple cloud RADIUS, which returns a VLAN for that person or device. Purple never touches card data.

  • Guests on the open networkGuests sign in through the captive portal and land on the guest VLAN, away from staff and payments.
  • Staff on certificates (EAP-TLS)Each staff device carries its own certificate. Group membership in your directory decides its VLAN.
  • Registers on WiFi keys (xPSK)Each register and card machine gets its own WiFi key and VLAN. To the register it is an ordinary WPA2-Personal passphrase.
  • No new hardwareThe access points you run today send each connection to Purple.
Illustration

How it works

What your QSA asks, and what Purple shows

  1. Req 2.3.2: change keys when people leave

    Revoke one key or certificate and every other device stays connected. No re-keying every register.

  2. Req 8: identify users and authenticate access

    Every person and device has its own certificate or WiFi key, tied to an identity, not one password shared by everyone.

  3. Req 10: log and monitor all access

    Every accept and reject is logged with the time, site, network, VLAN and device, and streamed to Microsoft Sentinel, Splunk, Elastic or Datadog.

Proof

Segmented networks in retail and hospitality

Whitbread runs segmented staff WiFi on Purple, and McDonald's runs on Purple across its estate. ISO 27001 and Cyber Essentials Plus, and zero data breaches since 2012.

80%
fewer IT helpdesk requests at McDonald's
500M
logins a year
80,000+
venues run on Purple, in 90 countries
  • ISO 27001 certified
  • Cyber Essentials Plus
  • Zero data breaches since 2012

Trusted by

  • Whitbread
  • McDonald's
  • Chase
  • Manchester Airports Group
  • Harrods
  • University of Sheffield
  • Walmart Canada
  • AGS Airports

FAQ

Common questions

Does Purple take our WiFi out of PCI scope?

Purple never touches card data. Each register and card machine gets its own WiFi key and VLAN, apart from guests and staff. Every authentication is logged as evidence for Req 8 and 10. Your QSA decides scope from the VLAN map and the log.

How does this help with Req 2.3.2?

Req 2.3.2 says wireless keys must change when anyone who knows them leaves. With a WiFi key or certificate per person and device, you revoke one and the rest stay connected.

Do we need new access points or switches?

No. Identity decides where someone lands, on the hardware you already run. Your access points send each connection to Purple cloud RADIUS.

Will our registers and payment terminals work with a key each?

Yes. To a register, its WiFi key is an ordinary WPA2-Personal passphrase, so nothing on it changes.

What about contractors who need the staff network?

Give each contractor their own WiFi key with its own VLAN. Revoke it when the job ends, and nobody else has to change anything.

What about card terminals on wired ports?

Switch ports take the same controls today: 802.1X certificates, or MAC authentication for terminals that cannot hold one, each on its own VLAN.

Get the registers off the shared network

Tell us how a typical site is wired. We map guests, staff and payments to their own VLANs and show you the evidence. All in a 45-minute design session.

Book a demo

Tell us about your network

Led by a Purple network engineer. No slides.