2.7 Ensure that a unique Certificate Authority is used for etcd

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


Use a different certificate authority for etcd from the one used for Kubernetes.


etcd is a highly available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. Its access should be restricted to specifically designated clients and peers only.

Authentication to etcd is based on whether the certificate presented was issued by a trusted certificate authority. There is no checking of certificate attributes such as common name or subject alternative name. As such, if any attackers were able to gain access to any certificate issued by the trusted certificate authority, they would be able to gain full access to the etcd database.


Additional management of the certificates and keys for the dedicated certificate authority will be required.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.


None required. Certificates for etcd are managed by the OpenShift cluster etcd operator.

Default Value:

By default, in OpenShift 4, communication with etcd is secured by the etcd serving CA.

See Also