| 1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 1.1.5 Ensure that the scheduler 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.6 Ensure that the scheduler pod specification file ownership is set to root:root | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 1.1.9 Ensure that the Container Network Interface file permissions are set to 600 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.13 Ensure that the default administrative credential file permissions are set to 600 | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.15 Ensure that the scheduler.conf file permissions are set to 600 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.16 Ensure that the scheduler.conf file ownership is set to root:root | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.4 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND SERVICES ACQUISITION |
| 1.2.5 Ensure that the --kubelet-certificate-authority argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND SERVICES ACQUISITION |
| 1.2.6 Ensure that the --authorization-mode argument is not set to AlwaysAllow | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.11 Ensure that the admission control plugin AlwaysPullImages is set | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, MEDIA PROTECTION |
| 1.2.18 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | AUDIT AND ACCOUNTABILITY |
| 1.2.20 Ensure that the --request-timeout argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 1.2.23 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.2.24 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.2.25 Ensure that the --client-ca-file argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.2.28 Ensure that encryption providers are appropriately configured | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.2.29 Ensure that the API Server only makes use of Strong Cryptographic Ciphers | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 1.2.30 Ensure that the --service-account-extend-token-expiration parameter is set to false | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND INFORMATION INTEGRITY |
| 1.3.3 Ensure that the --use-service-account-credentials argument is set to true | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY, IDENTIFICATION AND AUTHENTICATION |
| 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 1.4.1 Ensure that the --profiling argument is set to false | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 1.4.18 Ensure that the controller-manager.conf file ownership is set to root:root | CIS Kubernetes 1.8 Benchmark v1.2.0 L1 | Unix | CONFIGURATION MANAGEMENT |
| 2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 2.2 Ensure that the --client-cert-auth argument is set to true | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION |
| 2.6 Ensure that the --peer-auto-tls argument is not set to true | CIS Kubernetes v2.1.0 L1 Master Node | Unix | IDENTIFICATION AND AUTHENTICATION |
| 3.1.2 Service account token authentication should not be used for users | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 3.1.3 Bootstrap token authentication should not be used for users | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.1.2 Minimize access to secrets | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.1.4 Minimize access to create pods | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.1.6 Ensure that Service Account Tokens are only mounted where necessary | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.1.7 Avoid use of system:masters group | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.1.9 Minimize access to create persistent volumes | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.1.11 Minimize access to the approval sub-resource of certificatesigningrequests objects | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.1.13 Minimize access to the service account token creation | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL, AUDIT AND ACCOUNTABILITY |
| 5.2.4 Minimize the admission of containers wishing to share the host IPC namespace | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.2.5 Minimize the admission of containers wishing to share the host network namespace | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.2.6 Minimize the admission of containers with allowPrivilegeEscalation | CIS Kubernetes v2.1.0 L1 Master Node | Unix | ACCESS CONTROL |
| 5.2.8 Minimize the admission of containers with the NET_RAW capability | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT |
| 5.2.10 Minimize the admission of Windows HostProcess Containers | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND SERVICES ACQUISITION |
| 5.2.11 Minimize the admission of HostPath volumes | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SYSTEM AND COMMUNICATIONS PROTECTION |
| 5.2.12 Minimize the admission of containers which use HostPorts | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT, SYSTEM AND INFORMATION INTEGRITY |
| 5.2.13 Minimize the admission of containers which have unmasked procmounts | CIS Kubernetes v2.1.0 L1 Master Node | Unix | CONFIGURATION MANAGEMENT, SYSTEM AND INFORMATION INTEGRITY |
| 5.3.1 Ensure that the CNI in use supports Network Policies | CIS Kubernetes v2.1.0 L1 Master Node | Unix | SECURITY ASSESSMENT AND AUTHORIZATION, SYSTEM AND COMMUNICATIONS PROTECTION |
