Red Hat OpenShift
TMA-OPENSHIFT-4.1.3
If proxy kube proxy configuration file exists ensure permissions are set to 644 or more restrictive
Description
If kube-proxy is running, and if it is using a file-based configuration file, ensure that the file has permissions of 644 or more restrictive. The benchmark marks this recommendation Manual.
How it is checked
Audit method: Manual review
In OpenShift 4, the kube-proxy runs within the sdn pods, which copies the kubeconfig from a configmap to the container at /config/kube-proxy-config.yaml, with 644 permissions. Run the following command: for i in $(oc get pods -n openshift-sdn -l app=sdn -oname) do oc exec -n openshift-sdn $i -- \ stat -Lc %a /config/kube-proxy-config.yaml done Verify that the kube-proxy-config.yaml file has permissions of 644.
How it is fixed
Fix method: Guidance or infrastructure patch
Use chmod on kube-proxy config file and set permissions to 644
Properties
- Operating systems
- Any
- Tags
- openshiftworker-nodefile-permissions
- Reference
- CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 4.1.3 If proxy kube proxy configuration file exists ensure permissions are set to 644 or more restrictive