cyberstrikeus CIS Kubernetes Benchmark v2.0.0 - Control 2.3
Profile Applicability
- Level: 1 - Master Node
Description
Do not use self-signed certificates for TLS.
Rationale
etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should not be available to unauthenticated clients. You should enable the client authentication via valid certificates to secure the access to the etcd service.
Impact
Clients will not be able to use self-signed certificates for TLS.
Audit Procedure
Run the following command on the etcd server node:
ps -ef | grep etcd
Verify that if the --auto-tls argument exists, it is not set to true.
Remediation
Edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the master node and either remove the --auto-tls parameter or set it to false.
--auto-tls=false
Default Value
By default, --auto-tls is set to false.
References
- https://coreos.com/etcd/docs/latest/op-guide/security.html
- https://kubernetes.io/docs/admin/etcd/
- https://coreos.com/etcd/docs/latest/op-guide/configuration.html#auto-tls
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.11 Encrypt Sensitive Data at RestEncrypt sensitive data at rest on servers, applications, and databases containing sensitive data. Storage-layer encryption, also known as server-side encryption, meets the minimum requirement of this Safeguard. Additional encryption methods may include application-layer encryption, also known as client-side encryption, where access to the data storage device(s) does not permit access to the plain-text data. | ● | ● | |
| v7 | 14.4 Encrypt All Sensitive Information in TransitEncrypt all sensitive information in transit. | ● | ● |
Profile
Level 1 - Master Node (Automated)