The kubelet service file should be owned by root:root

kubernetes

Classification:

compliance

Framework:

cis-kubernetes

Control:

4.1.2

Set up the kubernetes integration.

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

Description

Ensure that the kubelet service file ownership is set to root:root.

Rationale

The kubelet service file controls various parameters that set the behavior of the kubelet service in the worker node. You should set its file ownership to maintain the integrity of the file. The file should be owned by root:root.

Audit

Run the following command (based on the file location on your system) on the each worker node. For example, stat -c %U:%G /etc/systemd/system/kubelet.service.d/10-kubeadm.conf. Verify that the ownership is set to root:root.

Remediation

Run the below command (based on the file location on your system) on the each worker node.

For example, chown root:root /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

Impact

None

Default value

By default, kubelet service file ownership is set to root:root.

References

  1. https://kubernetes.io/docs/admin/kubelet/
  2. https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#44-joining-your-nodes
  3. https://kubernetes.io/docs/admin/kubeadm/#kubelet-drop-in

CIS controls

Version 6.5.1 Minimize And Sparingly Use Administrative Privileges - Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior.

Version 7.5.2 Maintain Secure Images - Maintain secure images or templates for all systems in the enterprise based on the organization’s approved configuration standards. Any new system deployment or existing system that becomes compromised should be imaged using one of those images or templates.

PREVIEWING: bryce/soar-blog