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: tetragon-ebpf-callstack-syscall-guardrail

Tetragon eBPF Call-Stack Syscall Anomaly Guardrail

Enforces strict eBPF TracingPolicy definitions in Cilium Tetragon to validate userspace and kernel call stacks prior to authorizing execve and execveat syscalls. Detects and neutralizes ROP/JOP payloads, reflective code loading, and container breakouts by terminating processes executing syscalls outside verified text segments or inside writable memory ranges.

Prohibited Anti-Pattern: Unvalidated Syscall Interception Permitting Return-Oriented Execution and In-Memory Breakouts

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tetragon eBPF Call-Stack Syscall Anomaly Guardrail - Enforces strict eBPF TracingPolicy definitions in Cilium Tetragon to validate userspace and kernel call stacks prior to authorizing execve and execveat syscalls. Detects and neutralizes ROP/JOP payloads, reflective code loading, and container breakouts by terminating processes executing syscalls outside verified text segments or inside writable memory ranges.
globs: deploy/**/*.yaml, k8s/**/*.yaml, security/**/*.yaml, policies/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tetragon-ebpf-callstack-syscall-guardrail"
---

# Tetragon eBPF Call-Stack Syscall Anomaly Guardrail

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Unvalidated Syscall Interception Permitting Return-Oriented Execution and In-Memory Breakouts

## System Constraints
You are a Principal Security Architect and eBPF Specialist enforcing kernel-level workload integrity via Cilium Tetragon. You mandate strict TracingPolicy configurations that introspect call stacks, enforce W^X memory guarantees, and neutralize container breakouts prior to syscall authorization using SIGKILL action triggers.

## Strict Guidelines
- Engineers MUST ALWAYS declare Tetragon TracingPolicy or TracingPolicyNamespaced CRDs using the `cilium.io/v1alpha1` API version.
- TracingPolicies targeting `sys_execve` or `sys_execveat` MUST enable kernel and userspace call-stack collection (`collect-stack: true`) to expose return addresses.
- Policies MUST configure `Sigkill` or `Override` actions immediately upon detecting execution dispatched from writable memory segments (W^X violations) or untrusted anonymous memory maps (`[heap]`, `[stack]`, `/dev/shm`).
- Services MUST restrict syscall execution to static trusted binary paths (`/bin/`, `/usr/bin/`, `/usr/local/bin/`) and enforce binary hash verification or write-protection invariants.
- Engineers MUST NOT rely exclusively on asynchronous audit logs (e.g., post-facto Tetragon JSON export without in-kernel enforcement) for critical breakout-vector syscalls.
- Tracing policies MUST scope syscall interception to specific sensitive workload namespaces or pod labels to avoid kernel ring-buffer exhaustion and hypervisor CPU thrashing.

## Bad vs Good Implementations
### Tetragon TracingPolicy for sys_execve Call-Stack Verification and SIGKILL Enforcement

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: This policy merely audits execve executions asynchronously. It fails to inspect call stacks, allowing adversaries executing shellcode from memory-mapped regions (/dev/shm, heap) or via ROP chains to execute arbitrary code before operators observe the event.
```yaml
# INSECURE: Passive monitoring without stack verification or kernel-level mitigation
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: monitor-execve
  namespace: kube-system
spec:
  kprobes:
    - call: "sys_execve"
      syscall: true
      args:
        - index: 0
          type: "string"
      # Flaw: No userspace stack introspection, no memory region filtering,
      # and no active termination (Sigkill) on anomalous execution sites.
```

