1. Home
  2. Security Hardening
  3. CIS Kubernetes 1.8 Benchmark V1.2.0 L1
  4. Ensure that the –client-ca-file argument is set as appropriate

Ensure that the –client-ca-file argument is set as appropriate

Details

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. If ‘–client-ca-file’ argument is set, any request presenting a client certificate signed by one of the authorities in the ‘client-ca-file’ is authenticated with an identity corresponding to the CommonName of the client certificate.

Solution

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 client certificate authority file.

–client-ca-file=

Impact:

TLS and client certificate authentication must be configured for your Kubernetes cluster deployment.

Supportive Information

The following resource is also helpful.

This security hardening control applies to the following category of controls within NIST 800-53: Identification and Authentication.This control applies to the following type of system Unix.

References

Source

Updated on July 16, 2022
Was this article helpful?

Related Articles