Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive

MediumLevel 1Manual reviewopenshift

Description

Ensure that the controller manager pod specification file has permissions of 600 or more restrictive. The benchmark marks this recommendation Manual.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

OpenShift 4 deploys two controller managers: the OpenShift Controller manager and the Kube Controller manager. The OpenShift Controller manager is managed as a deployment. The pod specification yaml for openshift-controller-manager is stored in etcd. The Kube Controller manager is managed as a static pod. The pod specification file for the openshift-kube-controller-manager is created on control plane nodes at /etc/kubernetes/manifests/kube-controller-manager-pod.yaml.

How it is fixed

Fix method: Guidance or infrastructure patch

There is no remediation for updating the permissions of kube-controller-manager-pod.yaml. The file is owned by an OpenShift operator and any changes to the file will result in a degraded cluster state. Please do not attempt to remediate the permissions of this file.

Properties

Operating systems: Any
Tags: openshiftcontrol-planefile-permissions
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 1.1.3 Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive