Introduction: The Growing Threat of Container Escape on Virtual Private Servers

In the modern cloud-native landscape, Virtual Private Servers (VPS) frequently host containerized workloads using platforms like Docker. While containerization offers unparalleled flexibility and resource efficiency, it also introduces unique security paradigms. One of the most critical threats facing DevSecOps teams today is container privilege escalation, often leading to a complete container escape.

When an attacker compromises a containerized application, their immediate next step is usually to exploit kernel vulnerabilities, misconfigurations, or weak capabilities to gain root access on the host VPS. Traditional security tools that rely on user-space monitoring or periodic log analysis often fail to detect these rapid, low-level exploits. To safeguard infrastructure, organizations require deep, real-time visibility into the operating system kernel. This is where the combination of eBPF (Extended Berkeley Packet Filter) and Cilium Tetragon becomes a game-changer.

---

Understanding the Mechanics of Container Privilege Escalation

Before diving into the solution, it is vital to understand how attackers achieve privilege escalation within Docker containers running on a VPS. Containers share the host operating system's kernel. Isolation is maintained through Linux namespaces, cgroups, and capabilities. However, this isolation can be breached through several vectors:

Misconfigured Container Runtimes: Running containers with the --privileged flag or improperly assigning dangerous Linux capabilities such as CAP_SYS_ADMIN, CAP_SYS_PTRACE, or CAP_CHOWN.
Kernel Vulnerabilities: Exploiting unpatched vulnerabilities in the host Linux kernel (e.g., Dirty COW, Dirty Pipe) to bypass namespace boundaries directly from within a non-privileged container.
Exposed Docker Sockets: Mounting /var/run/docker.sock inside a container allows an attacker to issue commands directly to the host's Docker daemon, effectively granting them the ability to spin up new containers with root access to the host filesystem.

Warning: Once an attacker achieves execution capabilities on the host system, the entire VPS, along with adjacent network infrastructure, must be considered fully compromised.

---

What is eBPF and Why is it Revolutionary for Security?

Traditionally, security agents monitored system behavior by either modifying kernel source code or loading dynamic kernel modules (LKM). Both approaches carry inherent risks: a bug in a kernel module can crash the entire system, leading to catastrophic downtime on production VPS instances.

eBPF (Extended Berkeley Packet Filter) revolutionizes this paradigm by allowing developers to run sandboxed programs inside the Linux kernel without changing kernel source code or loading risky modules. It provides:

Safety: eBPF programs are strictly validated by an in-kernel verifier to ensure they cannot crash the system or loop infinitely.
High Performance: Because eBPF runs directly inside the kernel context, it eliminates the expensive context-switching overhead between user-space and kernel-space typical of traditional monitoring tools.
Absolute Visibility: eBPF can hook into almost any kernel function, system call, or tracepoint, providing an un-bypassable stream of truth regarding system behavior.

---

Enter Tetragon: Kernel-Level Security Enforcement

While eBPF provides the underlying technology, writing raw eBPF programs for security monitoring is complex and highly specialized. Cilium Tetragon solves this by providing a powerful, out-of-the-box security observability and runtime enforcement platform powered by eBPF.

Tetragon does not merely look at system calls (syscalls) at the entry point, which can be vulnerable to TOCTOU (Time-of-Check to Time-of-Use) attacks or obfuscation. Instead, Tetragon hooks deeply into the Linux kernel's internal subsystems, such as the Linux Security Modules (LSM) framework, process lifecycles, and network stacks. This allows Tetragon to detect not just *what* an application is asking to do, but *how* the kernel is actually executing it in real-time.

---

Architecture: Implementing eBPF + Tetragon on a VPS hosting Docker

Deploying Tetragon on a standard Linux VPS hosting Docker containers creates a robust, multi-layered defensive shield. Tetragon runs as a daemon on the host system (or within a specialized management container), injecting its eBPF probes directly into the host kernel.

Because all Docker containers on that VPS share the same host kernel, Tetragon automatically gains complete visibility into every single container without requiring any sidecars, agents, or modifications inside the container images themselves. This architecture ensures a zero-trust runtime environment with zero friction for developers.

---

Detecting Privilege Escalation with Tetragon Polices

Tetragon utilizes custom resources called TracingPolicies to define what behavior should be monitored or blocked. Let's look at how Tetragon detects specific privilege escalation indicators:

1. Monitoring Namespace Modifications and Escapes

An attacker attempting a container escape will often try to join the host namespaces (such as the PID or Network namespace). Tetragon can monitor sensitive system calls like setns or unshare. If a process inside a Docker container executes these calls unexpectedly, Tetragon immediately flags the event with full context, including the container ID, binary path, and user ID.

2. Tracking Binary Execution and Privilege Changes

Tetragon natively tracks process lifecycles (execve). If a process inside a container suddenly changes its effective user ID (EUID) from a non-root user to root (UID 0)—for instance, via a exploited SUID binary or local kernel exploit—Tetragon detects the mismatch between the parent process context and the new execution state instantly.

3. Protecting Sensitive Host Filesystems

If a VPS configuration inadvertently exposes host paths (like /etc or /root) to a container via volumes, Tetragon can enforce file integrity policies. Any unauthorized attempt by a container process to read or write to these sensitive paths triggers an immediate security alert or an automated termination signal to the offending process.

---

Step-by-Step Guide: Deploying Tetragon for Docker Monitoring

Setting up Tetragon on your VPS to secure Docker workloads involves a few straightforward steps:

Step 1: Verify Kernel Compatibility

Ensure your VPS runs a modern Linux kernel (recommended version 5.4 or higher) with BTF (BPF Type Format) enabled. You can check this by running:

ls /sys/kernel/btf/vmlinux

Step 2: Install Tetragon via Docker or Binary

You can run Tetragon directly as a privileged container on your host to monitor the rest of the ecosystem. Run the following command to start Tetragon:

docker run --name tetragon --privileged --pid=host -v /sys/kernel/debug:/sys/kernel/debug -v /var/run/docker.sock:/var/run/docker.sock quay.io/cilium/tetragon:latest

Step 3: Analyze the Real-Time Security Log

Tetragon streams its security events in JSON format to /var/log/tetragon/tetragon.log. You can monitor process executions and privilege adjustments in real-time by viewing this structured output. These logs can easily be forwarded to a SIEM system or an alerting pipeline (such as Slack or Webhooks) for immediate incident response.

---

Conclusion: Proactive Security for the Container Era

Relying on traditional signature-based or user-space security solutions on your VPS leaves a dangerous blind spot that modern attackers easily exploit. By harnessing the power of eBPF through Cilium Tetragon, you achieve deep kernel-level observability. This enables your security operations to detect container privilege escalation and escape attempts the exact millisecond they occur, ensuring your core infrastructure remains resilient, compliant, and secure.

Securing the Cloud: Leveraging eBPF and Tetragon for Real-Time Container Privilege Escalation Detection on VPS