AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
devopscritical PriorityID: tetragon-ebpf-namespace-escape-quarantine-standard

Cilium Tetragon eBPF Synchronous Namespace Escape Quarantine Standard

Mandates the deployment of Cilium Tetragon TracingPolicies configured for synchronous in-kernel enforcement (action: Sigkill) upon unauthorized container namespace boundary traversal, such as setns and unshare invocations. Prevents time-of-check to time-of-use (TOCTOU) container breakouts by replacing asynchronous user-space alerting with immediate eBPF-driven process termination and real-time structured audit event emission.

Prohibited Anti-Pattern: Post-Facto Asynchronous Alerting on Namespace Traversal Syscalls Without In-Kernel SIGKILL Enforcement

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Cilium Tetragon eBPF Synchronous Namespace Escape Quarantine Standard - Mandates the deployment of Cilium Tetragon TracingPolicies configured for synchronous in-kernel enforcement (action: Sigkill) upon unauthorized container namespace boundary traversal, such as setns and unshare invocations. Prevents time-of-check to time-of-use (TOCTOU) container breakouts by replacing asynchronous user-space alerting with immediate eBPF-driven process termination and real-time structured audit event emission.
globs: k8s/**/*.yaml, deploy/tetragon/**/*.yaml, crds/**/*.yaml, helm/**/*.yaml, policies/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tetragon-ebpf-namespace-escape-quarantine-standard"
---

# Cilium Tetragon eBPF Synchronous Namespace Escape Quarantine Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Post-Facto Asynchronous Alerting on Namespace Traversal Syscalls Without In-Kernel SIGKILL Enforcement

## System Constraints
You are a Principal Software Architect enforcing the Tetragon eBPF Container Namespace Escape Quarantine Standard. You must ensure all container security policies leverage kernel-level synchronous containment (action: Sigkill) on dangerous namespace manipulation syscalls (e.g., setns, unshare, mount) rather than passive, asynchronous logging. Never allow workloads to operate under monitor-only mode for privilege boundary transitions.

## Strict Guidelines
- Engineers MUST ALWAYS declare 'action: Sigkill' on kernel probe hooks targeting namespace traversal syscalls ('__x64_sys_setns', '__x64_sys_unshare', and mount operations) executed within untrusted container namespaces.
- Engineers MUST NOT rely on asynchronous user-space security agents (such as log scrapers or auditd daemons) for container escape mitigation; policy evaluation and process execution termination MUST occur synchronously inside eBPF kernel space.
- TracingPolicy resources SHOULD explicitly scope target selectors to non-host namespace processes using 'matchNamespaces' or 'matchPIDs' filters to prevent unintended disruption to kubelet, systemd, or container runtime daemons.
- Services MUST route the Tetragon gRPC audit stream to dedicated SIEM/SOC event pipelines using structured JSON logging containing process lineage (parent PID, binary path, namespaces, and security context).
- Components NEVER permit execution of binaries that alter mount namespaces or pivot root filesystems without an explicit, pre-authorized cryptographic signature or hardened seccomp exception profile.

## Bad vs Good Implementations
### Tetragon TracingPolicy Namespace Escape Enforcement

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The policy omits synchronous kernel enforcement ('action: Sigkill'). By only recording or using default event emission, the setns syscall succeeds, allowing an attacker to escape to the host namespace before an operator or user-space daemon can react.
```yaml
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: audit-namespace-escape
spec:
  kprobes:
    - call: "__x64_sys_setns"
      syscall: true
      args:
        - index: 0
          type: "int"
        - index: 1
          type: "int"
      # Flaw: Missing synchronous termination action; attacker completes escape
      # before asynchronous user-space logging agent can process the alert.
      selectors:
        - matchNamespaces:
            - namespace: default
```

