The controller manager pod specification file ownership should be root:root
Set up the kubernetes integration.
Description
Ensure that the controller manager pod specification file ownership is set to root:root.
Rationale
The controller manager pod specification file controls various parameters that set the behavior of various components of the master 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 below command (based on the file location on your system) on the master node.
stat -c %U:%G /etc/kubernetes/manifests/kube-controller-manager.yaml
Verify the ownership is set to root:root.
Run the below command (based on the file location on your system) on the master node. For example, chown root:root /etc/kubernetes/manifests/kube-controller-manager.yaml
Impact
None
Default value
By default, kube-controller-manager.yaml file ownership is set to root:root.
References
- https://kubernetes.io/docs/admin/kube-controller-manager
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.
