Everything is moving faster in the age of AI, and that includes security threats. What used to take attackers weeks to exploit can now happen in just a few minutes. Standard vulnerability scans that run on artifacts at rest can catch basic setup issues, but to detect an attack that's actively happening you need real-time runtime protection. Today, we’re introducing the Wiz Runtime Sensor add-on for Google Kubernetes Engine (GKE), in preview.
This built-in integration brings low-touch deployment, automated lifecycle management, enterprise credential security, and fleet-wide governance to Wiz's industry-leading eBPF runtime threat detection for both Standard and Autopilot GKE clusters. Security and platform engineering teams share common dilemmas when deploying in-cluster runtime defenses: Deployment and lifecycle friction : Deploying runtime agents often requires managing installations from third-party sources across dozens or hundreds of clusters.
Credential sprawl and security risks : Passing and rotating API keys as Kubernetes Secrets introduces administrative overhead and security risk. Fleet-wide enforcement gaps : Platform teams lack built-in policy controls to enforce that every new cluster has runtime sensors enabled before workloads are deployed and start receiving traffic. Performance and operational overhead : Without explicit and strategic resource limits, runtime agents can impact how much CPU and memory is available for your workloads and system functionality.
With the Wiz Runtime Sensor for GKE , Google Cloud and Wiz have minimized these operational barriers. The Runtime Sensor is now available in GKE as a first-party, managed platform add-on. The Wiz Runtime Sensor for GKE connects central security and platform engineering workflows by simplifying and automating the sensor lifecycle. Figure 1: High-level architecture showing credential sync, sensor deployment, and threat telemetry. With the add-on, GKE manages the sensor deployment, credential injection, and lifecycle updates.
