Verify Permissions on the Worker Proxy Kubeconfig File
An XCCDF Rule
Description
To ensure the Kubernetes ConfigMap is mounted into the sdn daemonset pods with the
correct permissions, make sure that the sdn-config
ConfigMap is mounted using
restrictive permissions. Check that the config
VolumeMount mounts the
sdn-config
configMap with permissions set to 420:
{ "configMap": { "defaultMode": 420, "name": "sdn-config" }, "name": "config" }
warning alert: Warning
/apis/apps/v1/namespaces/openshift-sdn/daemonsets/sdn
API endpoint to the local /apis/apps/v1/namespaces/openshift-sdn/daemonsets/sdn
file. Rationale
The kube-proxy kubeconfig file controls various parameters of the kube-proxy service in the worker node. If used, 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. The kube-proxy runs with the kubeconfig parameters configured as a Kubernetes ConfigMap instead of a file. In this case, there is no proxy kubeconfig file. But appropriate permissions still need to be set in the ConfigMap mount.
- ID
- xccdf_org.ssgproject.content_rule_file_permissions_proxy_kubeconfig
- Severity
- Medium
- References
- Updated