IT Infrastructure & Cloud
Office VLANs: Separating Guest, Staff, and Device Networks
One network for every person and every device is the most common pattern in offices, and the riskiest. This guide covers how to divide an office network with VLANs, the traffic rules between VLANs, and how to test them.
SEO and Content Specialist
7 min read
Short answer: office VLANs split one physical network into several logical networks, for example staff, guests, devices (printers, CCTV, attendance machines), and management of network equipment. The separation is done on the switches using the IEEE 802.1Q standard, while who may talk to whom is decided by rules on the firewall or router between VLANs. Without those rules, VLANs only tidy up addressing, they do not secure anything.
In many offices, staff laptops, guest phones, printers, CCTV cameras, and servers share one network. As long as nothing goes wrong, this feels practical. Once one device is infected, or a curious guest scans the network, every other device is within reach. Office VLANs are the most common way to separate them without pulling new cables. This guide covers how to divide VLANs, how to write rules between them, and the technical details that often make the separation leak.
What is a VLAN and how does it work?
A VLAN (Virtual LAN) is a logical network created on top of the same switch. Devices in different VLANs cannot reach each other directly, even when connected to the same switch. The standard is IEEE 802.1Q, whose current active edition is 802.1Q-2022.
It works through two types of switch ports:
| Port type | Function | Example |
|---|---|---|
| Access (untagged) | Carries one VLAN for one device that does not know about VLANs | Ports to desktop computers, printers, cameras |
| Trunk (tagged) | Carries many VLANs at once, each packet marked with its VLAN | Ports between switches, to access points, to the firewall or router |
The VLAN tag carries a VLAN number (VLAN ID). Cisco documentation notes that IDs 0 and 4095 are reserved for the system, so usable numbers fall in the range 1 to 4094. For an office, that is far more than enough. What matters is the design, not the count.
Wi-Fi follows the same pattern: each network name (SSID) on an access point is mapped to one VLAN, and the cable from the access point to the switch becomes a trunk. That way, guest Wi-Fi and staff Wi-Fi can be broadcast from the same access point but end up in different networks. Access point count and channels are covered in Designing Office Wi-Fi.
Example VLAN layout for a mid-sized office
VLANs should be divided by who the users are and what they may reach, not by the org chart. The example below is an illustration, not a design for a specific office.
| VLAN | Contents | May reach |
|---|---|---|
| 10 Staff | Staff laptops and computers | Internet, internal servers, printers |
| 20 Guests | Visitor devices | Internet only |
| 30 Devices | Printers, attendance machines, smart devices | Only the services they need, for example the attendance server |
| 40 CCTV | Cameras and video recorders | Only the video recorder and people authorized to view footage |
| 50 Servers | File servers, internal applications | Reached from the staff VLAN as needed |
| 99 Management | Management interfaces of switches, access points, firewall | Only from network admin devices |
Some considerations when designing it:
- Separate devices that cannot be updated. Cameras, attendance machines, and smart devices rarely receive security updates, so place them in their own VLAN with the narrowest possible access.
- Teams with sensitive data (finance, HR) can get their own VLAN if there really are servers or applications only they may reach.
- Do not create too many VLANs. Every VLAN adds rules that have to be maintained. Start with a division by function, then split further when there is a clear reason.
Rules between VLANs: where the real security lives
VLANs separate traffic at the switch layer. For devices in different VLANs to communicate, traffic has to pass through a router, a layer 3 switch, or a firewall. That is where the rules go. A common mistake: the VLANs are created, but the router allows all traffic between them, so the separation exists only on paper.
The safe principle is deny everything, then open only what is needed:
- Deny all traffic between VLANs as the base rule.
- Allow the staff VLAN to reach servers and printers on the services actually used.
- Allow the guest VLAN to reach the internet only, and deny destinations in every internal office address range.
- Allow the device VLAN to reach only the servers it needs.
- Allow access to the management VLAN only from network admin devices or through an admin VPN.
- Record each rule and its reason, so old rules can be reviewed and removed.
A firewall that separates VLANs also makes monitoring easier, because traffic between teams is logged in one place.
Technical details that often make the separation leak
A correct design can still leak because switch settings were left at their defaults. Some practices recommended in vendor documentation:
- Do not use VLAN 1 for users. Cisco’s best practices guide recommends a management VLAN separate from user traffic, and a native VLAN on trunks that uses a dummy VLAN not used by any end user.
- One VLAN per access port. MikroTik documentation explicitly says not to use multiple VLAN IDs on access ports.
- Limit the VLANs allowed on each trunk to the ones needed. A trunk to an access point does not need to carry the server VLAN.
- Unused ports are shut down or placed in an empty VLAN, so a cable plugged in at random does not land straight in the staff network.
- Enable VLAN filtering carefully. MikroTik documentation warns that enabling VLAN filtering without a ready management path can lock you out of your own device. Prepare console access or a spare port before changing the configuration.
Rolling out VLANs in an office that is already running
Splitting a network that is used every day needs an order, so the office does not stop working:
- Device inventory: list every connected device, especially printers, cameras, and devices whose IP address is typed manually into other systems.
- Check switch capability: switches that cannot be configured (unmanaged) do not support VLANs and need replacing at points that require separation.
- Design the address scheme for each VLAN, including automatic address assignment (DHCP) and fixed addresses for servers and printers.
- Move in stages: start with the guest VLAN and the management VLAN, which affect work the least, then devices, and staff last.
- Work outside busy hours and have a way to restore the old configuration.
- Update the documentation: port map, VLAN list, and firewall rule list.
Testing that the VLANs really are separate
Separation is only proven once it is tested from the user’s side. A minimum test:
- From the guest network, try to reach the printer, the server, and the switch admin interface. All of them must fail.
- From the staff VLAN, make sure the servers and printers that are allowed still work.
- From the device VLAN, make sure cameras or attendance machines cannot reach staff laptops.
- Plug a laptop into an unused port and make sure it gets no access.
Record the results together with the test date. A fuller installation checklist is in the New Office Network Installation Checklist.
How Legia works on this
In the Office Network Installation service, installing switches, routers, firewalls, and wireless access points includes separating the guest, office, and operational networks, so that one faulty device does not drag the others down. The need to divide the network between teams is also one of the bases for calculating the cost. The network division is configured during the testing and tidy-up stage, every point is tested, and you receive the cabling map, point numbering, and device configuration documentation. Other services in this pillar are in IT Infrastructure & Cloud.
Frequently asked questions
Are VLANs enough to secure an office network?
No. VLANs separate traffic, but the rules on the firewall or router decide what may pass between VLANs. Devices in each VLAN still need updates and strong passwords.
Do all switches support VLANs?
No. Switches that cannot be configured (unmanaged) generally do not support VLANs. You need managed switches, at least at points that carry more than one network, including switches connected to access points.
How many VLANs is ideal for an office?
There is no fixed number. The example in this article uses six VLANs by function: staff, guests, devices, CCTV, servers, and management. Add a VLAN only when there is a genuinely different access rule, because every VLAN adds rules that have to be maintained.
Is a different network name enough for guest Wi-Fi?
No. A different network name without a VLAN and firewall rules can still put guests on the same network as staff. Guest Wi-Fi has to be mapped to its own VLAN that may only reach the internet.
Sources
- IEEE, 802.1Q-2022 Bridges and Bridged Networksstandards.ieee.org
- Cisco, Best Practices for Catalyst 6500/6000 and 4500/4000 Series Switches Running Cisco IOS Softwarecisco.com
- MikroTik, Bridge VLAN Tablehelp.mikrotik.com
- Cisco Meraki, Configuring Simple Guest and Internal Wireless Networksdocumentation.meraki.com