#### Production Standard (Correct)
> **Standard**: The hardened TracingPolicy executes 'action: Sigkill' directly in the eBPF kernel layer before the syscall can alter the target process namespace descriptor. It also enforces structured rate-limited telemetry via 'action: Post' for immediate forensic analysis.
```yaml
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: block-namespace-escape
spec:
  kprobes:
    - call: "__x64_sys_setns"
      syscall: true
      args:
        - index: 0
          type: "int"
        - index: 1
          type: "int"
      selectors:
        - matchNamespaces:
            - namespace: default
            - namespace: production
          matchArgs:
            - index: 1
              operator: "Mask"
              values:
                - "0x00020000" # CLONE_NEWUSER
                - "0x00040000" # CLONE_NEWPID
                - "0x00080000" # CLONE_NEWNET
                - "0x00000020" # CLONE_NEWNS
          # Synchronously terminates the process in kernel space before syscall completion
          matchActions:
            - action: Sigkill
            - action: Post
              rateLimit: "10/s"
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Kubernetes Resource Inspector
Inspects and validates Tetragon TracingPolicy CRDs and cluster-wide security policies.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Cilium Tetragon CLI
CLI utility for interacting with Tetragon eBPF sensors, validating TracingPolicy schemas, and tailing synchronous kill audit events.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Cilium Tetragon eBPF Synchronous Namespace Escape Quarantine Standard

Cilium Tetragon eBPF Synchronous Namespace Escape Quarantine Standard defines an industrial-grade behavioral standard for devops engineering. Mandates the deployment of Cilium Tetragon TracingPolicies configured for synchronous in-kernel enforcement (action: Sigkill) upon unauthorized container namespace boundary traversal, such as setns and unshare invocations. Prevents time-of-check to time-of-use (TOCTOU) container breakouts by replacing asynchronous user-space alerting with immediate eBPF-driven process termination and real-time structured audit event emission. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Post-Facto Asynchronous Alerting on Namespace Traversal Syscalls Without In-Kernel SIGKILL Enforcement Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftPost-Facto Asynchronous Alerting on Namespace Traversal Syscalls Without In-Kernel SIGKILL EnforcementCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS declare 'action

Engineers MUST ALWAYS declare 'action: Sigkill' on kernel probe hooks targeting namespace traversal syscalls ('__x64_sys_setns', '__x64_sys_unshare', and mount operations) executed within untrusted container namespaces.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT rely on asynchronous user-space security agents (such as log scrapers or auditd daemons) for container escape mitigation

Engineers MUST NOT rely on asynchronous user-space security agents (such as log scrapers or auditd daemons) for container escape mitigation; policy evaluation and process execution termination MUST occur synchronously inside eBPF kernel space.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

TracingPolicy resources SHOULD explicitly scope target selectors to non-host namespace processes using 'matchNamespaces' or 'matchPIDs' filters to prevent unintended disruption to kubelet, systemd, or container runtime daemons.

TracingPolicy resources SHOULD explicitly scope target selectors to non-host namespace processes using 'matchNamespaces' or 'matchPIDs' filters to prevent unintended disruption to kubelet, systemd, or container runtime daemons.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST route the Tetragon gRPC audit stream to dedicated SIEM/SOC event pipelines using structured JSON logging containing process lineage (parent PID, binary path, namespaces, and security context).

Services MUST route the Tetragon gRPC audit stream to dedicated SIEM/SOC event pipelines using structured JSON logging containing process lineage (parent PID, binary path, namespaces, and security context).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER permit execution of binaries that alter mount namespaces or pivot root filesystems without an explicit, pre-authorized cryptographic signature or hardened seccomp exception profile.

Components NEVER permit execution of binaries that alter mount namespaces or pivot root filesystems without an explicit, pre-authorized cryptographic signature or hardened seccomp exception profile.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Cilium Tetragon eBPF Synchronous Namespace Escape Quarantine Standard critical for AI coding assistants?

Mandates the deployment of Cilium Tetragon TracingPolicies configured for synchronous in-kernel enforcement (action: Sigkill) upon unauthorized container namespace boundary traversal, such as setns and unshare invocations. Prevents time-of-check to time-of-use (TOCTOU) container breakouts by replacing asynchronous user-space alerting with immediate eBPF-driven process termination and real-time structured audit event emission. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Post-Facto Asynchronous Alerting on Namespace Traversal Syscalls Without In-Kernel SIGKILL Enforcement) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related DEVOPS Rules

View all rules →
devops
86

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

devops
118

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

devops
40

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

Cilium