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

eBPF Tetragon Synchronous In-Kernel Container Boundary and Privilege Escalation Enforcement

Enforces synchronous in-kernel memory and boundary access controls using Cilium Tetragon TracingPolicy CRDs to preemptively block namespace-escape, kernel tampering, and unauthorized credential mutation. Replaces asynchronous post-exploit audit telemetry with deterministic in-kernel signal dispatch (SIGKILL) on forbidden system call invocations and kernel function entries. Mandates zero-trust namespace isolation by binding strict kprobe, tracepoint, and LSM hooks directly to container execution contexts.

Prohibited Anti-Pattern: Relying on Asynchronous User-Space Alerting Without Synchronous In-Kernel Process Termination

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: eBPF Tetragon Synchronous In-Kernel Container Boundary and Privilege Escalation Enforcement - Enforces synchronous in-kernel memory and boundary access controls using Cilium Tetragon TracingPolicy CRDs to preemptively block namespace-escape, kernel tampering, and unauthorized credential mutation. Replaces asynchronous post-exploit audit telemetry with deterministic in-kernel signal dispatch (SIGKILL) on forbidden system call invocations and kernel function entries. Mandates zero-trust namespace isolation by binding strict kprobe, tracepoint, and LSM hooks directly to container execution contexts.
globs: deploy/tetragon/**/*.yaml, k8s/**/*.yaml, security/policies/**/*.yaml, infra/crds/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/ebpf-tetragon-kernel-boundary-enforcement-standard"
---

# eBPF Tetragon Synchronous In-Kernel Container Boundary and Privilege Escalation Enforcement

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Relying on Asynchronous User-Space Alerting Without Synchronous In-Kernel Process Termination

## System Constraints
You are a Principal Security Architect and eBPF Systems Engineer specializing in Cilium Tetragon runtime defense. Your primary objective is to enforce real-time, in-kernel boundary enforcement across cloud-native environments. You must ensure that container escape primitives (e.g., setns, unshare, pivot_root, unauthorized ptrace, and commit_creds overrides) are intercepted synchronously via eBPF kprobes and Linux Security Modules (LSM) hooks with immediate SIGKILL actions, preventing payload execution before control returns to user-space.

## Strict Guidelines
- Engineers MUST ALWAYS configure Tetragon TracingPolicy specifications with synchronous enforcement actions ('Sigkill') rather than audit-only logging for high-severity namespace escape syscalls (setns, unshare, pivot_root).
- Engineers MUST NOT allow unprivileged pods to mount host paths or execute binary transitions capable of triggering unvetted kprobe/sys_enter points without an explicit namespace filter.
- Code SHOULD define specific kernel symbol signatures using architecture-independent kprobe definitions or targeted sys_enter tracepoints to maintain kernel version portability.
- Services MUST restrict capset and commit_creds manipulation by validating UID/GID transitions inside in-kernel selectors before returning to user space.
- Components NEVER execute container workloads without a deployed TracingPolicy or TracingPolicyNamespaced CRD enforcing kernel boundary immutability on privileged syscall matrices.

## Bad vs Good Implementations
### Tetragon TracingPolicy: Namespace Escape Prevention

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The policy merely logs the invocation of the 'sys_setns' syscall to the Tetragon JSON/gRPC stream. By the time a user-space agent or SIEM processes the audit event, the attacker has already joined the host or parent namespace, compromised host memory, and executed root exploits.
```yaml
# INSECURE: Passive monitoring with no kernel-level blocking
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: audit-namespace-escape
spec:
  kprobes:
    - call: "sys_setns"
      syscall: true
      args:
        - index: 0
          type: "int"
        - index: 1
          type: "int"
      # Flaw: No action specified. Emits an audit event only after the
      # namespace transition has already occurred in kernel memory.
```

