More Info:
Anonymous authentication should be disabled on the kubelet so that unauthenticated requests are rejected. Enabling it allows anonymous, unauthenticated access to the kubelet API.Risk Level
CriticalAddress
SecurityCompliance Standards
- CIS AKS
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
- On every worker node, open the kubelet config file and ensure anonymous auth is disabled:
- If the kubelet is also configured via systemd flags, ensure no conflicting
--anonymous-authflag is present:
--anonymous-auth=true, edit it:- Reload systemd and restart kubelet on that worker node:
- Verify the kubelet process is running with anonymous auth disabled on that worker node:
--anonymous-auth=false or confirm there is no --anonymous-auth=true flag and anonymous auth is disabled via /var/lib/kubelet/config.yaml as edited in step 1.Using kubectl
Using kubectl
kubectl cannot change kubelet process flags or its config file, so this finding cannot be remediated via the Kubernetes API. The fix must be applied directly on each worker node’s host configuration (for example
/var/lib/kubelet/config.yaml and the kubelet systemd unit); see the Manual Steps section for details.Automation
Automation

