Vulnerabilities
Misconfiguration
Runtime Security
Compliance
Compliance > Kubernetes > CIS 1.24 > Control Plane Security Configuration >

Control Plane Node Configuration Files

N/A
Source
Kube Bench
ID
1.1
Version
cis-1.24

1.1 Control Plane Node Configuration Files

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

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 $apiserverconf

1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root $apiserverconf

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

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 $controllermanagerconf

1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root $controllermanagerconf

1.1.5 Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 $schedulerconf

1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root $schedulerconf

1.1.7 Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 $etcdconf

1.1.8 Ensure that the etcd pod specification file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root $etcdconf

1.1.9 Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 <path/to/cni/files>

1.1.10 Ensure that the Container Network Interface file ownership is set to root:root (Manual)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root <path/to/cni/files>

1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)

On the etcd server node, get the etcd data directory, passed as an argument –data-dir, from the command ‘ps -ef | grep etcd’. Run the below command (based on the etcd data directory found above). For example, chmod 700 /var/lib/etcd

1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)

On the etcd server node, get the etcd data directory, passed as an argument –data-dir, from the command ‘ps -ef | grep etcd’. Run the below command (based on the etcd data directory found above). For example, chown etcd:etcd /var/lib/etcd

1.1.13 Ensure that the admin.conf file permissions are set to 600 or more restrictive (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 /etc/kubernetes/admin.conf

1.1.14 Ensure that the admin.conf file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root /etc/kubernetes/admin.conf

1.1.15 Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 $schedulerkubeconfig

1.1.16 Ensure that the scheduler.conf file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root $schedulerkubeconfig

1.1.17 Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod 600 $controllermanagerkubeconfig

1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown root:root $controllermanagerkubeconfig

1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)

Run the below command (based on the file location on your system) on the control plane node. For example, chown -R root:root /etc/kubernetes/pki/

1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive (Manual)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod -R 600 /etc/kubernetes/pki/*.crt

1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)

Run the below command (based on the file location on your system) on the control plane node. For example, chmod -R 600 /etc/kubernetes/pki/*.key

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2023 Aqua Security Software Ltd.   Privacy Policy | Terms of Use