Network segmentation that follows people, not subnets
Network segmentation divides a network into parts, so that one compromised host cannot reach all other hosts. This guide explains VLANs, firewall rules, microsegmentation, and identity-based segmentation, and it shows where each method gets hard.
Hosts go into segments
Each group of hosts with the same job and the same risk gets its own segment.
A checkpoint between them
All traffic between segments goes through an enforcement point that refuses what no rule permits.
Only the needed path opens
The laptop reaches the app on one port. The app reaches the database on one port.
Lateral movement stops
An attacker on the laptop cannot connect to the database directly.
What network segmentation is
Network segmentation divides one network into smaller parts, and it controls the traffic between the parts. Each part is a segment.
The opposite is a flat network. In a flat network, each host can open a connection to each other host. A printer can reach the payroll database, and a guest laptop can reach a domain controller.
A flat network is easy to operate, but it helps an attacker. An attacker who controls one host scans the network, finds a weak server, and moves to it. This step is called lateral movement. Most large breaches include it.
Segmentation does not stop the first compromise. It limits what the attacker can reach next, and it gives you more time to find them.
Four ways to segment a network
VLANs and subnets
A VLAN separates hosts at layer 2, and each VLAN usually has its own IP subnet. Hosts in different VLANs can only communicate through a router. This method is the base of most segmentation, but a VLAN by itself is not a security control. The router decides what goes through.
Firewalls and ACLs between segments
A firewall or a router with access control lists sits between the segments. Firewall ACLs say which source addresses can reach which destination addresses and ports. A default-deny rule at the end refuses all other traffic.
Microsegmentation
Microsegmentation makes the segment as small as one workload. A host firewall, a hypervisor, or a cloud security group applies the rules next to each workload. Two servers in the same subnet can then have different rules, and traffic inside a subnet is also controlled.
Identity-based segmentation
Identity-based segmentation writes each rule in terms of a user, a group, or a service. The rule does not contain a source IP address. A rule says "the database team can reach the database on port 5432", and the system applies it wherever the user is.
Where each method gets hard
Rule sprawl
Each new application adds rules, and few people remove old rules. After some years, a firewall holds thousands of lines that nobody fully understands. A wide rule that someone added during an outage stays in place.
IP addresses that change
A rule with an IP address assumes that the address means one thing. Containers, autoscaling groups, and DHCP break that assumption. The address that was a build server last week is a different host today, and the old rule still permits it.
Remote users who land inside a segment
A traditional VPN gives a remote user an address from a pool inside the network. All remote users share that pool. The firewall sees one source subnet for the finance team, the engineers, and the contractors, so it cannot tell them apart.
Many teams then permit the full VPN pool to reach most segments. The segmentation that protects the office does not apply to the people who work outside it.
Agents on each workload
Microsegmentation frequently needs an agent or a host firewall policy on each server. Legacy systems, appliances, and managed databases cannot run an agent.
How to plan a segmentation project
- Find the systems that matter most. Start with databases, domain controllers, and admin interfaces. Do not start with a full network redesign.
- Record who needs each system. Write the group of people or services, the protocol, and the port.
- Refuse by default. Permit the paths from step 2 and refuse all other traffic. A default-deny rule is the only rule that covers the cases you did not think of.
- Write rules for groups, not for addresses. A rule for a group stays correct when people move and when addresses change.
- Include remote users. Give a remote user the same narrow access as a user in the office.
- Look at the logs. A rule that no traffic uses is a rule that you can remove.
How Firezone segments access
Firezone does identity-based segmentation for the traffic of users and services. It does not replace the VLANs and firewalls inside your network. It controls who can enter each part of it.
- Default-deny. A Resource is not reachable until a Policy permits it. Firezone has no deny rules to put in order.
- One Group to one Resource. Each Policy connects a Group from your identity provider to one Resource.
- Small Resources. A Resource can be a CIDR range, one IP address, or a DNS name. Traffic restrictions limit a Resource to protocols and port ranges, for example TCP port 5432 only.
- The most specific Resource wins. When Resources overlap, Firezone uses the Resource with the longest prefix. An IP Resource is more specific than any CIDR Resource.
- No change to the existing network. You put a Gateway in the network. Clients and Gateways make outbound connections only, so you open no inbound firewall port.
A remote user does not land in a shared address pool with a route to the full network. The Client routes only the addresses of Resources. For all other addresses, the Client has no route through Firezone.
Policies combine with OR logic. If two Policies give the same person the same Resource, the less strict Policy applies. Keep wide Resources for the small group that needs them.
Try the rules
The table shows four Resources that overlap. Type an IPv4 address to see which Resource Firezone uses for it. The longest prefix is the most specific Resource. Only the Group in the Policy of that Resource can reach the address through it.
Segmentation with VLANs and ACLs, a legacy VPN, and Firezone
The three approaches control different traffic. Many networks use more than one of them.
| VLANs + firewall ACLs | Legacy VPN | Firezone | |
|---|---|---|---|
| What a rule names | Source and destination addresses | An address pool and a subnet | A Group and a Resource |
| Default-deny | YesWith a deny rule at the end | PartialFrequently a route to the full network | YesNo Policy means no access |
| Controls traffic between two servers | Yes | No | PartialOnly traffic that goes through a Client |
| Different access for two remote users | NoRemote users share one pool | PartialWith one profile for each group | YesEach Policy names a Group |
| Access as small as one address and one port | Yes | Partial | YesAn IP Resource with traffic restrictions |
| Rules stay correct when a user moves | No | Partial | Yes |
| Needs a change to the network | YesNew VLANs, routes, and rules | YesAn inbound port and routes | NoAn outbound Gateway only |
The table describes the usual design of each category. A specific product can be different. Read the documentation of the product before you decide.
Common questions
What is the difference between network segmentation and microsegmentation?
Network segmentation divides a network into zones, usually a subnet or a VLAN for each zone. Microsegmentation makes each workload its own zone. It also controls traffic between two hosts in the same subnet.
Is a VLAN a security boundary?
Not by itself. A VLAN separates hosts at layer 2. Security comes from the firewall rules or ACLs on the router between the VLANs. If the router permits all traffic, the VLANs do not stop lateral movement.
Does a flat network make ransomware worse?
Yes. In a flat network, malware on one host can reach all other hosts on the ports that they listen on. Segmentation with default-deny rules limits the hosts that the malware can reach.
Does Firezone replace my internal firewall?
No. Firezone is not a firewall, and it does not control traffic between two servers in your network. It controls which users and services can reach each Resource through a Gateway. Keep your firewall for traffic inside the network.
How do I segment access for remote users?
Do not give remote users a route to the full network. Give each group a rule for the systems that it needs. In Firezone, you create a Resource for each system or subnet, and a Policy for each Group.