Flow Network Security

In the Ultra Transcenders books

NCP-MCI-7.5

Each book explains Flow Network Security in context, with comparison tables and the common traps.

Terms in this definition

• Nutanix AHV

  The hypervisor from Nutanix. Veeam's integration backs up its VMs to repositories and can restore to it from backups of vSphere, Hyper-V, AHV and other platforms.

• Legacy

  A label Databricks gives to older agent offerings: their documentation remains so that existing agents can be kept running or migrated, but new agents should avoid them.

Related terms

• Allow list

  The way Flow Network Security policies work: you name the permitted traffic, and anything not named is blocked by default. There is no option to name categories or subnets to block.

• DFW

  Application policies in this VMware NSX firewall become Flow Network Security ones when Nutanix Move converts them.

• Flow security policy

  Rules in Flow Network Security that target workloads instead of networks. Entities are chosen by category, so protection follows a VM wherever it moves.

• ICMP

  Ping runs on this protocol. Health checks on Flow Virtual Networking load balancers look for its unreachable replies, and Flow Network Security rules can permit it by name.

• Isolation policy

  A Flow Network Security rule set keeping categories of VMs from talking to each other, with multicast, broadcast and unknown-unicast blocked too.

• Microsegmentation

  Controlling VM-to-VM traffic by rules, delivered through Flow Network Security. It starts switched off and is enabled in Prism Central's settings.

• Network Controller

  Service inside Prism Central that powers Flow Virtual Networking and Flow Network Security Next-Gen. X-Large deployments turn it on automatically; X-Small ones cannot run it.

• NSX

  Flow Network Security can take over the rules from this VMware networking and security platform when they are moved across using Nutanix Move.