Cis Ocp V190 1.1.6

CIS Red Hat OpenShift Container Platform Benchmark v1.9.0 - Control 1.1.6

Profile Applicability

• Level: 1

Description

Ensure that the scheduler pod specification file ownership is set to root:root.

Rationale

The scheduler pod specification file controls various parameters that set the behavior of the kube-scheduler service in the master node. You should set its file ownership to maintain the integrity of the file. The file should be owned by root:root.

Impact

None

Audit Procedure

In OpenShift 4, the kube-scheduler is deployed as a static pod and its pod specification file is created on control plane nodes at /etc/kubernetes/manifests/kube-scheduler-pod.yaml. It is mounted via hostpath to the kube-controller-manager pods via /etc/kubernetes/static-pod-resources/kube-scheduler-pod.yaml with ownership root:root.

Run the following command.

#Verify openshift-kube-scheduler ownership
for i in $(oc get pods -n openshift-kube-scheduler -l app=openshift-kube-scheduler -o name)
  do
  oc exec -n openshift-kube-scheduler $i -- \
  stat -c %U:%G /etc/kubernetes/static-pod-resources/kube-scheduler-pod.yaml
  done

Verify that the ownership is set to root:root.

Remediation

No remediation required; file permissions are managed by the operator.

Default Value

By default, in OpenShift 4, kube-scheduler-pod.yaml file ownership is set to root:root.

References

1. https://docs.openshift.com/container-platform/latest/architecture/control-plane.html#defining-masters_control-plane
2. https://docs.openshift.com/container-platform/latest/operators/operator-reference.html#cluster-kube-scheduler-operator_red-hat-operators
3. https://docs.openshift.com/container-platform/latest/nodes/scheduling/nodes-scheduler-about.html
4. https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/

CIS Controls

MITRE ATT&CK Mappings

Profile

Level 1 (Manual)