More Info:
Verifies that Container Network Interface configuration files have permissions of 600 or more restrictive to prevent tampering with pod networking.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every control plane node, identify the CNI config directory used by kubelet (fallbacks to
/etc/cni/net.dif not set): -
On every control plane node, set permissions on all CNI config files in the directory (replace
/etc/cni/net.dif your path is different): -
On every control plane node, ensure ownership is appropriate (commonly
root:root; adjust if your environment requires different ownership): -
On every control plane node, if you are using per-network state under
/var/lib/cni/networks, optionally restrict those files as well (if present): -
On every control plane node, verify that all CNI configuration and network state files now have permissions
600:Confirm the output shows onlypermissions=600.
Using kubectl
Using kubectl
kubectl cannot modify Container Network Interface file permissions because they are host-level files under
/etc/cni/net.d (and other CNI paths) on each control plane node. To remediate this finding, adjust permissions directly on those nodes as described in the Manual Steps section.Automation
Automation

