Kubernetes Compliance
Security and reliability rules purpose-built for Kubernetes — privileged containers, missing probes, dangerous capabilities, and more.
Sample dashboard
Kubernetes Compliance, at a glance
Clusters connected
3
EKS, GKE, on-prem
Security findings
7
Privileged containers, etc.
Reliability findings
4
Missing probes, SPOFs
Namespaces scanned
56
Excludes system namespaces
Illustrative figures — your dashboard reflects your own connected data.
Kubernetes security issues rarely look like traditional cloud misconfigurations — privileged containers, host namespace sharing, missing liveness probes, and single-replica production workloads need rules built specifically for how Kubernetes actually runs, from first principles.
Purpose-built rules cover both security (privileged/root containers, hostPath mounts, dangerous capabilities) and reliability (missing probes, single points of failure, CrashLoopBackOff), evaluated against any cluster — EKS, AKS, GKE, on-premises, or k3s — with system namespaces inventoried but not flagged for legitimately privileged components like kube-proxy.
How it works
- Security rules: privileged containers, host namespace sharing, dangerous capabilities
- Reliability rules: missing probes, single-replica production workloads, CrashLoopBackOff
- Works against any cluster — EKS, AKS, GKE, on-premises, or k3s
- System namespaces inventoried, not incorrectly flagged
Want to see it against your own data?
Talk to us about kubernetes compliance, or get started directly on Cloud & Kubernetes Performance & Compliance.