Cloud Native Network Firewall (CNNF) is a Layer 4 network monitoring tool.
CNNF automatically discovers how entities in your environment communicate, and shows the communication mesh on Radar.
Radar has a container view, which shows the network topology for your containerized apps.
Radar also has a host view, which shows the network topology for hosts.
Defender monitors how your containers and hosts connect to each other in real-time.
Defender inspects connections before they’re set up.
After a connection is established, traffic flows directly between source and destination without any further oversight from Defender.
Defender adds iptables rules to observe TCP’s three-way handshake.
The three-way handshake sets up new connections using SYN messages.
For each pod or container IP address, Defender adds an iptables rule with the target set to NFQUEUE.
NFQUEUE is an iptables target which delegates the decision of how to handle a packet to a userspace program (in this case Defender).
When SYN messages arrive, Defender evaluates them to track connections.
From this vantage point, Defender can see all connections.
The following screenshot shows the mesh Radar draws for a typical microservices app.
Radar draws directed edges for each connection, and displays the associated port number.
An instance count for each node shows how many copies of the image are running as containers.
Black bubbles mean the runtime model is in enforcement mode.
Blue bubbles mean the runtime model is in learning mode.
You might have resources that interact with external, non-containerized services.
For example, a payment gateway might pass information to an external service to verify transactions.
Network objects represent sources and destinations.
Network objects can represent container images, subnets, and hosts.
You can create new network objects representing a range of IP addresses or a single IP.
Radar shows any connections established to the network object: