More Info:
Ensure that the certificate authorities file has permissions of 644 or more restrictive.Risk Level
MediumAddress
SecurityCompliance Standards
- APRA CPS 234 (Australia)
- BSI C5 (Germany)
- Brazil LGPD
- CCPA / CPRA (California)
- CIS Critical Security Controls v8
- CIS EKS
- CMMC 2.0
- CSA Cloud Controls Matrix v4
- DPDPA
- Digital Operational Resilience Act (EU)
- Essential 8
- ISO/IEC 27017
- ISO/IEC 27018
- ISO/IEC 27701
- KSA PDPL
- MAS Technology Risk Management (Singapore)
- MITRE ATT&CK (Cloud)
- NIS2 Directive
- NIST SP 800-171
- NYDFS 23 NYCRR 500
- SWIFT Customer Security Controls Framework
- Sarbanes-Oxley IT General Controls
- UK NCSC Cyber Assessment Framework
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every worker node, check the current permissions of the kubelet configuration file:
-
On every worker node, set the kubelet configuration file permissions to 644:
-
(Optional, if you want to restrict ownership as well) On every worker node, ensure the file is owned by root:
-
On every worker node, verify the permissions are now 644 or more restrictive:
Using kubectl
Using kubectl
kubectl cannot change file permissions on worker node files such as
/var/lib/kubelet/config.yaml; this must be fixed directly on each worker node’s host filesystem. Use the guidance in the Manual Steps section to update the permissions and verify the fix.Automation
Automation

