This page explains the intended privacy posture for KubeDefence pilots. Final production agreements should be reviewed with customer security, procurement, and legal teams.
KubeDefence is designed to process Kubernetes and cloud security metadata such as cluster inventory, namespaces, workloads, images, RBAC relationships, findings, scan results, agent heartbeat, backup job metadata, and audit evidence.
The product should not require application payloads, customer database content, end-user records, passwords, private keys, or business transaction data to deliver posture and attack-path evidence.
Cluster backup workflows are positioned around customer-owned S3-compatible buckets wherever possible, helping regulated teams keep backup artifacts inside their control boundary.
For privacy, pilot, or security-review questions, contact contact@kubedefence.ai.