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.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.24 Benchmark v1.0.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.5 Ensure Interactive Login is Disabled | CIS MariaDB 10.6 on Linux L2 v1.1.0 | Unix | ACCESS CONTROL |
3.5 Ensure that the /etc/docker directory ownership is set to root:root | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
3.5 Ensure the SQL Server's MSSQL Service Account is Not an Administrator | CIS SQL Server 2017 Database L1 AWS RDS v1.3.0 | MS_SQLDB | ACCESS CONTROL |
3.5 Ensure the SQL Server's MSSQL Service Account is Not an Administrator | CIS SQL Server 2017 Database L1 OS v1.3.0 | Windows | ACCESS CONTROL |
3.6 Ensure the SQL Server's SQLAgent Service Account is Not an Administrator | CIS Microsoft SQL Server 2019 v1.4.0 L1 AWS RDS | MS_SQLDB | ACCESS CONTROL |
3.9 Ensure that TLS CA certificate file ownership is set to root:root | CIS Docker v1.6.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.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.10.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.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 |
4.2.19 Ensure sshd PermitRootLogin is disabled | CIS AlmaLinux OS 8 Workstation L1 v3.0.0 | Unix | ACCESS CONTROL |
4.2.19 Ensure sshd PermitRootLogin is disabled | CIS AlmaLinux OS 8 Server L1 v3.0.0 | Unix | ACCESS CONTROL |
4.3.1 Ensure sudo is installed | CIS Debian 10 Workstation L1 v2.0.0 | Unix | ACCESS CONTROL |
4.3.2 Ensure sudo commands use pty | CIS CentOS Linux 7 v4.0.0 L1 Workstation | Unix | ACCESS CONTROL |
4.3.4 Ensure users must provide password for escalation | CIS AlmaLinux OS 8 Workstation L2 v3.0.0 | Unix | ACCESS CONTROL |
4.3.4 Ensure users must provide password for escalation | CIS AlmaLinux OS 8 Server L2 v3.0.0 | Unix | ACCESS CONTROL |
4.3.5 Ensure re-authentication for privilege escalation is not disabled globally | CIS Amazon Linux 2 v3.0.0 L1 | Unix | ACCESS CONTROL |
4.3.5 Ensure sudo authentication timeout is configured correctly | CIS Amazon Linux 2023 Server L1 v1.0.0 | Unix | ACCESS CONTROL |
5.1.7 Avoid use of system:masters group | CIS Kubernetes v1.10.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.10.0 L1 Master | Unix | ACCESS CONTROL |
5.2 Ensure 'FILE' is Not Granted to Non-Administrative Users | CIS MariaDB 10.6 Database L1 v1.1.0 | MySQLDB | ACCESS CONTROL |
5.2.2 Ensure sudo commands use pty | CIS AlmaLinux OS 9 v2.0.0 L1 Server | 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.4 Ensure users must provide password for escalation | CIS AlmaLinux OS 9 v2.0.0 L2 Workstation | Unix | ACCESS CONTROL |
5.2.4 Ensure users must provide password for privilege escalation | CIS Debian Linux 12 v1.1.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 Workstation | Unix | ACCESS CONTROL |
5.2.6 Ensure sudo authentication timeout is configured correctly | CIS Debian Linux 11 v2.0.0 L1 Server | Unix | ACCESS CONTROL |
5.2.7 Minimize the admission of root containers | CIS Kubernetes v1.10.0 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 |
5.3.1 Ensure sudo is installed | CIS Fedora 28 Family Linux Server L1 v2.0.0 | Unix | ACCESS CONTROL |
5.3.2 Ensure sudo commands use pty | CIS CentOS Linux 8 Server L1 v2.0.0 | Unix | ACCESS CONTROL |
5.3.4 Ensure users must provide password for escalation | CIS Fedora 28 Family Linux Server L2 v2.0.0 | Unix | ACCESS CONTROL |
5.6 Ensure the "root" Account Is Disabled | CIS Apple macOS 13.0 Ventura v2.1.0 L1 | Unix | ACCESS CONTROL |
5.24 Ensure that docker exec commands are not used with the user=root option | CIS Docker v1.6.0 L2 Docker Linux | Unix | ACCESS CONTROL |
9.3 Ensure 'super_priv' is Not Set to 'Y' for Replication Users | CIS MariaDB 10.6 Database L1 v1.1.0 | MySQLDB | ACCESS CONTROL |
10.3 Restrict manager application | CIS Apache Tomcat 10 L2 v1.1.0 Middleware | Unix | ACCESS CONTROL |
10.3 Restrict manager application | CIS Apache Tomcat 9 L2 v1.2.0 Middleware | Unix | ACCESS CONTROL |
10.13 Do not run applications as privileged | CIS Apache Tomcat 9 L1 v1.2.0 Middleware | Unix | ACCESS CONTROL |
10.17 Setting Security Lifecycle Listener - check for config component | 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 10 L1 v1.1.0 | Unix | ACCESS CONTROL |
10.17 Setting Security Lifecycle Listener - check for umask uncommented in startup | CIS Apache Tomcat 9 L1 v1.2.0 Middleware | Unix | ACCESS CONTROL |
18.10.81.2 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Windows Server 2012 R2 DC L1 v3.0.0 | Windows | ACCESS CONTROL |
19.7.40.1 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Windows Server 2012 R2 DC L1 v3.0.0 | Windows | ACCESS CONTROL |
19.7.43.1 (L1) Ensure 'Always install with elevated privileges' is set to 'Disabled' | CIS Microsoft Windows Server 2008 Domain Controller Level 1 v3.3.1 | Windows | ACCESS CONTROL |