| 1.1.2 Ensure that the API server pod specification file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.2 Ensure that the API server pod specification file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.2 Ensure that the API server pod specification file ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.8 Ensure that the etcd pod specification file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.10 Ensure that the Container Network Interface file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.14 Ensure that the admin.conf file ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.14 Ensure that the admin.conf file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.14 Ensure that the admin.conf file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
| 1.2.1 Set 'privilege 1' for local users - 'All users have encrypted passwords' | CIS Cisco IOS 15 L1 v4.1.1 | Cisco | ACCESS CONTROL |
| 1.2.1 Set 'privilege 1' for local users - 'No users with privileges 2-15' | CIS Cisco IOS 15 L1 v4.1.1 | Cisco | ACCESS CONTROL |
| 3.1 Ensure that the docker.service file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.3 Ensure that docker.socket file ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 3.5 Ensure that the /etc/docker directory ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.5 Ensure that the /etc/docker directory ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 3.7 Ensure that registry certificate file ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 3.11 Ensure that Docker server certificate file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.13 Ensure that the Docker server certificate key file ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 3.17 Ensure that the daemon.json file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.19 Ensure that the /etc/default/docker file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.22 Ensure that the /etc/sysconfig/docker file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.23 Ensure that the Containerd socket file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.23 Ensure that the Containerd socket file ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 4.1.2 Ensure that the kubelet service file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.2 Ensure that the kubelet service file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.4 If proxy kubeconfig file exists ensure ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.4 If proxy kubeconfig file exists ensure ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.4 If proxy kubeconfig file exists ensure ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.10 Ensure that the kubelet --config configuration file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.10 If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root | CIS Kubernetes Benchmark v1.8.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.10 If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.8 Ensure setuid and setgid permissions are removed | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 5.1.7 Avoid use of system:masters group | CIS Kubernetes Benchmark v1.8.0 L1 Master | Unix | ACCESS CONTROL |
| 5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes Benchmark v1.8.0 L1 Master | Unix | ACCESS CONTROL |
| 5.2.6 Minimize the admission of containers with allowPrivilegeEscalation | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
| 5.2.6 Minimize the admission of containers with allowPrivilegeEscalation | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.2.6 Minimize the admission of root containers | CIS Kubernetes v1.20 Benchmark v1.0.1 L2 Master | Unix | ACCESS CONTROL |
| 5.2.7 Minimize the admission of root containers | CIS Kubernetes v1.24 Benchmark v1.0.0 L2 Master | Unix | ACCESS CONTROL |
| 5.5 Ensure SNMP Write Access is not set | CIS Juniper OS Benchmark v2.1.0 L2 | Juniper | ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.23 Ensure that docker exec commands are not used with the privileged option | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 5.24 Ensure that docker exec commands are not used with the user=root option | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
