Skip to main content

More Info:

Verifies that the controller-manager.conf kubeconfig file has permissions of 600 or more restrictive to protect the controller managers client credentials.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. Check current permissions (run on every control plane node):
  2. Set restrictive permissions (600) (run on every control plane node):
  3. Set secure ownership (root:root) if needed (run on every control plane node):
  4. Verify final permissions (run on every control plane node):
    Confirm that permissions=600 and owner=root group=root.
kubectl cannot modify file permissions on control plane nodes, so it cannot be used to fix /etc/kubernetes/controller-manager.conf. Apply the remediation directly on every control plane node’s host OS as described in the Manual Steps section.