| 1.1.4 Ensure that the controller manager 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.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 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 600 or more restrictive | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL |
| 2.2.2 Ensure administrator password retries and lockout time are configured | CIS Fortigate 7.0.x v1.3.0 L1 | FortiGate | ACCESS CONTROL |
| 3.1 Ensure that the docker.service file ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 3.3 Ensure that docker.socket file ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
| 3.7 Ensure that registry certificate file ownership is set to root:root | CIS Docker v1.6.0 L2 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.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.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.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.10 If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Worker | Unix | ACCESS CONTROL |
| 4.2.7 Ensure SSH root login is disabled | CIS Ubuntu Linux 20.04 LTS Workstation L1 v2.0.1 | Unix | ACCESS CONTROL |
| 4.2.20 Ensure sshd PermitRootLogin is disabled | CIS CentOS Linux 7 v4.0.0 L1 Workstation | Unix | ACCESS CONTROL |
| 4.3.1 Ensure sudo is installed | CIS Debian 10 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
| 4.3.2 Ensure sudo commands use pty | CIS Ubuntu Linux 18.04 LTS v2.2.0 L1 Workstation | Unix | ACCESS CONTROL |
| 4.3.2 Ensure sudo commands use pty | CIS Debian 10 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
| 4.3.4 Ensure users must provide password for privilege escalation | CIS Ubuntu Linux 20.04 LTS Server L2 v2.0.1 | Unix | ACCESS CONTROL |
| 4.3.4 Ensure users must provide password for privilege escalation | CIS Debian 10 Workstation L2 v2.0.0 | Unix | ACCESS CONTROL |
| 4.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS Debian 10 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
| 4.3.6 Ensure sudo authentication timeout is configured correctly | CIS Ubuntu Linux 18.04 LTS v2.2.0 L1 Workstation | 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 v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.1.7 Avoid use of system:masters group | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.1.20 Ensure sshd PermitRootLogin is disabled | CIS Rocky Linux 9 v2.0.0 L1 Server | Unix | ACCESS CONTROL |
| 5.1.20 Ensure sshd PermitRootLogin is disabled | CIS Rocky Linux 9 v2.0.0 L1 Workstation | Unix | ACCESS CONTROL |
| 5.2.1 Ensure sudo is installed | CIS Rocky Linux 9 v2.0.0 L1 Server | Unix | ACCESS CONTROL |
| 5.2.1 Minimize the admission of privileged containers | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.2.2 Ensure sudo commands use pty | CIS Ubuntu Linux 24.04 LTS v1.0.0 L1 Server | Unix | ACCESS CONTROL |
| 5.2.4 Ensure users must provide password for escalation | CIS Rocky Linux 9 v2.0.0 L2 Server | Unix | ACCESS CONTROL |
| 5.2.4 Ensure users must provide password for escalation | CIS Rocky Linux 9 v2.0.0 L2 Workstation | Unix | ACCESS CONTROL |
| 5.2.5 Minimize the admission of containers with allowPrivilegeEscalation | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL |
| 5.2.7 Ensure SSH root login is disabled | CIS Fedora 28 Family Linux Server L1 v2.0.0 | Unix | ACCESS CONTROL |
| 5.2.7 Minimize the admission of root containers | CIS Kubernetes v1.23 Benchmark v1.0.1 L2 Master | Unix | ACCESS CONTROL |
| 5.2.10 Ensure SSH root login is disabled | CIS SUSE Linux Enterprise 15 Server L1 v1.1.1 | Unix | ACCESS CONTROL |
| 5.3.4 Ensure users must provide password for escalation | CIS Fedora 28 Family Linux Workstation L2 v2.0.0 | Unix | ACCESS CONTROL |
| 5.4 Ensure root login is restricted to system console | CIS Google Container-Optimized OS v1.2.0 L1 Server | Unix | ACCESS CONTROL |
| 5.5 Ensure that privileged containers are not used | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 5.5 Ensure the 'root' Account Is Disabled | CIS Apple macOS 10.15 Catalina v3.0.0 L1 | Unix | ACCESS CONTROL |
| 5.5 Ensure the 'root' Account Is Disabled | CIS Apple macOS 11.0 Big Sur v4.0.0 L1 | Unix | ACCESS CONTROL |
| 5.6 Ensure the 'root' Account Is Disabled | CIS Apple macOS 10.14 v2.0.0 L1 | Unix | ACCESS CONTROL |
| 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 |
| 7.1 Ensure a replication-only user is created and used for streaming replication | CIS PostgreSQL 13 DB v1.2.0 | PostgreSQLDB | ACCESS CONTROL |
| 7.1 Ensure a replication-only user is created and used for streaming replication | CIS PostgreSQL 14 DB v 1.2.0 | PostgreSQLDB | ACCESS CONTROL |
| 7.1 Ensure a replication-only user is created and used for streaming replication | CIS PostgreSQL 16 DB v1.0.0 | PostgreSQLDB | ACCESS CONTROL |
| 7.2 Ensure logging of replication commands is configured | CIS PostgreSQL 13 DB v1.2.0 | PostgreSQLDB | ACCESS CONTROL |
| 7.2 Ensure logging of replication commands is configured | CIS PostgreSQL 16 DB v1.0.0 | PostgreSQLDB | ACCESS CONTROL |