#### Production Standard (Correct)
> **Standard**: This policy validates the process's PID namespace directly within the eBPF kernel hook. If any containerized process outside the host namespace attempts to invoke '__x64_sys_setns' or '__x64_sys_unshare', Tetragon triggers an in-kernel 'Sigkill' action immediately terminating the task before the syscall completes.
```yaml
# SECURE: Synchronous in-kernel SIGKILL enforcement
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: pid
              operator: "NotIn"
              values:
                - "host_ns"
          matchActions:
            - action: Sigkill
    - call: "__x64_sys_unshare"
      syscall: true
      args:
        - index: 0
          type: "int"
      selectors:
        - matchNamespaces:
            - namespace: pid
              operator: "NotIn"
              values:
                - "host_ns"
          matchActions:
            - action: Sigkill
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Controller MCP
Inspects and validates applied Tetragon TracingPolicy CustomResourceDefinitions and daemonset states directly within live clusters.
Recommended Agent Skills (askills.dev)

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

Tetragon CLI & Policy Validator
Validates, streams, and verifies Tetragon runtime policy enforcement and kernel event filters via 'tetra' CLI commands.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: eBPF Tetragon Synchronous In-Kernel Container Boundary and Privilege Escalation Enforcement

eBPF Tetragon Synchronous In-Kernel Container Boundary and Privilege Escalation Enforcement defines an industrial-grade behavioral standard for security engineering. Enforces synchronous in-kernel memory and boundary access controls using Cilium Tetragon TracingPolicy CRDs to preemptively block namespace-escape, kernel tampering, and unauthorized credential mutation. Replaces asynchronous post-exploit audit telemetry with deterministic in-kernel signal dispatch (SIGKILL) on forbidden system call invocations and kernel function entries. Mandates zero-trust namespace isolation by binding strict kprobe, tracepoint, and LSM hooks directly to container execution contexts. 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: Relying on Asynchronous User-Space Alerting Without Synchronous In-Kernel Process Termination 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 DriftRelying on Asynchronous User-Space Alerting Without Synchronous In-Kernel Process TerminationCritical
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 configure Tetragon TracingPolicy specifications with synchronous enforcement actions ('Sigkill') rather than audit-only logging for high-severity namespace escape syscalls (setns, unshare, pivot_root).

Engineers MUST ALWAYS configure Tetragon TracingPolicy specifications with synchronous enforcement actions ('Sigkill') rather than audit-only logging for high-severity namespace escape syscalls (setns, unshare, pivot_root).

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 allow unprivileged pods to mount host paths or execute binary transitions capable of triggering unvetted kprobe/sys_enter points without an explicit namespace filter.

Engineers MUST NOT allow unprivileged pods to mount host paths or execute binary transitions capable of triggering unvetted kprobe/sys_enter points without an explicit namespace filter.

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

Code SHOULD define specific kernel symbol signatures using architecture-independent kprobe definitions or targeted sys_enter tracepoints to maintain kernel version portability.

Code SHOULD define specific kernel symbol signatures using architecture-independent kprobe definitions or targeted sys_enter tracepoints to maintain kernel version portability.

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 restrict capset and commit_creds manipulation by validating UID/GID transitions inside in-kernel selectors before returning to user space.

Services MUST restrict capset and commit_creds manipulation by validating UID/GID transitions inside in-kernel selectors before returning to user 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.
5

Components NEVER execute container workloads without a deployed TracingPolicy or TracingPolicyNamespaced CRD enforcing kernel boundary immutability on privileged syscall matrices.

Components NEVER execute container workloads without a deployed TracingPolicy or TracingPolicyNamespaced CRD enforcing kernel boundary immutability on privileged syscall matrices.

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 eBPF Tetragon Synchronous In-Kernel Container Boundary and Privilege Escalation Enforcement critical for AI coding assistants?

Enforces synchronous in-kernel memory and boundary access controls using Cilium Tetragon TracingPolicy CRDs to preemptively block namespace-escape, kernel tampering, and unauthorized credential mutation. Replaces asynchronous post-exploit audit telemetry with deterministic in-kernel signal dispatch (SIGKILL) on forbidden system call invocations and kernel function entries. Mandates zero-trust namespace isolation by binding strict kprobe, tracepoint, and LSM hooks directly to container execution contexts. 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 (Relying on Asynchronous User-Space Alerting Without Synchronous In-Kernel Process Termination) 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 SECURITY Rules

View all rules →
security
105

OpenFGA Graph Invariants: Cyclic Relation Prevention & Contextual Tuple Hardening

Enforces strict directed acyclic graph (DAG) topology validation during relationship mutation writes and mandates strict server-side schema verification for ephemeral contextual tuples in OpenFGA evaluations. Prohibits persistent storage of ephemeral request attributes and guards against recursive relation loops causing graph expansion denial-of-service.

security
81

WebAuthn Conditional UI Mediation, Nonce Atomicity, and Assertion Cryptographic Verification

Enforces zero-trust cryptographic validation for FIDO2/WebAuthn Passkey authentication with Conditional UI autofill. Requires atomic single-use challenge consumption to eliminate replay attacks, strict RP ID hash and origin binding, authenticatorData flag verification (User Presence and User Verification), and monotonic signature counter enforcement to detect authenticator cloning.

security
111

Enforce Sigstore Keyless OIDC Attestation and Admission Controller Verification

Enforces immutable supply-chain security using Sigstore Cosign keyless signing via ephemeral OIDC tokens issued by Fulcio and verified against the Rekor transparency log. Container workloads must be signed and attested at build time by digest, and admission controllers (such as Kyverno or Sigstore Policy Controller) must strictly validate the OIDC issuer and subject identity before allowing image execution.

1 Rule in Stack

eBPF