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.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.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.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.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.12 Ensure the 'SYSADMIN' Role is Limited to Administrative or Built-in Accounts | CIS SQL Server 2022 Database L1 DB v1.1.0 | MS_SQLDB | 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 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.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.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.24 Benchmark v1.0.0 L1 Worker | Unix | ACCESS CONTROL |
4.1.6 Avoid use of system:masters group | CIS Google Kubernetes Engine (GKE) v1.6.1 L1 | GCP | ACCESS CONTROL |
4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root | CIS Kubernetes v1.10.0 L1 Worker | Unix | ACCESS CONTROL |
4.1.7 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Google Kubernetes Engine (GKE) v1.6.1 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.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 |
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.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 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 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.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.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 |
6.3.1 Privilege escalation: sudo | CIS IBM AIX 7.2 L2 v1.1.0 | Unix | ACCESS CONTROL |
6.4 Adding authorized users in at.allow | CIS IBM AIX 7.2 L1 v1.1.0 | Unix | ACCESS CONTROL |
6.6 Adding authorized users in cron.allow | CIS IBM AIX 7.2 L1 v1.1.0 | 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 |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - 800-53r5 High | Unix | ACCESS CONTROL |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - All Profiles | Unix | ACCESS CONTROL |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - CNSSI 1253 | Unix | ACCESS CONTROL |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - 800-171 | Unix | ACCESS CONTROL |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - 800-53r4 High | Unix | ACCESS CONTROL |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - 800-53r4 Moderate | Unix | ACCESS CONTROL |
Monterey - Require Administrator Password to Modify System-Wide Preferences | NIST macOS Monterey v1.0.0 - 800-53r5 Moderate | Unix | ACCESS CONTROL |