Segmentación de redes WiFi: VLANs, SSIDs y tráfico de invitados

Welcome to the Purple Technical Briefing series. Today we are tackling one of the most consequential, and most frequently misunderstood, decisions in enterprise wireless network design: WiFi network segmentation. If you are managing a hotel, a retail estate, a conference centre, a stadium, or any venue where you are running both guest-facing and operational WiFi, this episode is directly relevant to you. We are going to cover why segmentation is non-negotiable in 2024, how VLANs and multiple SSIDs work together to deliver it, and what a well-designed deployment actually looks like in practice. This is not a theoretical lecture. By the end of this briefing, you will have a clear framework for evaluating your current network, identifying the gaps, and making a confident decision about your next steps. Let us get into it. So, what exactly is WiFi network segmentation? At its core, it is the practice of dividing a single physical wireless infrastructure into multiple logically isolated networks. Each segment carries different traffic, serves different users or devices, and is governed by different security policies, all running over the same physical access points and cabling. The two technologies that make this possible are VLANs, Virtual Local Area Networks, and SSIDs, Service Set Identifiers. Let us take each in turn. A VLAN is a Layer 2 construct defined in the IEEE 802.1Q standard. It allows a single physical switch or access point to carry multiple, logically separate broadcast domains. Think of it like having multiple separate roads running through the same tunnel. The vehicles, your data packets, are tagged with a VLAN ID as they enter the network, and that tag determines which road they travel on and which exits they can use. VLAN IDs range from 1 to 4094, and in a well-designed enterprise deployment, each traffic class gets its own ID. An SSID is simply the network name that a wireless device sees and connects to. When you configure multiple SSIDs on an access point, each one is mapped to a corresponding VLAN. So your guest network, let us call it VenueGuest, maps to VLAN 10. Your staff network maps to VLAN 20. Your IoT and building management devices map to VLAN 30. And your point-of-sale or payment terminals sit on VLAN 40, which carries the strictest access controls to satisfy PCI DSS requirements. Now, why does this matter so much from a security perspective? The answer is lateral movement. In a flat, unsegmented network, where every device shares the same broadcast domain, a compromised device can communicate directly with every other device on that network. A guest's smartphone infected with malware can, in theory, probe your POS terminals, your staff laptops, your CCTV system. That is not a theoretical risk. It is a documented attack vector. Network segmentation eliminates that attack surface by ensuring that traffic from one segment simply cannot reach another without passing through a firewall or router that enforces explicit policy. From a compliance standpoint, segmentation is often mandatory, not optional. PCI DSS, the Payment Card Industry Data Security Standard, requires that cardholder data environments be isolated from all other network traffic. GDPR imposes obligations around data minimisation and access control that are much easier to satisfy when your network architecture enforces separation by design. In healthcare environments, clinical device networks must be isolated from general-purpose WiFi under NHS Digital guidelines. Let us talk about the architecture in a bit more detail. In a typical enterprise deployment, you will have a core switch connected to your internet uplink and firewall. That switch carries multiple VLANs as tagged traffic, what is called trunk ports, down to your wireless LAN controller or cloud-managed access points. Each access point broadcasts multiple SSIDs simultaneously. Modern enterprise access points from vendors like Cisco Meraki, Aruba, Ruckus, and Ubiquiti can handle between eight and sixteen SSIDs per radio, though best practice is to keep it to four or fewer to minimise management overhead and radio frequency pollution. The wireless LAN controller handles the mapping between SSIDs and VLANs, and also enforces client isolation within each SSID. Client isolation is a critical setting: it prevents devices on the same SSID from communicating directly with each other, which is essential on a guest network where you do not want one guest's device talking to another's. Authentication is the other key dimension. For your guest network, you will typically use an open SSID with a captive portal, a web-based authentication page where guests log in via social media, email, or a voucher code. This is where a platform like Purple's Guest WiFi solution adds significant value: it handles the captive portal, the data capture, the consent management under GDPR, and the downstream marketing analytics, all integrated with your VLAN architecture. For your corporate staff network, you should be running WPA3-Enterprise, which uses IEEE 802.1X authentication against a RADIUS server, typically integrated with your Active Directory or Azure AD. This means each staff member authenticates with their corporate credentials, and the network can apply per-user policies based on role or department. For IoT devices, the challenge is different. Most IoT devices do not support 802.1X, so you will use WPA2-PSK or WPA3-SAE with a strong, rotated passphrase, combined with strict firewall rules that limit what those devices can reach. Many organisations also deploy MAC address filtering as an additional control on IoT VLANs, though this should be treated as a secondary measure rather than a primary security control. One more architecture consideration worth flagging: bandwidth management. On your guest VLAN, you should implement per-client rate limiting, typically somewhere between 5 and 20 megabits per second downstream, depending on your total uplink capacity and expected concurrent user count. This prevents any single guest from saturating your uplink and degrading the experience for everyone else. Now let me give you the practical implementation framework. I would break this into five phases. Phase one: traffic classification. Before you touch a single switch port, document every device type and traffic class in your environment. Guest devices, staff devices, IoT, payment terminals, building management systems, CCTV. Each one needs a home. Phase two: VLAN design. Assign a VLAN ID and IP subnet to each traffic class. Keep your guest VLAN on a completely separate subnet with no route to your internal address space. Your firewall should have an explicit deny-all rule between the guest VLAN and everything internal, with only outbound internet access permitted. Phase three: SSID mapping. Configure your SSIDs on your wireless controller, map each to its VLAN, enable client isolation on the guest SSID, and set your authentication method per segment. Phase four: firewall policy. This is where most deployments fall short. The VLAN architecture is only as strong as the inter-VLAN routing rules on your firewall. Document every permitted flow explicitly. Default-deny everything else. Phase five: monitoring and validation. Deploy a network monitoring tool and validate that your segmentation is actually working. Run periodic penetration tests, or at minimum use a scanning tool from a guest device to confirm you cannot reach internal subnets. Now, the pitfalls. The most common one I see is misconfigured trunk ports. If a switch port carrying multiple VLANs is accidentally configured as an access port, all traffic collapses onto a single VLAN and your segmentation disappears silently. Always audit your switch configurations after any change. The second pitfall is SSID proliferation. Every additional SSID you broadcast consumes airtime for beacon frames, even when no clients are connected. In a dense venue with hundreds of access points, broadcasting eight SSIDs per AP can meaningfully degrade throughput. Keep it lean. The third pitfall is forgetting the wired network. WiFi segmentation is pointless if your wired infrastructure is not equally segmented. A guest who plugs into an Ethernet port in a conference room and finds themselves on your corporate network has bypassed your entire wireless security architecture. Let me run through a few questions I hear regularly from clients. How many SSIDs should we broadcast? No more than four per radio band. Three is ideal: guest, corporate, IoT. Do we need a separate physical access point for guests? No. Modern enterprise APs handle multiple SSIDs and VLANs on the same hardware. Physical separation is unnecessary and expensive. Can Purple's platform work with existing wireless infrastructure? Yes. Purple integrates with all major enterprise wireless vendors via standard RADIUS and VLAN tagging. You do not need to replace your APs. Is WPA3 mandatory for guest networks? Not yet mandatory, but strongly recommended. WPA3's Simultaneous Authentication of Equals protocol eliminates the dictionary attack vulnerability present in WPA2-PSK. Deploy it where your client device mix supports it. What is the minimum viable segmentation for a small venue? At minimum: one guest VLAN, one staff VLAN, one IoT VLAN. That is three VLANs, three SSIDs, and a firewall with inter-VLAN rules. That is your baseline. To wrap up: WiFi network segmentation using VLANs and multiple SSIDs is the foundational security and compliance architecture for any enterprise or venue wireless deployment. It is not optional if you are handling guest traffic, payment data, or clinical devices. It is the difference between a network that is defensible and one that is a liability. The key takeaways are these. First: map every device type to a dedicated VLAN before you design anything. Second: your firewall inter-VLAN rules are as important as the VLAN architecture itself. Default-deny, explicit-permit. Third: keep your SSID count low, enable client isolation on guest networks, and implement per-client rate limiting. Fourth: validate your segmentation regularly. Do not assume it is working because you configured it once. If you are looking to add a managed guest WiFi layer with GDPR-compliant data capture, captive portal authentication, and marketing analytics on top of your segmented architecture, Purple's platform is designed to slot directly into this architecture. You can find out more at purple dot ai. Thanks for listening. Until next time.