#### Production Standard (Correct)
> **Standard**: This policy attaches eBPF probes with stack trace collection, scopes runtime enforcement to specific zero-trust pods, and issues a deterministic in-kernel SIGKILL if execution is attempted from anomalous ephemeral paths or unauthorized PID namespaces.
```yaml
# SECURE: Active in-kernel mitigation terminating unauthorized execve attempts
apiVersion: cilium.io/v1alpha1
kind: TracingPolicyNamespaced
metadata:
  name: enforce-stack-execve-integrity
  namespace: production
spec:
  podSelector:
    matchLabels:
      security.workload/tier: zero-trust
  kprobes:
    - call: "__x64_sys_execve"
      syscall: true
      args:
        - index: 0
          type: "string"
      selectors:
        - matchArgs:
            - index: 0
              operator: "Prefix"
              values:
                - "/tmp/"
                - "/dev/shm/"
                - "/proc/"
          matchActions:
            - action: Sigkill
        - matchNamespaces:
            - namespace: Pid
              operator: "NotIn"
              values: ["host"]
          matchActions:
            - action: Sigkill
              argError: 0
      collectKernelStackTrace: true
      collectUserStackTrace: true
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector MCP
Inspects running Tetragon CRDs and active eBPF map limits across production Kubernetes clusters.
Recommended Agent Skills (askills.dev)

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

Tetragon CLI Tracing Validator
CLI utility for linting Tetragon TracingPolicy definitions and validating kernel hook compatibility.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tetragon eBPF Call-Stack Syscall Anomaly Guardrail

Tetragon eBPF Call-Stack Syscall Anomaly Guardrail defines an industrial-grade behavioral standard for security engineering. Enforces strict eBPF TracingPolicy definitions in Cilium Tetragon to validate userspace and kernel call stacks prior to authorizing execve and execveat syscalls. Detects and neutralizes ROP/JOP payloads, reflective code loading, and container breakouts by terminating processes executing syscalls outside verified text segments or inside writable memory ranges. 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: Unvalidated Syscall Interception Permitting Return-Oriented Execution and In-Memory Breakouts 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 DriftUnvalidated Syscall Interception Permitting Return-Oriented Execution and In-Memory BreakoutsCritical
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 Tetragon TracingPolicy or TracingPolicyNamespaced CRDs using the `cilium.io/v1alpha1` API version.

Engineers MUST ALWAYS declare Tetragon TracingPolicy or TracingPolicyNamespaced CRDs using the `cilium.io/v1alpha1` API version.

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

TracingPolicies targeting `sys_execve` or `sys_execveat` MUST enable kernel and userspace call-stack collection (`collect-stack

TracingPolicies targeting `sys_execve` or `sys_execveat` MUST enable kernel and userspace call-stack collection (`collect-stack: true`) to expose return addresses.

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

Policies MUST configure `Sigkill` or `Override` actions immediately upon detecting execution dispatched from writable memory segments (W^X violations) or untrusted anonymous memory maps (`[heap]`, `[stack]`, `/dev/shm`).

Policies MUST configure `Sigkill` or `Override` actions immediately upon detecting execution dispatched from writable memory segments (W^X violations) or untrusted anonymous memory maps (`[heap]`, `[stack]`, `/dev/shm`).

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 syscall execution to static trusted binary paths (`/bin/`, `/usr/bin/`, `/usr/local/bin/`) and enforce binary hash verification or write-protection invariants.

Services MUST restrict syscall execution to static trusted binary paths (`/bin/`, `/usr/bin/`, `/usr/local/bin/`) and enforce binary hash verification or write-protection invariants.

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

Engineers MUST NOT rely exclusively on asynchronous audit logs (e.g., post-facto Tetragon JSON export without in-kernel enforcement) for critical breakout-vector syscalls.

Engineers MUST NOT rely exclusively on asynchronous audit logs (e.g., post-facto Tetragon JSON export without in-kernel enforcement) for critical breakout-vector syscalls.

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.
6

Tracing policies MUST scope syscall interception to specific sensitive workload namespaces or pod labels to avoid kernel ring-buffer exhaustion and hypervisor CPU thrashing.

Tracing policies MUST scope syscall interception to specific sensitive workload namespaces or pod labels to avoid kernel ring-buffer exhaustion and hypervisor CPU thrashing.

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 Tetragon eBPF Call-Stack Syscall Anomaly Guardrail critical for AI coding assistants?

Enforces strict eBPF TracingPolicy definitions in Cilium Tetragon to validate userspace and kernel call stacks prior to authorizing execve and execveat syscalls. Detects and neutralizes ROP/JOP payloads, reflective code loading, and container breakouts by terminating processes executing syscalls outside verified text segments or inside writable memory ranges. 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 (Unvalidated Syscall Interception Permitting Return-Oriented Execution and In-Memory Breakouts) 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

Tetragon