| 1.1.2 Ensure that the --basic-auth-file argument is not set | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.10 Ensure that the admission control plugin AlwaysAdmit is not set | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | ACCESS CONTROL |
| 1.1.13 Ensure that the admin.conf 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.13 Ensure that the admission control plugin SecurityContextDeny is set | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | ACCESS CONTROL |
| 1.1.13 Ensure that the admission control policy is set to NamespaceLifecycle | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | ACCESS CONTROL |
| 1.1.14 Ensure that the admission control plugin NamespaceLifecycle is set | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | ACCESS CONTROL |
| 1.1.14 Ensure that the admission control plugin NamespaceLifecycle is set | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | ACCESS CONTROL |
| 1.1.15 Ensure that the scheduler.conf 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.17 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | AUDIT AND ACCOUNTABILITY |
| 1.1.20 Ensure that the --token-auth-file parameter is not set | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.22 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate - certificate | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.22 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate - key | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.28 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate - cert | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.1.28 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate - key | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.1.29 Ensure that the --client-ca-file argument is set as appropriate | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.29 Ensure that the --client-ca-file argument is set as appropriate | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.30 Ensure that the API Server only makes use of Strong Cryptographic Ciphers | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.1.32 Ensure that the admission control policy is set to NodeRestriction | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | ACCESS CONTROL |
| 1.1.33 Ensure that the --experimental-encryption-provider-config argument is set as appropriate | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | |
| 1.1.33 Ensure that the admission control plugin NodeRestriction is set | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | ACCESS CONTROL |
| 1.1.34 Ensure that the --experimental-encryption-provider-config argument is set as appropriate | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | |
| 1.2.1 Ensure that the --anonymous-auth argument is set to false | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.1 Ensure that the --profiling argument is set to false | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.2.3 Ensure that the --kubelet-https argument is set to true | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.2.12 Ensure that the admission control plugin ServiceAccount is set | CIS Kubernetes v2.1.0 L2 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.13 Ensure that the admission control plugin NamespaceLifecycle is set | CIS Kubernetes v2.1.0 L2 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 1.2.14 Ensure that the admission control plugin NodeRestriction is set | CIS Kubernetes v2.1.0 L2 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.3.2 Ensure that the --profiling argument is set to false | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.3.2 Ensure that the --profiling argument is set to false | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.3.2 Ensure that the --profiling argument is set to false | CIS Kubernetes v1.20 Benchmark v1.0.1 L1 Master | Unix | CONFIGURATION MANAGEMENT |
| 1.3.5 Ensure that the --root-ca-file argument is set as appropriate | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true | CIS Kubernetes 1.11 Benchmark v1.3.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.3.7 Ensure that the RotateKubeletServerCertificate argument is set to true | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.4.8 Ensure that the etcd.conf file ownership is set to root:root | CIS Kubernetes 1.7.0 Benchmark v1.1.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 1.5.1 Ensure that the --cert-file and --key-file arguments are set as appropriate - key | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.5.6 Ensure that the --peer-auto-tls argument is not set to true | CIS Kubernetes 1.13 Benchmark v1.4.1 L1 | Unix | IDENTIFICATION AND AUTHENTICATION |
| 1.5.8 Ensure that the --max-wals argument is set to 0 | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | AUDIT AND ACCOUNTABILITY |
| 2.7 Ensure that a unique Certificate Authority is used for etcd | CIS Kubernetes v2.1.0 L2 Master Node | Unix | ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION |
| 3.2.2 Ensure that the audit policy covers key security concerns | CIS Kubernetes v2.1.0 L2 Master Node | Unix | AUDIT AND ACCOUNTABILITY |
| 5.1.14 Ensure that access to the Kubelet API uses fine-grained subresources instead of nodes/proxy where possible | CIS Kubernetes v2.1.0 L2 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.2.7 Minimize the admission of root containers | CIS Kubernetes v2.1.0 L2 Master Node | Unix | ACCESS CONTROL |
| 5.2.9 Minimize the admission of containers with capabilities assigned | CIS Kubernetes v2.1.0 L2 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 5.3.2 Ensure that all Namespaces have Network Policies defined | CIS Kubernetes v2.1.0 L2 Master Node | Unix | SECURITY ASSESSMENT AND AUTHORIZATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.4.1 Prefer using secrets as files over secrets as environment variables | CIS Kubernetes v2.1.0 L2 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.4.2 Consider external secret storage | CIS Kubernetes v2.1.0 L2 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller | CIS Kubernetes v2.1.0 L2 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 5.6.2 Ensure that the seccomp profile is set to docker/default in your pod definitions | CIS Kubernetes v2.1.0 L2 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 5.6.3 Apply Security Context to Your Pods and Containers | CIS Kubernetes v2.1.0 L2 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 5.6.4 The default namespace should not be used | CIS Kubernetes v2.1.0 L2 Master Node | Unix | CONFIGURATION MANAGEMENT, CONTINGENCY PLANNING, PLANNING, PROGRAM MANAGEMENT, SYSTEM AND SERVICES ACQUISITION, SYSTEM AND COMMUNICATIONS PROTECTION |
