index series
Cloud-Native Runtime Security with Wazuh
Extending Wazuh into Kubernetes and containers: kernel-level eBPF telemetry, cluster hardening across seven compliance frameworks, and the container registry as a sensor.
Wazuh was built for hosts. These posts extend it into cloud-native environments from the kernel up: Tetragon eBPF telemetry for runtime visibility, a Helm chart that hardens Kubernetes across seven compliance frameworks, and Harbor plus Trivy turning the container registry into a sensor. Each post ships a working artifact and builds on the one before it.
- Closing the Kernel-Level Gap in Wazuh: an eBPF Sidecar with Tetragon A custom Wazuh rule pack and reproducible Docker lab that pairs a stock Wazuh agent with a Tetragon eBPF sidecar to catch what stock Wazuh cannot: short-lived process exec, fileless memfd payloads, sub-second TCP connects, kernel module loads, bpf() syscall use, sensitive-file argv reads, setuid escalation. 1 decoder family, 15 rules, 4 distros, 1.59M events validated.
- Wazuh on K8s: 7 Frameworks, Auto-Remediation, One Chart An open-source Helm chart that wraps Wazuh agents with Kubernetes-native enforcement: CIS, NIST 800-53, PCI-DSS, HIPAA, SOC2, MITRE ATT&CK runtime detection, admission webhook, and a remediation CronJob: all from one deploy.
- Registry as a Sensor: Wiring Harbor and Trivy into Wazuh, with a Wolfi Agent to Prove It A Harbor→Wazuh webhook bridge, a 25-rule supply-chain detection pack with three correlation chains (vulnerable image deployed, unscanned image deployed, already-deployed image found vulnerable), and a Wazuh agent rebuilt from source on Wolfi that scored 0 CVEs against the official manager image's 567. Validated live on Wazuh 4.14.5: 23 of 25 rules fire from one script, 40 alerts.
Start reading →Part 1: Closing the Kernel-Level Gap in Wazuh: an eBPF Sidecar with Tetragon