Network Micro Segmentation
Network Micro Segmentation
Network Micro Segmentation
Birds eye view of micro segmentation and its features and benefits
Micro Segmentation can fill the gap as one of the very effective way to contain
compromised asset.
Traditional Networks
In traditional Network, security is set at the edge or periphery, where North-south
communication takes place. This secures the intranet or office Network from outside
world. Security are extended by creating branches (and sub-branches) and keeping them
behind firewall. Communications with outside branch entities has to pass through the
firewall at edge of the branch.
This allows unrestricted communication between themselves within the branch. Inter-
branch or out side communications from any host in the branch has to go through branch
or departmental firewall. Granularity depends on the how many firewalls can be afforded
or how many logical firewalls can be created. In all these cases, traffic has to go all the
way to the firewall and return to the intended branch. This unnecessarily increases traffic
and delays within.
Practically, in most cases the firewall only exists at the edge to connect to outside world
or used for creating DMZs, unless, there is some specific needs. An example Traditional
network looks like the following
The picture below shows that the end points are able to communicate to each other
freely within VLANs or subnets behind a firewall. Practically, endpoint count may be in
hundreds. Infections in one of these servers are not contained within itself and can easily
spread
Figure 2. Cross-Talk within branch
Because of the nature of granularity, this cannot be achieved with physical Firewalls.
When this is done right at the virtualization level or by Virtualization Vendor, this brings
more and more controls that can be implemented and can take it to a whole new level.
This will make it truly software defined security controls
Figure 3. Each endpoint is protected by a virtual Firewall
We will try to explore this further with VMware NSX. All networking components in NSX
are Software Defined, which means these can be configured through management pane
as well as through APIs. The main component that is used for micro segmentation is
Distributed Firewall. This NSX component is implemented at hypervisor kernel layer
giving it full visibility of the in-memory data and traffic in Software defined Network.
Traffic is filtered at at the vNIC of each VMs making it impossible to bypass Distributed
Firewall.
The filtering of traffic happens happens based on series of security (policy) rules. The last
one obviously to DENY All. Policies are applied top to bottom and stops after executing
the match. The source and destination in the rules can be Security Groups in addition to
traditional IP and Ports. Security Groups are defined using anything from VMware
vSphere inventory. This may include
1. Static values
2. Tenant or department name
3. Logical Switch or VDS name
4. Operating system ( even like OS name containing "Windows")
5. VM name
6. Security tags (This can be added to VMs dynamically or statically)
7. any other entity within VMware vSphere inventory
Service composer is another advance topic, where this merges with other providers for
Antivirus etc. and security groups can include user identity and security posture. This may
be used to dynamically quarantine infected endpoint or VM.
Granularity - This give tremendous level of granularity. With proper vendor echo-system,
this can be extended to introspect for security posture and certain action including
quarantine of endpoints
Policy based - Extended rules possible using security groups, security tags. It makes it
truly software defined
Zero Trust - Trust level can be narrowed down as very granular level of control is
possible. Allow only the intended traffic
Performance - Since, the the firewall features are kernel modules, it uses of modern days
compute power and can process quite large number of rules without affecting
performance. Further, it reduces hair pinning. Traffic do not need to leave the
Virtualization host, if the the destination in within the same host. It can reduce traffic and
limit to the TOR Switch when destination is in the same rack