Kubernetes Kubelet authorization configuration is inspected to confirm the mode is not AlwaysAllow.
If authorization settings are absent, the effective mode requires manual verification.
Risk
With AlwaysAllow, any authenticated user (or anonymous if enabled) can call kubelet APIs. This enables reading logs and stats, running exec, or disrupting pods, leading to takeover, data exfiltration, and node abuse, degrading confidentiality, integrity, and availability.
prowler kubernetes --checks kubelet_authorization_mode
Recommendation
Use kubelet authorization mode Webhook so decisions defer to RBAC. Apply least privilege on node subresources, disable anonymous access, and restrict network exposure of the kubelet endpoint. Employ defense in depth with TLS and audit to monitor and control access.
Remediation
- In your cluster admin shell, run: kubectl -n kube-system edit configmap kubelet-config-<version>
- In the opened YAML, set the authorization mode to Webhook (add if missing): authorization: mode: Webhook
- Save and exit. Re-run the scan to confirm the finding is now PASS.
Source Code
Resource Type
ConfigMap