cyberstrikeus 1.1.3 Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)
Profile Applicability
- Level 1 - Master Node
Description
Ensure that the controller manager pod specification file has permissions of 600 or more restrictive.
Rationale
The controller manager pod specification file controls various parameters that set the behavior of the Controller Manager on the master node. You should restrict its file permissions to maintain the integrity of the file. The file should be writable by only the administrators on the system.
Impact
None
Audit
Run the below command (based on the file location on your system) on the Control Plane node. For example,
stat -c %a /etc/kubernetes/manifests/kube-controller-manager.yaml
Verify that the permissions are 600 or more restrictive.
Remediation
Run the below command (based on the file location on your system) on the Control Plane node. For example,
chmod 600 /etc/kubernetes/manifests/kube-controller-manager.yaml
Default Value
By default, the kube-controller-manager.yaml file has permissions of 640.
References
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.3 Configure Data Access Control Lists - Configure data access control lists based on a user's need to know. Apply data access control lists, also known as access permissions, to local and remote file systems, databases, and applications. | * | * | * |
| v7 | 14.6 Protect Information through Access Control Lists - Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. | * | * | * |