The Kubernetes etcd must use TLS to protect the confidentiality of sensitive data during electronic dissemination. (Cat II impact)
The Kubernetes API Server will prohibit the use of SSL and unauthorized versions of TLS protocols to properly secure communication. The use of unsupported protocol exposes vulnerabilities to the Kubernetes by rogue traffic interceptions, man-in-the-middle attacks, and impersonation of users or services from the container platform runtime, registry, and keystore. To enable the minimum version of TLS to be used by the Kubernetes API Server, the setting "peer-auto-tls" must be set.
Change to the /etc/kubernetes/manifests directory on the Kubernetes Master Node. Run the command: grep -I peer-auto-tls * If the setting "peer-auto-tls" is not configured in the Kubernetes etcd manifest file or it is set to "true", this is a finding.
Edit the Kubernetes etcd manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Master Node. Set the value of "peer-auto-tls" to "false".
The information system implements cryptographic mechanisms to protect the confidentiality of remote access sessions.
Protection Of Confidentiality / Integrity Using Encryption