CIS Kubernetes Benchmark v1.6.1 L1 Master

Audit Details

Name: CIS Kubernetes Benchmark v1.6.1 L1 Master

Updated: 4/25/2022

Authority: CIS

Plugin: Unix

Revision: 1.3

Estimated Item Count: 93

File Details

Filename: CIS_Kubernetes_v1.6.1_Level_1_Master.audit

Size: 201 kB

MD5: 1218e8a834cf8c4513e78f48d1bcdd6b
SHA256: 3d130700d7dce84a9285e64018714eba3d96e0b9820b8718902737891b2d17e7

Audit Items

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive

CONFIGURATION MANAGEMENT

1.1.14 Ensure that the admin.conf file ownership is set to root:root

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

CONFIGURATION MANAGEMENT

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

ACCESS CONTROL

1.2.2 Ensure that the --basic-auth-file argument is not set

IDENTIFICATION AND AUTHENTICATION

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

IDENTIFICATION AND AUTHENTICATION

1.2.4 Ensure that the --kubelet-https argument is set to true

SYSTEM AND COMMUNICATIONS PROTECTION

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

IDENTIFICATION AND AUTHENTICATION

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

IDENTIFICATION AND AUTHENTICATION

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

IDENTIFICATION AND AUTHENTICATION

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

SYSTEM AND INFORMATION INTEGRITY

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

SYSTEM AND INFORMATION INTEGRITY

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

SYSTEM AND INFORMATION INTEGRITY

1.2.10 Ensure that the admission control plugin EventRateLimit is set

SYSTEM AND COMMUNICATIONS PROTECTION, SYSTEM AND INFORMATION INTEGRITY

1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set

ACCESS CONTROL

1.2.12 Ensure that the admission control plugin AlwaysPullImages is set

ACCESS CONTROL

1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used

CONFIGURATION MANAGEMENT

1.2.14 Ensure that the admission control plugin ServiceAccount is set

ACCESS CONTROL

1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set

ACCESS CONTROL

1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set

ACCESS CONTROL

1.2.17 Ensure that the admission control plugin NodeRestriction is set

ACCESS CONTROL

1.2.18 Ensure that the --insecure-bind-address argument is not set

SYSTEM AND INFORMATION INTEGRITY

1.2.19 Ensure that the --insecure-port argument is set to 0

SYSTEM AND INFORMATION INTEGRITY

1.2.20 Ensure that the --secure-port argument is not set to 0

SYSTEM AND COMMUNICATIONS PROTECTION

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

ACCESS CONTROL

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

AUDIT AND ACCOUNTABILITY

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

AUDIT AND ACCOUNTABILITY

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

AUDIT AND ACCOUNTABILITY

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

AUDIT AND ACCOUNTABILITY

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

AUDIT AND ACCOUNTABILITY

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

ACCESS CONTROL

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

CONFIGURATION MANAGEMENT