The kubelet server certificate rotation on controller-manager should be enabled

문서 > Datadog 보안 > OOTB Rules > The kubelet server certificate rotation on controller-manager should be enabled

Classification:

compliance

Framework:

cis-kubernetes

Control:

1.3.6

Set up the kubernetes integration.

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Description

Enable kubelet server certificate rotation on controller-manager.

Rationale

RotateKubeletServerCertificate causes the kubelet to both request a serving certificate after bootstrapping its client credentials and rotate the certificate as its existing credentials expire. This automated periodic rotation ensures that the there are no downtimes due to expired certificates and thus addressing availability in the CIA security triad.

Note: This recommendation only applies if you let kubelets get their certificates from the API server. In case your kubelet certificates come from an outside authority/tool (e.g. Vault) then you need to take care of rotation yourself.

Audit

Run the following command on the master node:

ps -ef | grep kube-controller-manager

Verify that RotateKubeletServerCertificate argument exists and is set to true.

Remediation

Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml on the master node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.

--feature-gates=RotateKubeletServerCe`rtificate=true

Impact

None

Default value

By default, RotateKubeletServerCertificate is not set.

References

CIS controls

Version 6 14.2 Encrypt All Sensitive Information Over Less-trusted Networks All communication of sensitive information over less-trusted networks should be encrypted. Whenever information flows over a network with a lower trust level, the information should be encrypted.

Version 7 14.4 Encrypt All Sensitive Information in Transit Encrypt all sensitive information in transit.