More Info:
Verifies that —tls-cipher-suites is restricted to strong cipher suites so the API server does not negotiate weak or deprecated TLS ciphers.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
Back up the existing manifest (run on every control plane node):
-
Edit the API server manifest to set strong ciphers (run on every control plane node):
Open the file with a text editor:In thecommand:orargs:list forkube-apiserver, add or replace the existing--tls-cipher-suitesflag so it is exactly:Save and exit.
Operational impact: because this is a static pod manifest under/etc/kubernetes/manifests, the kubelet will automatically restart the API server with the new configuration. -
Confirm the API server pod has restarted (run on any machine with
kubectlaccess):Ensure theREADYstatus is1/1and theAGEreflects a recent restart compared to the time of your edit. -
Verify the running process uses only the configured strong ciphers (run on every control plane node):
Confirm the output exactly matches:
Using kubectl
Using kubectl
kubectl cannot modify the API server’s host-level configuration or its static pod manifest at
/etc/kubernetes/manifests/kube-apiserver.yaml on the control plane nodes. To remediate this finding, follow the guidance in the Manual Steps section to edit the manifest directly on each control plane node.Automation
Automation

