Use this guide as an implementation reference. Validate commands, policies and version-specific behaviour in a lab before applying changes to production systems.
What problem does segmentation solve?
Flat networks make it easier for a compromised endpoint to reach other systems. A malware infection on a user workstation may be able to scan servers, cameras, printers and management interfaces if the network has few internal controls.
Segmentation reduces unnecessary reachability. It does not guarantee that an attack cannot spread, but it can limit lateral movement and make suspicious communication easier to detect.
Plan security zones before creating VLANs
Start by grouping systems according to function, sensitivity and communication requirements. Common zones include administration, faculty, students, servers, CCTV, voice, guest wireless and network management.
- Administration: approved staff devices and business applications.
- Faculty and students: user networks with access limited to required services.
- Servers: application, database, directory and file services.
- CCTV and IoT: cameras and devices that should not initiate connections to user endpoints.
- Guest Wi-Fi: internet-only access, isolated from internal resources.
- Management: switches, firewalls, hypervisors and out-of-band interfaces.
Example VLAN and subnet plan
The following is an illustrative campus design. Select VLAN IDs and IP ranges to fit your existing addressing plan; do not copy them blindly into production.
| VLAN | Zone | Example subnet | Default access |
|---|---|---|---|
| 10 | Administration | 10.10.10.0/24 | Approved business services |
| 20 | Faculty | 10.10.20.0/24 | Learning and staff services |
| 30 | Students | 10.10.30.0/23 | Internet and approved learning systems |
| 40 | CCTV | 10.10.40.0/24 | NVR and required management only |
| 50 | Servers | 10.10.50.0/24 | Explicitly permitted application flows |
| 60 | Guest Wi-Fi | 10.10.60.0/23 | Internet only |
How traffic is controlled
VLANs create separate Layer 2 broadcast domains. Communication between VLANs requires Layer 3 routing. Place policy enforcement at a firewall or a suitably capable Layer 3 gateway, then define which source zones may reach which destinations, ports and services.
- Create VLAN interfaces and assign unique gateway addresses.
- Configure switch access ports for endpoint devices.
- Configure 802.1Q trunks between switches, routers and firewalls where required.
- Apply DHCP scopes and DNS settings for each subnet.
- Start with deny-by-default inter-zone policy, then allow only documented business flows.
- Log important allowed and denied traffic and review the logs.
Security policy examples
- Guest to internal networks: deny; allow internet access through the intended egress policy.
- Student to server zone: allow only required learning application services.
- CCTV to NVR: allow required camera-to-recorder traffic; deny general access to user networks.
- Management network to infrastructure devices: allow from approved administrator endpoints only.
- User networks to DNS, DHCP, authentication and application services: allow only the required ports and destinations.
Document each rule with an owner, purpose, source, destination, service and review date. Avoid broad any-to-any rules.
Validation and troubleshooting
Test from a client in every VLAN. Confirm it receives the correct address, gateway and DNS settings. Verify permitted services, confirm prohibited paths fail, and inspect firewall logs. Useful tools include ping, traceroute or tracert, ipconfig, ip addr, nslookup and packet capture.
Common issues include mismatched VLAN tagging, incorrect native VLAN configuration, missing routes, DHCP relay errors, duplicate subnets and firewall rules in the wrong order.
Best practices
- Maintain an up-to-date network diagram and IP/VLAN register.
- Use dedicated management access and MFA for administration.
- Disable unused switch ports and restrict trunk VLANs.
- Review inter-VLAN rules periodically.
- Monitor east-west traffic and investigate unusual flows.
- Test changes in a maintenance window and keep configuration backups.
Conclusion
A secure network is not simply a collection of connected devices. It is a set of controlled communication paths. VLANs provide useful separation, while routing policy, firewall controls, monitoring and regular reviews turn that separation into a meaningful security boundary.
