| 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.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.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.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.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.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.4.1 Set 'password' for 'enable secret' | CIS Cisco IOS XE 16.x v2.1.0 L1 | Cisco | ACCESS CONTROL |
| 3.5 Ensure the SQL Server's MSSQL Service Account is Not an Administrator | CIS SQL Server 2016 Database L1 AWS RDS v1.4.0 | MS_SQLDB | ACCESS CONTROL |
| 3.5 Ensure the SQL Server's MSSQL Service Account is Not an Administrator | CIS SQL Server 2016 Database L1 OS v1.4.0 | Windows | ACCESS CONTROL |
| 3.6.3.3 FTPD: Disable root access to ftp | CIS IBM AIX 7.1 L1 v2.1.0 | Unix | ACCESS CONTROL |
| 3.7 Ensure the SQL Server's Full-Text Service Account is Not an Administrator | CIS SQL Server 2017 Database L1 AWS RDS v1.3.0 | MS_SQLDB | ACCESS CONTROL |
| 3.9 Ensure that TLS CA certificate file ownership is set to root:root | CIS Docker v1.6.0 L1 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 |
| 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.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.2.20 Ensure sshd PermitRootLogin is disabled | CIS CentOS Linux 7 v4.0.0 L1 Server | Unix | ACCESS CONTROL |
| 4.3.1 Ensure sudo is installed | CIS CentOS Linux 7 v4.0.0 L1 Workstation | Unix | ACCESS CONTROL |
| 4.3.1 Ensure sudo is installed | CIS CentOS Linux 7 v4.0.0 L1 Server | Unix | ACCESS CONTROL |
| 4.3.1 Ensure sudo is installed | CIS AlmaLinux OS 8 Workstation L1 v3.0.0 | Unix | ACCESS CONTROL |
| 4.3.1 Ensure sudo is installed | CIS Amazon Linux 2 v3.0.0 L1 | Unix | ACCESS CONTROL |
| 4.3.2 Ensure sudo commands use pty | CIS AlmaLinux OS 8 Server L1 v3.0.0 | Unix | ACCESS CONTROL |
| 4.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS Debian 10 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
| 4.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS CentOS Linux 7 v4.0.0 L1 Server | Unix | ACCESS CONTROL |
| 4.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS AlmaLinux OS 8 Server L1 v3.0.0 | Unix | ACCESS CONTROL |
| 4.3.6 Ensure sudo authentication timeout is configured correctly | CIS Debian 10 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
| 4.3.6 Ensure sudo authentication timeout is configured correctly | CIS CentOS Linux 7 v4.0.0 L1 Server | Unix | ACCESS CONTROL |
| 4.3.6 Ensure sudo authentication timeout is configured correctly | CIS AlmaLinux OS 8 Workstation L1 v3.0.0 | Unix | ACCESS CONTROL |
| 5.1 Ensure Options for the OS Root Directory Are Restricted | CIS Apache HTTP Server 2.4 L1 v2.1.0 | 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.20 Ensure sshd PermitRootLogin is disabled | CIS Debian Linux 12 v1.1.0 L1 Workstation | Unix | ACCESS CONTROL |
| 5.2.1 Ensure sudo is installed | CIS Debian Linux 12 v1.1.0 L1 Server | Unix | ACCESS CONTROL |
| 5.2.1 Ensure sudo is installed | CIS Debian Linux 11 v2.0.0 L1 Server | Unix | ACCESS CONTROL |
| 5.2.1 Ensure sudo is installed | CIS AlmaLinux OS 9 v2.0.0 L1 Workstation | Unix | ACCESS CONTROL |
| 5.2.2 Ensure sudo commands use pty | CIS Debian Linux 12 v1.1.0 L1 Server | Unix | ACCESS CONTROL |
| 5.2.4 Ensure users must provide password for privilege escalation | CIS Debian Linux 12 v1.1.0 L2 Workstation | Unix | ACCESS CONTROL |
| 5.2.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS Debian Linux 11 v2.0.0 L1 Server | Unix | ACCESS CONTROL |
| 5.2.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS AlmaLinux OS 9 v2.0.0 L1 Server | 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.3.1 Ensure sudo is installed | CIS CentOS Linux 8 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
| 5.3.2 Ensure sudo commands use pty | CIS CentOS Linux 8 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
| 5.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS CentOS Linux 8 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
| 5.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS CentOS Linux 8 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
| 5.4 Ensure 'SUPER' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 Database L1 v1.1.0 | MySQLDB | ACCESS CONTROL |
| 5.18 Ensure that host devices are not directly exposed to containers | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 5.32 Ensure that the Docker socket is not mounted inside any containers | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
| 10.17 Setting Security Lifecycle Listener - check for config component | CIS Apache Tomcat 10 L1 v1.1.0 Middleware | Unix | ACCESS CONTROL |
| 18.9.90.2 Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Azure Compute Microsoft Windows Server 2022 v1.0.0 L1 MS | Windows | ACCESS CONTROL |
| 18.10.81.2 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Windows Server 2012 DC L1 v3.0.0 | Windows | ACCESS CONTROL |
