Checks

Ensure that the controller-manager config file has permissions of 600 or more restrictive.

Ensure that the controller-manager config file ownership is set to root:root.

Ensure that the Kubernetes PKI directory and file file ownership is set to root:root.

Ensure that the Kubernetes PKI key file permission is set to 600.

Ensure that the Kubernetes PKI certificate file permission is set to 600.

Ensure that the kubelet service file has permissions of 600 or more restrictive.

Ensure that the kubelet service file ownership is set to root:root.

If kube-proxy is running, and if it is using a file-based kubeconfig file, ensure that the proxy kubeconfig file has permissions of 600 or more restrictive.

If kube-proxy is running, ensure that the file ownership of its kubeconfig file is set to root:root.

Ensure that the kubelet.conf file has permissions of 600 or more restrictive.

Ensure that the kubelet.conf file ownership is set to root:root.

Ensure that the certificate authorities file has permissions of 600 or more restrictive.

Ensure that the certificate authorities file ownership is set to root:root.

Ensure that if the kubelet refers to a configuration file with the --config argument, that file has permissions of 600 or more restrictive.

Ensure that if the kubelet refers to a configuration file with the --config argument, that file is owned by root:root.

Disable anonymous requests to the Kubelet server.

Do not allow all requests. Enable explicit authorization.

Enable Kubelet authentication using certificates.

Disable the read-only port.

Protect tuned kernel parameters from overriding kubelet default kernel parameter values.

Allow Kubelet to manage iptables.

Do not disable timeouts on streaming connections.

Do not override node hostnames.

Security relevant information should be captured. The --event-qps flag on the Kubelet can be used to limit the rate at which events are gathered