More Info:
If the kube-proxy kubeconfig file exists it may contain connection credentials and should be protected. Permissions of 600 or more restrictive keep it readable only by root.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On each worker node, check if the kube-proxy kubeconfig file exists and view its current permissions:
-
On each worker node where
/etc/kubernetes/proxy.confexists, set its permissions to600: -
On each worker node, confirm the file is owned by
rootand in therootgroup (adjust if necessary): -
On each worker node, verify the final permissions match the benchmark requirement:
The output must show:
Using kubectl
Using kubectl
kubectl cannot modify file permissions on worker node files such as
/etc/kubernetes/proxy.conf; this must be fixed directly on each worker node’s host filesystem. Use SSH and follow the steps in the Manual Steps section to set the correct permissions.Automation
Automation

