1.1.1 Ensure Administrative accounts are separate and cloud-only | CIS Microsoft 365 Foundations E3 L1 v3.1.0 | microsoft_azure | 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.3.17.1 Set 'User Account Control: Admin Approval Mode for the Built-in Administrator account' to 'Enabled' | CIS Windows 8 L1 v1.0.0 | Windows | ACCESS CONTROL |
1.1.7 Set 'aaa accounting' to log all privileged use commands using 'commands 15' | CIS Cisco IOS 15 L2 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 |
1.4.1 Set 'password' for 'enable secret' | CIS Cisco IOS XE 17.x v2.1.0 L1 | Cisco | ACCESS CONTROL |
3.6 Ensure the SQL Server's SQLAgent Service Account is Not an Administrator | CIS SQL Server 2016 Database L1 AWS RDS v1.4.0 | MS_SQLDB | 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.7 Ensure the SQL Server's Full-Text Service Account is Not an Administrator | CIS SQL Server 2016 Database L1 AWS RDS v1.4.0 | MS_SQLDB | ACCESS CONTROL |
3.11 Ensure that Docker server certificate file ownership is set to root:root | CIS Docker v1.6.0 L1 Docker Linux | 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.24 Benchmark v1.0.0 L1 Worker | Unix | ACCESS CONTROL |
4.2.7 Ensure SSH root login is disabled | CIS Debian 10 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
4.3.2 Ensure sudo commands use pty | CIS Amazon Linux 2 v3.0.0 L1 | Unix | ACCESS CONTROL |
4.3.4 Ensure re-authentication for privilege escalation is not disabled globally | CIS Amazon Linux 2023 Server L1 v1.0.0 | Unix | ACCESS CONTROL |
4.3.4 Ensure users must provide password for privilege escalation | CIS Debian 10 Server L2 v2.0.0 | Unix | ACCESS CONTROL |
4.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS AlmaLinux OS 8 Workstation L1 v3.0.0 | Unix | ACCESS CONTROL |
4.3.6 Ensure sudo authentication timeout is configured correctly | CIS Debian 10 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
5.1.20 Ensure sshd PermitRootLogin is disabled | CIS Debian Linux 12 v1.1.0 L1 Server | Unix | ACCESS CONTROL |
5.1.20 Ensure sshd PermitRootLogin is disabled | CIS Debian Linux 11 v2.0.0 L1 Server | Unix | ACCESS CONTROL |
5.2 Ensure 'FILE' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 on Linux L1 v1.1.0 | Unix | ACCESS CONTROL |
5.2 Ensure Options for the Web Root Directory Are Restricted | CIS Apache HTTP Server 2.4 L1 v2.1.0 | Unix | ACCESS CONTROL |
5.2.1 Ensure sudo is installed | CIS Debian Linux 12 v1.1.0 L1 Workstation | Unix | ACCESS CONTROL |
5.2.2 Ensure sudo commands use pty | CIS Debian Linux 12 v1.1.0 L1 Workstation | Unix | ACCESS CONTROL |
5.2.4 Ensure users must provide password for privilege escalation | CIS Debian Linux 11 v2.0.0 L2 Server | Unix | ACCESS CONTROL |
5.2.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS Debian Linux 12 v1.1.0 L1 Server | Unix | ACCESS CONTROL |
5.2.6 Ensure sudo authentication timeout is configured correctly | CIS AlmaLinux OS 9 v2.0.0 L1 Workstation | Unix | ACCESS CONTROL |
5.2.6 Ensure sudo authentication timeout is configured correctly | CIS Debian Linux 12 v1.1.0 L1 Workstation | 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 Ensure SSH root login is disabled | CIS CentOS Linux 8 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
5.3 Ensure 'PROCESS' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 Database L2 v1.1.0 | MySQLDB | ACCESS CONTROL |
5.3 Ensure 'PROCESS' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 on Linux L2 v1.1.0 | Unix | ACCESS CONTROL |
5.3.1 Ensure sudo is installed | CIS CentOS Linux 8 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
5.3.6 Ensure sudo authentication timeout is configured correctly | CIS Fedora 28 Family Linux Server L1 v2.0.0 | Unix | ACCESS CONTROL |
5.4 Adding authorized users in at.allow | CIS IBM AIX 7.1 L1 v2.1.0 | Unix | ACCESS CONTROL |
5.5 Ensure 'SHUTDOWN' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 Database L1 v1.1.0 | MySQLDB | ACCESS CONTROL |
5.6 Ensure the "root" Account Is Disabled | CIS Apple macOS 14.0 Sonoma v1.1.0 L1 | Unix | ACCESS CONTROL |
5.7 Ensure 'GRANT OPTION' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 Database L1 v1.1.0 | MySQLDB | ACCESS CONTROL |
5.26 Ensure that the container is restricted from acquiring additional privileges | CIS Docker v1.6.0 L1 Docker Linux | Unix | ACCESS CONTROL |
10.13 Do not run applications as privileged | CIS Apache Tomcat 10 L1 v1.1.0 | Unix | ACCESS CONTROL |
10.17 Setting Security Lifecycle Listener - check for umask present in startup | CIS Apache Tomcat 9 L1 v1.2.0 | Unix | ACCESS CONTROL |
10.17 Setting Security Lifecycle Listener - check for umask present in startup | CIS Apache Tomcat 9 L1 v1.2.0 Middleware | Unix | ACCESS CONTROL |
10.17 Setting Security Lifecycle Listener - check for umask uncommented in startup | CIS Apache Tomcat 10 L1 v1.1.0 | Unix | ACCESS CONTROL |
18.3.1 (L1) Ensure 'Apply UAC restrictions to local accounts on network logons' is set to 'Enabled' (MS only) | CIS Microsoft Windows Server 2008 Member Server Level 1 v3.3.1 | Windows | ACCESS CONTROL |
18.9.90.2 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Azure Compute Microsoft Windows Server 2019 v1.0.0 L1 MS | Windows | ACCESS CONTROL |
18.9.90.2 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Microsoft Windows Server 2008 Member Server Level 1 v3.3.1 | Windows | ACCESS CONTROL |
19.7.40.1 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Windows Server 2012 DC L1 v3.0.0 | Windows | ACCESS CONTROL |