---
name: "falco-kubernetes-threat-detection"
description: "Detect anomalous runtime behaviors and zero-day threats in containers with Falco."
metadata:
  author: "Falco"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "install falco kubernetes"
  - "write custom falco rule"
  - "detect shell spawned in container"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Falco eBPF Runtime Threat Detection in Kubernetes

Instruments Kubernetes clusters with Falco eBPF engine: monitoring Linux syscalls, authoring custom Falco YAML rules, detecting shell spawns in containers, and streaming alert webhooks.

## When to Invoke
Invoke this skill whenever you need to:
- install falco kubernetes
- write custom falco rule
- detect shell spawned in container

## Execution SOP & Rules
1. Deploy Falco as a DaemonSet using modern eBPF probe drivers (driver.kind=ebpf).
2. Define detection rules with condition, output, priority, and tags in custom rules files.
3. Alert on dangerous actions: container interactive shell spawns, modifying binary directories.
4. Integrate Falcosidekick to forward high-priority alerts to incident response channels.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.