cyberstrikeus 1.2.24 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)
Profile Applicability
- Level 1 - Master Node
Description
Setup TLS connection on the API server.
Rationale
API server communication contains sensitive parameters that should remain encrypted in transit. Configure the API server to serve only HTTPS traffic.
Impact
TLS and client certificate authentication must be configured for your Kubernetes cluster deployment.
Audit
Run the following command on the Control Plane node:
ps -ef | grep kube-apiserver
Verify that the --tls-cert-file and --tls-private-key-file arguments exist and they are set as appropriate.
Remediation
Follow the Kubernetes documentation and set up the TLS connection on the apiserver. Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the TLS certificate and private key file parameters.
--tls-cert-file=<path/to/tls-certificate-file>
--tls-private-key-file=<path/to/tls-key-file>
Default Value
By default, --tls-cert-file and --tls-private-key-file are presented and created for use.
References
- https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
- https://github.com/kelseyhightower/docker-kubernetes-tls-guide
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.10 Encrypt Sensitive Data in Transit | * | * | |
| v7 | 14.4 Encrypt All Sensitive Information in Transit | * | * |