If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive
Note: to enable this control run Kubescape with host sensor (see here)
The kubelet reads various parameters, including security settings, from a config file specified by the
--config argument. If this file is specified you should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.
Ensure that if the kubelet refers to a configuration file with the
--config argument, that file has permissions of 600 or more restrictive.
Run the below command (based on the file location on your system) on the each worker node. For example,
stat -c %a /var/lib/kubelet/config.yaml
Verify that the permissions are
600 or more restrictive.
Run the following command (using the config file location identied in the Audit step)
chmod 600 /var/lib/kubelet/config.yaml
By default, the /var/lib/kubelet/config.yaml file as set up by
kubeadm has permissions of 600.
Updated 12 days ago