Skip to main content

More Info:

Ensure that the controller-manager.conf file has permissions of 644 or more restrictive

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, check the current permissions of the file (if it exists):
  2. If the file exists and permissions are more permissive than 644 (e.g., 666, 664, 777), tighten them:
  3. Confirm the ownership is appropriate (usually root:root); adjust if needed:
  4. Re-verify the permissions are now 644:
kubectl cannot modify host-level file permissions such as /etc/kubernetes/controller-manager.conf on control plane nodes. To remediate this finding, you must change the file permissions directly on every control plane node; see the Manual Steps section for the exact commands.

Additional Reading: