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.2 Ensure that the API server pod specification file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root | CIS Kubernetes v1.11.1 L1 Master Node | Unix | ACCESS CONTROL |
1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.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 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 v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
1.1.8 Ensure that the etcd pod specification file ownership is set to root:root | CIS Kubernetes v1.11.1 L1 Master Node | Unix | ACCESS CONTROL |
1.1.10 Ensure that the Container Network Interface file ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
1.1.10 Ensure that the Container Network Interface file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.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.11.1 L1 Master Node | Unix | ACCESS CONTROL |
1.1.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes v1.23 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.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes v1.11.1 L1 Master Node | 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.18 Ensure that the controller-manager.conf file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.0 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.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive | CIS Kubernetes v1.11.1 L1 Master Node | Unix | 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.4 Ensure that Cassandra is run using a non-privileged, dedicated service account | CIS Apache Cassandra 3.11 L1 Unix Audit v1.0.0 | Unix | ACCESS CONTROL |
3.4 Ensure that Cassandra is run using a non-privileged, dedicated service account | CIS Apache Cassandra 3.11 L2 Unix Audit v1.0.0 | 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.2 Ensure that the kubelet service file ownership is set to root:root | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
4.1.2 Ensure that the kubelet service file 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.20 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.11.1 L1 Worker Node | 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.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root | CIS Kubernetes v1.11.1 L1 Worker Node | 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.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 v1.24 Benchmark v1.0.0 L1 Worker | Unix | ACCESS CONTROL |
4.1.8 Ensure that the client certificate authorities file ownership is set to root:root | CIS Kubernetes v1.23 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.8 Ensure that the client certificate authorities file ownership is set to root:root | CIS Kubernetes v1.24 Benchmark v1.0.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 |
5.1.7 Avoid use of system:masters group | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes v1.11.1 L1 Master Node | Unix | ACCESS CONTROL |
5.2.2 Minimize the admission of privileged containers | 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 containers with allowPrivilegeEscalation | CIS Kubernetes v1.11.1 L1 Master Node | 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 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 |
10.2 Restrict access to the web administration application | CIS Apache Tomcat 11 v1.0.0 L1 | Unix | ACCESS CONTROL |
10.3 Restrict manager application | CIS Apache Tomcat 10.1 v1.1.0 L2 | Unix | ACCESS CONTROL |
10.13 Do not run applications as privileged | CIS Apache Tomcat 11 v1.0.0 L1 | Unix | ACCESS CONTROL |
10.13 Do not run applications as privileged | CIS Apache Tomcat 10.1 v1.1.0 L1 | Unix | ACCESS CONTROL |