Ensure that the API server pod specification file permissions are set to 600 or more restrictive

MediumLevel 1Manual reviewopenshift

Description

Ensure that the API server 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 API servers: the OpenShift API server and the Kube API server. The OpenShift API server delegates requests for Kubernetes objects to the Kube API server. The OpenShift API server is managed as a deployment. The pod specification yaml for openshift-apiserver is stored in etcd. The Kube API Server is managed as a static pod. The pod specification file for the kube-apiserver is created on the control plane nodes at /etc/kubernetes/manifests/kube-apiserver-pod.yaml.

How it is fixed

Fix method: Guidance or infrastructure patch

There is no remediation for updating the permissions of kube-apiserver-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-permissionsapi-server
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 1.1.1 Ensure that the API server pod specification file permissions are set to 600 or more restrictive