cyberstrikeus 1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root (Automated)
Profile Applicability
- Level 1 - Master Node
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.
Impact
None
Audit
Run the below command (based on the file location on your system) on the Control Plane node. For example,
stat -c %U:%G /etc/kubernetes/manifests/kube-controller-manager.yaml
Verify that the ownership is set to root:root.
Remediation
Run the below command (based on the file location on your system) on the Control Plane node. For example,
chown root:root /etc/kubernetes/manifests/kube-controller-manager.yaml
Default Value
By default, kube-controller-manager.yaml file ownership is set to root:root.
References
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts - Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account. | * | * | * |
| v7 | 4 Controlled Use of Administrative Privileges - Controlled Use of Administrative Privileges |