📊 KUBESCAPE SECURITY REPORT
Cluster Security Posture
Automated security scanning across NSA, MITRE ATT&CK, CIS, SOC2, and DevOps best practices frameworks.
admin@edgit-k8s
2026-03-18
v4.0.3
57
~946
COMPLIANCE SCORES BY FRAMEWORK
Each framework evaluates a different set of security controls. CIS is the most comprehensive with 40 controls.
NSA
2/20 controls passed
MITRE
2/19 controls passed
CIS
7/40 controls passed
SOC2
1/7 controls passed
DevOps
3/15 controls passed
Severity Distribution
Findings grouped by severity level across all frameworks.
2
6% of total
12
36% of total
12
36% of total
7
21% of total
HIGH SEVERITY FINDINGS
12 findingsMissing CPU limits
367 containers
Missing memory limits
298 containers
Containers running as root
251 containers
Credentials in config files
27 resources
Privileged containers
24 pods
Writable hostPath mounts
37 pods
HostPath mounts
40 pods
List K8s secrets (RBAC)
68 roles
HostNetwork access
7 pods
Insecure capabilities
11 pods
Host PID/IPC privileges
5 pods
Ingress TLS encryption
2 ingresses
MEDIUM SEVERITY FINDINGS
12 findingsNo Network Policies
53/57 namespaces
SA token automount
210 SAs / 223 pods
Container SA access
161 pods
Allow privilege escalation
115 pods
Missing seccomp profile
146 pods
Missing Linux hardening
118 pods
Unencrypted PVs
72 PVs
Missing liveness probes
130 pods
Secrets as env vars
137 env refs
Roles with delete caps
40 roles
Administrative Roles
5 roles
Admission ctrl not validated
25 webhooks
LOW SEVERITY FINDINGS
7 findingsMissing labels
188 resources
Immutable container FS
139 pods
Missing readiness probes
112 pods
Missing CPU requests
134 containers
Missing memory requests
139 containers
Image pull policy latest
6 pods
Naked pods (no controller)
3 pods
Security Coverage Gaps
Network policy enforcement and Pod Security Standards adoption across all namespaces.
Network Policy Coverage
Pod Security Standards
Compliance Score Targets
Projected scores after each remediation phase. Current scores shown as solid bars.
Remediation Roadmap
Phased approach from quick wins to advanced hardening — prioritized by impact and risk.
Quick Wins
Week 1-2 Low riskNetwork Segmentation
Week 2-4 Medium riskWorkload Hardening
Week 3-6 Medium riskAdvanced Hardening
Week 6-8 Higher riskOngoing Governance
Continuous Low riskACCEPTED RISKS
Infrastructure components that legitimately require elevated privileges. These are expected and documented.
Cilium CNI
kube-system
Longhorn
longhorn-system
NVIDIA GPU Operator
gpu-operator
NFS CSI
kube-system
Node Exporter
observability
Alloy (logs)
observability
Alloy (profiles)
observability
Eraser
eraser-system