Skip to main content

More Info:

The kube-proxy kubeconfig file should have permissions of 644 or more restrictive so that only authorized users can read or modify it. Overly permissive permissions could allow unauthorized users to alter proxy configuration.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS GKE

Triage and Remediation

Remediation

Manual Steps

  1. On every worker node, check the current permissions of the kubeconfig file:
  2. On every worker node, set the kubeconfig file permissions to 644:
  3. On every worker node, optionally ensure the file is owned by root (adjust if your environment requires a different owner/group):
  4. On every worker node, verify the permissions are now 644 or more restrictive (e.g., 640, 600):
kubectl cannot modify host-level file permissions such as /var/lib/kubelet/kubeconfig on worker nodes. To remediate this finding, you must change the file mode directly on each worker node’s filesystem; see the Manual Steps section for the exact commands.