In this multi-part series, the goal is to first familiarize you with the solution and then provide guidance on preparing to deploy Flow Network Security and help you learn the constructs that form your policy framework.
So, what is Flow Network Security? By now, you may have heard the name, read about it or had a conversation about it with a Nutanix employee. First off, and in most basic terms, Flow Network Security is built-in security for workloads that run on Nutanix AHV, our native hypervisor. Think of it more as a feature or solution rather than a separate “product”.
While AHV has been available for many years, one thing became obvious as customers were looking to have more security options in their Nutanix environment; we didn’t have a Nutanix-developed solution to provide network security.
Enter microsegmentation. Network virtualization got its beginning as a Stanford University research project that ultimately became a startup and commercial solution from Nicira, circa 2007. VMware acquired Nicira in 2012 and the solution became, as you may know, NSX, which offered software-defined networking and microsegmentation functionality. Since this time, other software companies have brought their own solutions to market.
होस्ट: एंडी व्हाइटसाइड
सह-मेजबान: हार्वे ग्रीन
सह-मेजबान: फिलिप सेलर्स
सह-मेज़बान: जिराह कॉक्स
Why Network Security Has to Move Inside the Data Center
For decades, network investment focused on performance and density rather than security. The same NICs and switches used 20 or 30 years ago are still in place, and hardening the perimeter while leaving the inside of the network open remains common thinking. Adding real control inside the network used to mean siloed designs, dedicated firewalls for individual applications, or far more complex network architectures.
Rising ransomware activity makes that approach harder to defend. Attacks are becoming more frequent and more successful, and some insurers have even considered pulling back from writing cyber insurance. Organizations need a plan beyond recovering from backups and snapshots after an infection has already spread.
What Flow Network Security Is
Flow Network Security is built-in security for workloads running on Nutanix AHV, the native hypervisor. It is best thought of as a feature of the platform rather than a separate product. Before it existed, Nutanix had no native network security option, and customers who wanted microsegmentation had to bring in third-party technology, which added cost and complexity.
Microsegmentation itself is not new. Network virtualization grew out of research that led to Nicira, which VMware acquired and turned into NSX. Flow brings the same idea directly into AHV.
Simple to Turn On, Safe to Learn With
The enforcement capability is already present on every running AHV instance, so there is nothing to install or deploy. The control plane lives in Prism Central and is enabled with a single checkbox. After that, the work is writing policies that allow, block, or monitor traffic. In effect, it places a firewall in front of every virtual machine network interface.
Turning it on does not cut off traffic. Flow can start in a monitoring mode and show what is actually flowing between workloads, which helps teams who are unsure what policies to write. A clear interface shows both what has been configured and what has been discovered, so decisions about what to allow or deny are based on observed behavior.
Visibility Into Applications Nobody Has Mapped
Many operations teams cannot say exactly which ports and communication paths their applications need. Software vendors often cannot articulate it, and in-house developers rarely document everything their applications consume. Seeing real traffic addresses that problem directly, and it gives teams concrete information to take back to vendors about what an application requires.
Protecting East-West Traffic
Traditional network segmentation does little for east-west traffic, the movement between workloads on the same switch or even the same hypervisor, which may never touch a physical switch at all. Because Flow operates at the virtual NIC level, it can see and control that traffic without in-guest agents.
This matters because ransomware rarely lands on the system with the most valuable credentials. Attackers move laterally from desktop to desktop and server to server looking for more access. Limiting each workload to the communication it needs shrinks what an attacker can reach. The same approach supports zero trust thinking, and policies can even vary based on who is logged in, so a vendor and an administrator receive different access on the same machine.
Working Alongside Firewalls and Automation
Out of the box, Flow is a layer 4 firewall, evaluating source and destination addresses, subnets, protocols, and ports. It does not replace next-generation firewalls. Those tools offer deep inspection but are expensive and limited in throughput, so they are best reserved for traffic that truly needs web session inspection, with Flow handling broad filtering for all virtual machines. Traffic can also be redirected to partner appliances when deeper inspection is needed.
Flow also fits automation well. Policies for categories such as database servers or public web servers can be written once and applied to new virtual machines through an automation run, API call, or service request, so a workload is secured from the moment it is deployed. And it works on the network and VMs already in place, with no new VLANs, routers, or redesign required.