A fictional, anonymized example of the assessment format you receive, with a full downloadable PDF. It contains no customer information.
This public example shows how findings are organized and explained. A real assessment is tailored to the agreed environment and scope, with remediation priority based on severity, impact, and practical effort.
This sample report uses fictional data (cluster: production-demo) and is provided solely to demonstrate the structure and level of detail of a Kubernetes Cluster Audit. It contains no real customer, infrastructure, or credential information.
K8S-SEC-001 Critical
The payments-api deployment in the payments namespace runs a container with privileged: true.
A privileged container has effectively unrestricted access to the host, defeating standard container isolation.
Remove privileged mode or document and isolate the exception with least-privilege controls.
K8S-NET-001 Medium
The data and payments namespaces run workloads but have no NetworkPolicy resource defined.
Pod-to-pod traffic may be unrestricted depending on the CNI, widening the blast radius of a compromised workload.
Introduce a default-deny baseline, then add explicit ingress and egress rules required by each workload.
These two findings are a quick preview. Download the full PDF report to see all 42 findings, the executive summary, and the prioritized remediation plan.
The Kubernetes Cluster Audit is a fixed-price $500 engagement with a written report, prioritized remediation recommendations, and a live walkthrough.