| 1.1.2 Ensure that the API server pod specification file ownership is set to root:root | CIS Kubernetes v1.10.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.10.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.10.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.10.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.10.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.14 Ensure that the default administrative credential file ownership is set to root:root | CIS Kubernetes v1.10.0 L1 Master | Unix | ACCESS CONTROL |
| 1.1.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes v1.10.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.10.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.10.0 L1 Master | Unix | ACCESS CONTROL |
| 1.8.2 Set username secret for all local users | CIS Cisco IOS XR 7.x v1.0.0 L1 | Cisco | ACCESS CONTROL |
| 3.1 Ensure that the docker.service file ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 3.3 Ensure that docker.socket file ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 3.5 Ensure that the /etc/docker directory ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 3.6 Review Superuser/Admin Roles - clusterAdmin | CIS MongoDB 3.2 Database Audit L2 v1.0.0 | MongoDB | ACCESS CONTROL |
| 3.6 Review Superuser/Admin Roles - clusterAdmin | CIS MongoDB 3.4 Database Audit L2 v1.0.0 | MongoDB | ACCESS CONTROL |
| 3.7 Ensure that registry certificate file ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 3.11 Ensure that Docker server certificate file ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 3.13 Ensure that the Docker server certificate key file ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 3.17 Ensure that the daemon.json file ownership is set to root:root | CIS Docker v1.7.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.7.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.7.0 L2 Docker - Linux | Unix | ACCESS CONTROL |
| 3.23 Ensure that the Containerd socket file ownership is set to root:root | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 4.1 Ensure Interactive Login is Disabled | CIS PostgreSQL 13 OS v1.2.0 | Unix | ACCESS CONTROL |
| 4.1 Ensure Interactive Login is Disabled | CIS PostgreSQL 14 OS v 1.2.0 | Unix | ACCESS CONTROL |
| 4.1 Ensure Interactive Login is Disabled | CIS PostgreSQL 17 v1.0.0 L1 PostgreSQL | Unix | ACCESS CONTROL |
| 4.1.2 Ensure that the kubelet service file ownership is set to root:root | CIS Kubernetes v1.10.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.4 If proxy kubeconfig file exists ensure ownership is set to root:root | CIS Kubernetes v1.10.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.1.6 Avoid use of system:masters group | CIS Google Kubernetes Engine (GKE) Autopilot v1.1.0 L1 | GCP | ACCESS CONTROL |
| 4.1.6 Avoid use of system:masters group | CIS Google Kubernetes Engine (GKE) v1.7.0 L1 | GCP | ACCESS CONTROL |
| 4.1.7 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Google Kubernetes Engine (GKE) v1.7.0 L1 | GCP | ACCESS CONTROL |
| 4.1.7 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Google Kubernetes Engine (GKE) Autopilot v1.1.0 L1 | GCP | ACCESS CONTROL |
| 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root | CIS Kubernetes v1.10.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.10.0 L1 Worker | Unix | ACCESS CONTROL |
| 4.8 Ensure setuid and setgid permissions are removed | CIS Docker v1.7.0 L2 Docker - Linux | Unix | ACCESS CONTROL |
| 5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes v1.10.0 L1 Master | Unix | ACCESS CONTROL |
| 5.2.6 Minimize the admission of containers with allowPrivilegeEscalation | CIS Kubernetes v1.10.0 L1 Master | Unix | ACCESS CONTROL |
| 5.2.7 Minimize the admission of root containers | CIS Kubernetes v1.10.0 L2 Master | Unix | ACCESS CONTROL |
| 5.5 Ensure that privileged containers are not used | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 5.18 Ensure that host devices are not directly exposed to containers | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 5.23 Ensure that docker exec commands are not used with the privileged option | CIS Docker v1.7.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.7.0 L2 Docker - Linux | Unix | ACCESS CONTROL |
| 5.26 Ensure that the container is restricted from acquiring additional privileges | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 5.32 Ensure that the Docker socket is not mounted inside any containers | CIS Docker v1.7.0 L1 Docker - Linux | Unix | ACCESS CONTROL |
| 6.1.1 Ensure sudo is installed | CIS IBM AIX 7 v1.0.0 L2 | Unix | ACCESS CONTROL |
| 6.2.2 Ensure at.allow is configured | CIS IBM AIX 7 v1.0.0 L1 | Unix | ACCESS CONTROL |
| 7.0.1 Establish an administrator group - 'sysadm_group value' | CIS IBM DB2 OS L2 v1.2.0 | Unix | ACCESS CONTROL |
| 7.0.4 Establish system monitoring group - 'sysmon_group users' | CIS IBM DB2 OS L1 v1.2.0 | Unix | ACCESS CONTROL |
| 8.5 Remove the toor user. | CIS FreeBSD v1.0.5 | Unix | ACCESS CONTROL |
| 10.3 Restrict manager application | CIS Apache Tomcat 7 L2 v1.1.0 | Unix | ACCESS CONTROL |
| 10.3 Restrict manager application | CIS Apache Tomcat 7 L2 v1.1.0 Middleware | Unix | ACCESS CONTROL |
