Kubescape 4.0: Kubernetes Security Meets the AI Agent Era
kubescapekubernetessecurityebpfcncfruntime-detectionai-agents
Loading…
At KubeCon EU in Amsterdam on 26 March 2026, the Kubescape team released version 4.0 of the open-source Kubernetes security platform. The release general availability for two major capabilities: runtime threat detection powered by eBPF, and a dedicated security scanner for CNCF Sandbox's KAgent CRDs. The architecture also sheds the host-sensor DaemonSet that required elevated privileges in previous versions, replacing it with a unified node-agent that runs with standard permissions.
The headline features are runtime threat detection and KAgent security scanning, but the architectural cleanup is equally significant.
Previous versions of Kubescape focused on configuration scanning: checking whether deployments violated CIS benchmarks, whether RBAC policies were too permissive, or whether containers ran as root. Version 4.0 adds runtime threat detection using eBPF probes that monitor actual system behaviour: network connections, process execution, file access patterns, and system calls.
The detection engine uses CEL (Common Expression Language) rules rather than traditional signature matching. This approach filters over 95%% of CVE-related noise that plagues signature-based runtime scanners, surfacing only behaviourally significant threats.
KAgent, the CNCF Sandbox project for defining AI agent workloads as Kubernetes custom resources, introduces a new attack surface. An AI agent with access to cluster APIs can inspect secrets, modify deployments, or exfiltrate data through permitted network paths.
Kubescape 4.0 ships a scanner that evaluates KAgent CRDs against 15 Rego policies covering 42 security-critical configuration points. These policies check privilege boundaries, network access rules, secret access permissions, and resource limits for agent workloads.
A companion KAgent plugin allows AI agents themselves to query the cluster's security posture at runtime. An agent about to execute a deployment change can check whether its target namespace has active threat alerts, review the RBAC permissions it holds, and verify that no runtime anomalies have been detected on the target pods.
The host-sensor DaemonSet, which required privileged access to nodes in earlier versions, has been removed entirely. Its functionality is now handled by a unified node-agent that runs with standard Kubernetes permissions. This eliminates the need for elevated privileges and removes the security concern of running high-privilege DaemonSets in production clusters.
The new Kubescape Storage component uses an Aggregated API to decouple security metadata from etcd. Security scan results, compliance reports, and threat detection data are stored separately from Kubernetes state, reducing etcd load and improving query performance.
Kubescape 4.0 supports the following frameworks out of the box:
# Install Kubescape CLI
curl -s https://raw.githubusercontent.com/kubescape/kubescape/master/install.sh | bash
# Scan a framework
kubescape scan framework nsa --exclude-namespaces kube-system
# Scan with KAgent controls
kubescape scan framework custom --controls 'KAgent-*'
```text
## CNCF and community
Kubescape graduated to CNCF incubating status in January 2025. The project has accumulated over 11,000 GitHub stars and is used by more than 25,000 organisations, including Intel, AWS, and Bitnami. Version 4.0 is available now from the [GitHub releases page](https://github.com/kubescape/kubescape/releases/tag/v4.0.0).
The release arrives at a moment when Kubernetes clusters are increasingly running AI agent workloads alongside traditional applications. The security model that assumed all workloads were defined at deploy time no longer holds. Kubescape 4.0 acknowledges this shift by adding runtime detection and agent-specific scanning alongside its existing configuration checks.