CIS Kubernetes v1.11.1 L1 Master Node

Audit Details

Name: CIS Kubernetes v1.11.1 L1 Master Node

Updated: 7/29/2025

Authority: CIS

Plugin: Unix

Revision: 1.0

Estimated Item Count: 95

File Details

Filename: CIS_Kubernetes_v1.11.1_L1_Master_Node.audit

Size: 246 kB

MD5: c284f6a3f8fe69fa402252b0b742a63f
SHA256: 0808f3901c918c0be93302f6d70755082fbbf6f15210975349c39dd6a22d7ea5

Audit Items

DescriptionCategories
1.1.1 Ensure that the API server pod specification file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.2 Ensure that the API server pod specification file ownership is set to root:root

ACCESS CONTROL

1.1.3 Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root

ACCESS CONTROL

1.1.5 Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root

ACCESS CONTROL

1.1.7 Ensure that the etcd pod specification file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.8 Ensure that the etcd pod specification file ownership is set to root:root

ACCESS CONTROL

1.1.9 Ensure that the Container Network Interface file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.10 Ensure that the Container Network Interface file ownership is set to root:root

ACCESS CONTROL

1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd

ACCESS CONTROL, MEDIA PROTECTION

1.1.13 Ensure that the default administrative credential file permissions are set to 600

ACCESS CONTROL, MEDIA PROTECTION

1.1.14 Ensure that the default administrative credential file ownership is set to root:root

ACCESS CONTROL

1.1.15 Ensure that the scheduler.conf file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.16 Ensure that the scheduler.conf file ownership is set to root:root

ACCESS CONTROL

1.1.17 Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive

ACCESS CONTROL, MEDIA PROTECTION

1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root

ACCESS CONTROL

1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root

ACCESS CONTROL, MEDIA PROTECTION

1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive

ACCESS CONTROL

1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600

ACCESS CONTROL, MEDIA PROTECTION

1.2.1 Ensure that the --anonymous-auth argument is set to false

ACCESS CONTROL, MEDIA PROTECTION

1.2.2 Ensure that the --token-auth-file parameter is not set

CONFIGURATION MANAGEMENT, MAINTENANCE

1.2.3 Ensure that the DenyServiceExternalIPs is set

CONFIGURATION MANAGEMENT, MAINTENANCE

1.2.4 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate

SYSTEM AND SERVICES ACQUISITION

1.2.5 Ensure that the --kubelet-certificate-authority argument is set as appropriate

SYSTEM AND SERVICES ACQUISITION

1.2.6 Ensure that the --authorization-mode argument is not set to AlwaysAllow

ACCESS CONTROL, MEDIA PROTECTION

1.2.7 Ensure that the --authorization-mode argument includes Node

ACCESS CONTROL, MEDIA PROTECTION

1.2.8 Ensure that the --authorization-mode argument includes RBAC

ACCESS CONTROL, AUDIT AND ACCOUNTABILITY

1.2.9 Ensure that the admission control plugin EventRateLimit is set

SYSTEM AND SERVICES ACQUISITION

1.2.10 Ensure that the admission control plugin AlwaysAdmit is not set

ACCESS CONTROL, MEDIA PROTECTION

1.2.11 Ensure that the admission control plugin AlwaysPullImages is set

ACCESS CONTROL, MEDIA PROTECTION

1.2.15 Ensure that the --profiling argument is set to false

AUDIT AND ACCOUNTABILITY

1.2.16 Ensure that the --audit-log-path argument is set

AUDIT AND ACCOUNTABILITY

1.2.17 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate

AUDIT AND ACCOUNTABILITY

1.2.18 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate

AUDIT AND ACCOUNTABILITY

1.2.19 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate

AUDIT AND ACCOUNTABILITY

1.2.20 Ensure that the --request-timeout argument is set as appropriate

CONFIGURATION MANAGEMENT

1.2.21 Ensure that the --service-account-lookup argument is set to true

ACCESS CONTROL, MEDIA PROTECTION

1.2.22 Ensure that the --service-account-key-file argument is set as appropriate

IDENTIFICATION AND AUTHENTICATION

1.2.23 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate

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

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

1.2.25 Ensure that the --client-ca-file argument is set as appropriate

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

1.2.26 Ensure that the --etcd-cafile argument is set as appropriate

IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

1.2.27 Ensure that the --encryption-provider-config argument is set as appropriate

IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

1.2.28 Ensure that encryption providers are appropriately configured

IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

1.2.29 Ensure that the API Server only makes use of Strong Cryptographic Ciphers

CONFIGURATION MANAGEMENT

1.2.30 Ensure that the --service-account-extend-token-expiration parameter is set to false

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate

SYSTEM AND INFORMATION INTEGRITY

1.3.2 Ensure that the --profiling argument is set to false

CONFIGURATION MANAGEMENT