Etcd is configured to require TLS client certificate authentication when the etcd container includes --client-cert-auth, so client access is validated with trusted certificates.
Risk
Without mTLS client auth, any reachable client can query or mutate etcd:
- Confidentiality: exposure of Secrets and cluster metadata
- Integrity: tampering with RBAC, pods, and configs
- Availability: destructive writes can disrupt the control plane
Run this check with Prowler CLI
prowler kubernetes --checks etcd_client_cert_auth
Recommendation
Enforce mutual TLS for etcd clients by requiring validated certificates (--client-cert-auth=true) issued by a trusted CA.
Restrict network access to etcd to API servers, rotate keys regularly, and apply least privilege and separation of duties for certificate management.
Remediation
Terraform
Other
- SSH to the control plane node that runs etcd
- Edit the static pod manifest: /etc/kubernetes/manifests/etcd.yaml
- Under spec.containers[0].command (or args), add:
- --client-cert-auth=true # Critical: enables client certificate authentication - Save the file; kubelet will restart the etcd pod automatically
- Repeat on each control-plane node hosting an etcd pod
Source Code
Resource Type
Pod