Solution Brief

The guide to host-based Kubernetes visibility

Correlate process-to-network data.

Extracting security data no one else can

We need to know which process sent out this HTTP call on Tuesday at 3:15 p.m. from host A. How can we possibly get this info?

The largest companies in the world with dozens of security tools are still flying blind when it comes to securing Kubernetes. Why?

Because they are relying on traditional tooling that only see’s IPs. But IP addresses are useless information in cloud-native environments, they can change by the minute.

What they need instead is the ability to look at the network and node processes at the same time, mapping one layer to the other. Break down traditional silos around networking and process level observability. 

Meet Tetragon, offering host-based Kubernetes visibility, mapping process information (down to the binary and parent id) to the network traffic they create.

  • Saved thousands of people hours
  • Ease of deployment, even in cloud
  • Crucial insights for security and compliance teams

Tetragon’s eBPF deployment saves hundreds if not thousands of people hours, and doesn’t add any equipment to your racks.

Learn more

Explore the protocols Tetragon parses, cloud compatibility, and extensive filtering in the solution brief.

Learn how Tetragon’s lightweight eBPF sensor captures K8s telemetry down to the binary, tying process to network data with no application changes.

Decode DNS, TLS, HTTP, UDP, TCP , and more while matching to process ancestry information, all with Kubernetes identity-aware metadata (labels, pod names, etc).

Read the solution brief and get under the hood with Tetragon.