We separate user, server, camera, guest and production networks by purpose. We define the required connections between networks and check that permissions work correctly after the migration.
Internal firewallNAC / 802.1XGuest networkCamera and IoT networkManagement networkMicro-segmentation
Need and approach
Why is this service needed?
VLAN separation splits broadcast domains. Access between networks, however, is controlled by firewall or ACL rules at the point where routing happens. We design the two separately.
01
Are our existing switches sufficient for segmentation?
Most managed switches support VLANs and basic ACLs. Stateful inspection between segments usually requires a firewall; the assessment starts with the device inventory.
02
Will segmentation break our applications?
The observation phase and monitoring mode exist to reduce this risk. We turn on blocking mode after unexpected traffic in the logs has been cleaned up.
03
Do we have to deploy 802.1X?
It isn’t mandatory. But it’s a strong control in office and production areas where physical access can’t be controlled; it can be rolled out in phases starting with critical areas.
04
What is micro-segmentation, and do we need it?
It’s separation at the server or workload level and is valuable in virtualized data centers. In most organizations we recommend finishing macro-segmentation first.
Implementation approach
Controlled, documented, sustainable
01 / ANALYSIS
Observation
The current communication map is built from flow data and logs.
02 / PLAN
Design
The segment model, addressing and permission matrix are prepared.
03 / EXECUTION
Phased migration
Segments are enabled first in monitoring mode, then in blocking mode.
04 / HANDOVER
Verification
Access tests are run; documentation and a change procedure are delivered.