| 1.1.1 Ensure that the API server pod specification file permissions are set to 600 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.4 Ensure that the --insecure-bind-address argument is not set | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.1.5 Ensure that the --insecure-bind-address argument is not set | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.1.7 Ensure that the etcd pod specification file permissions are set to 600 or more restrictive | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.7 Ensure that the etcd pod specification file permissions are set to 600 or more restrictive | CIS Kubernetes v1.23 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.7 Ensure that the etcd pod specification file permissions are set to 600 or more restrictive | CIS Kubernetes v1.24 Benchmark v1.0.0 L1 Master | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.8 Ensure that the etcd pod specification file ownership is set to root:root | CIS Red Hat OpenShift Container Platform v1.9.0 L1 | OpenShift | ACCESS CONTROL |
| 1.1.17 Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.2 Ensure that the --token-auth-file parameter is not set | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT, MAINTENANCE |
| 1.2.7 Ensure that the --authorization-mode argument includes Node | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.8 Ensure that the --authorization-mode argument includes RBAC | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 1.2.10 Ensure that the admission control plugin AlwaysAdmit is not set | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.15 Ensure that the --profiling argument is set to false | CIS Kubernetes v2.1.0 L1 Master Node | Unix | AUDIT AND ACCOUNTABILITY |
| 1.2.16 Ensure that the --audit-log-path argument is set | CIS Kubernetes v2.1.0 L1 Master Node | Unix | AUDIT AND ACCOUNTABILITY |
| 1.2.19 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | AUDIT AND ACCOUNTABILITY |
| 1.2.21 Ensure that the --service-account-lookup argument is set to true | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.26 Ensure that the --etcd-cafile argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.2.27 Ensure that the --encryption-provider-config argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.3.2 Ensure that the --profiling argument is set to false | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.4.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.1 Ensure that the apiserver file permissions are set to 644 or more restrictive | CIS Kubernetes 1.7.0 Benchmark v1.1.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.2 Ensure that the API server pod specification file ownership is set to root:root | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.3 Ensure that the config file permissions are set to 644 or more restrictive | CIS Kubernetes 1.7.0 Benchmark v1.1.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.5 Ensure that the scheduler file permissions are set to 644 or more restrictive | CIS Kubernetes 1.7.0 Benchmark v1.1.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.6 Ensure that the scheduler file ownership is set to root:root | CIS Kubernetes 1.7.0 Benchmark v1.1.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.6 Ensure that the scheduler pod specification file ownership is set to root:root | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.14 Ensure that the admin.conf file ownership is set to root:root | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.14 Ensure that the admin.conf file ownership is set to root:root | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.21 Ensure that the Kubernetes PKI key file permissions are set to 600 | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.5.7 Ensure that the --wal-dir argument is set as appropriate | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | AUDIT AND ACCOUNTABILITY |
| 2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 3.1.1 Client certificate authentication should not be used for users | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 4.1.1 Ensure that the kubelet service file permissions are set to 600 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 5.1.1 Ensure that the cluster-admin role is only used where required | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.1.5 Ensure that default service accounts are not actively used. | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.1.8 Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.1.10 Minimize access to the proxy sub-resource of nodes | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.1.12 Minimize access to webhook configuration objects | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.2.1 Ensure that the cluster has at least one active policy control mechanism in place | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SECURITY ASSESSMENT AND AUTHORIZATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.2.2 Minimize the admission of privileged containers | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.2.3 Minimize the admission of containers wishing to share the host process ID namespace | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.6.1 Create administrative boundaries between resources using namespaces | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
