Skip to main content

More Info:

Verifies that Kubernetes PKI certificate files have permissions of 644 or more restrictive to protect the clusters public certificates from tampering.

Risk Level

Medium

Address

Security

Compliance Standards

  • CIS Kubernetes

Triage and Remediation

Remediation

Manual Steps

  1. On every control plane node, list current permissions for all PKI certificate files and review them for unexpected entries or ownership before changing anything:
  1. Still on each control plane node, back up the PKI directory (for recovery if needed):
  1. On each control plane node, set certificate file permissions to 644 (owner read/write, group and others read-only), which is “644 or more restrictive”:
  1. On each control plane node, ensure the certificate files are owned by the expected Kubernetes user and group (commonly root:root); adjust if needed based on your environment’s standard:
  1. If your environment requires stricter permissions (for example, no world-read), you may optionally further restrict them, but only after confirming that all Kubernetes components that need to read these certificates will still have access:
  1. Verify on each control plane node that all .crt files now have permissions 644 or more restrictive (e.g., 640, 600):
kubectl cannot modify file permissions on control plane nodes, so this finding cannot be fixed through the Kubernetes API. The required changes must be made directly on each control plane node’s filesystem (for /etc/kubernetes/pki/*.crt); follow the guidance in the Manual Steps section to remediate.