- When guests, reception and connected devices share one network, a compromised guest device can try to reach the hotel's internal systems
- Three security zones (guest, administrative and infrastructure/IoT) are a sensible starting point; payments, CCTV, locks and network management may need zones of their own
- Segmentation has to cover wired ports as well as Wi-Fi, with default-deny firewall rules between zones
- A captive portal controls access. Client isolation and Wi-Fi encryption are separate controls that need their own configuration
- No reply to a ping proves nothing: validation checks allowed and blocked flows from every access point and network segment
How a network becomes a risk without anyone noticing
Many mid-size hotels did not design their network from scratch. It grew in stages: guest access came first, then reception plugged the PMS computer into the same network because it was the nearest cable, and later someone added security cameras on whatever Wi-Fi signal reached the corridor. Each decision made sense at the time. Where nobody revisited them, the result can be a flat network in which a guest's laptop and the reception terminal sit, technically, in the same environment.
That changes what a compromised guest device can do. On a segmented network it can browse the internet. On a flat one it can also see, and try to reach, the reception printer, a PMS workstation or a camera's admin page. Nobody has to have exploited that path yet for it to be a risk; it stays open until someone closes it.
The US National Institute of Standards and Technology covers this in its hotel-specific practice guide, NIST SP 1800-27: Securing Property Management Systems. Its reference architecture gives guests and hotel staff different levels of access, instead of equal access because they happen to share a network.
A reference architecture: three zones to start
A workable starting point for many small and mid-size hotels is three security zones:
- Guest zone: internet access, no route to hotel systems, and client isolation switched on.
- Administrative zone: reception PCs, office systems and PMS workstations, with access only to the business systems they use.
- Infrastructure and IoT zone: cameras, electronic locks, building automation and sensors, reachable only by the controllers and management servers that run them.
Two caveats. Not everything is Wi-Fi: payment terminals, the PMS server, access-control controllers, cameras and switches often use wired Ethernet, so the segmentation has to cover cabled ports as well as SSIDs. And three zones may not be enough. A property with card-payment systems, extensive CCTV, electronic locks and building automation may need finer separation, for example:
| Zone | Examples | Access principle |
|---|---|---|
| Guest | Phones, laptops, tablets | Internet access; no unauthorised access to internal networks; client isolation |
| Administrative | Reception PCs, office systems, PMS workstations | Access to authorised business systems only |
| Payments | Card-payment systems in PCI DSS scope | Restricted access, based on the payment architecture and PCI DSS scope |
| Building and IoT | CCTV, locks, HVAC, sensors | Only the controllers, management servers and vendor services they need |
| Network management | Switches, firewalls, access points, controllers | Authorised IT administration only |
This is a simplified example, not an implementation blueprint. The principle behind it is least-privilege communication: each zone talks only to the systems it needs. In practice you build it with VLANs on the switches and the Wi-Fi controller, plus explicit firewall rules between zones. Block traffic between zones by default and allow only the flows the operation needs, each one documented. A camera monitoring station, for instance, needs a specific rule to reach the cameras, not open access between networks.
Segmentation reduces the risk of guests reaching the hotel's internal devices and services directly. If your PMS is cloud-hosted, though, its login page is on the internet and anyone can reach it, guests included. It still depends on strong authentication, sensible permissions, application security and monitoring, and network separation doesn't replace any of them.
Why cameras and locks need a restricted segment
Cameras, electronic locks and other IoT devices can carry a high risk when they run unsupported firmware, keep default credentials, expose admin interfaces or have limited update mechanisms. How exposed a given device is depends on the vendor, its configuration and how it is maintained. These devices need an inventory, secure configuration, updates in line with the manufacturer's guidance, and network access limited to the integrations they use.
Restricted doesn't mean cut off. The PMS usually talks to the lock-management system, reception uses keycard encoders, monitoring stations reach the cameras and building-management servers reach HVAC controllers. List those integrations, document them and allow each one with a specific rule.
If a camera or electronic lock can be reached directly from the guest network, it is exposed to untrusted users on the hotel's local network. That raises the risk of someone exploiting a vulnerability or logging in with default credentials, even if the device can't be reached from the public internet. Moving these devices to a restricted segment, with internet access limited to what they need, is one of the controls with the best return for the effort.
Captive portal, encryption and client isolation
A captive portal controls whether a device gets onto the network or the internet. On its own, it doesn't stop one guest's device from talking to another guest's device on the same network. That needs client isolation (also called AP isolation or peer-to-peer blocking), configured and tested on every access point and controller. These are three different controls:
| Control | What it does | What it doesn't do |
|---|---|---|
| Wi-Fi encryption (WPA2/WPA3, Enhanced Open) | Protects traffic on the radio link against passive interception | Stop authenticated devices from reaching each other |
| Captive portal | Controls access, and presents terms or authentication after connection | Encrypt the radio link or isolate guests from each other |
| Client isolation | Blocks direct traffic between guest devices | Control who joins the network |
For encryption, consider WPA2/WPA3 or Enhanced Open (OWE) where guest devices support it. An open network with no encryption leaves any traffic that isn't otherwise encrypted readable to someone nearby with the right tools.
If you authenticate guests per booking, use random vouchers or individual codes that expire with the stay. Avoid passwords built from the room number and surname: room numbers get overheard, and a surname is easy to learn at check-in. If the portal integrates with the PMS, share only the data the Wi-Fi system needs.
Tell guests the official network name at check-in and in the room. Criminals can set up networks with names similar to a hotel's, so staff should know how to spot and report an access point that isn't on the hotel's inventory.
The portal can also collect personal data: names, booking references, device identifiers and connection logs. Under UK GDPR, decide why you collect each item, your lawful basis, what you tell guests, who can see the logs and how long you keep them. Don't ask for more than the connection needs, and check what the Wi-Fi provider receives.
Card payments and PCI DSS
If the hotel has systems that store, process or transmit card data, segmentation can also limit the scope of PCI DSS, as long as it actually isolates those systems. Creating VLANs doesn't reduce scope by itself. The PCI Security Standards Council accepts VLANs as a segmentation method when they are configured to restrict access, and the isolation has to be shown to work. Where segmentation is used to isolate the cardholder data environment, requirement 11.4.5 of PCI DSS v4.0.1 calls for penetration testing of the segmentation controls at least every 12 months and after any change to them. Our PCI DSS guide for hotels covers the rest of the standard.
How to implement segmentation with less disruption
How to check whether your network is exposed
A first check is to connect a laptop to the guest network and try to open connections to known administrative devices, such as the reception printer's web page or a camera's admin interface. If a connection succeeds, the isolation has failed. The reverse doesn't hold: a device that ignores ping may still have an open web or management port, and a reply can come from a gateway or firewall instead of the device itself.
Treat that as a health check, not proof. A formal segmentation validation, or a penetration test where PCI DSS applies, covers:
- guest-to-internal access, tested by protocol and port, not by ping alone
- guest-to-guest isolation on every access point and controller
- access to the management interfaces of network equipment
- the authorised integrations, to confirm they work and go no further
- IPv6 where the network uses it, as well as IPv4
- the encryption settings of each SSID
- differences introduced by individual access points, controllers or wired ports
Guest Wi-Fi is one of four attack surfaces a hotel runs at the same time. For the wider picture, see our analysis of the cybersecurity risks hotels need to address.