The API server should set up TLS connection for client authentication

문서 > Datadog 보안 > OOTB Rules > The API server should set up TLS connection for client authentication

Classification:

compliance

Framework:

cis-kubernetes

Control:

1.2.31

Set up the kubernetes integration.

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

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. 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.

Audit

Run the following command on the master node:

ps -ef | grep kube-apiserver

Verify that the --client-ca-file argument exists and it is 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 client certificate authority file: --client-ca-file=<path/to/client-ca-file>

Impact

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

Default value

By default, --client-ca-file argument is not set.

References

CIS controls

Version 6 14.2 Encrypt All Sensitive Information Over Less-trusted Networks - All communication of sensitive information over less-trusted networks should be encrypted. Whenever information flows over a network with a lower trust level, the information should be encrypted.

Version 7 14.4 Encrypt All Sensitive Information in Transit - Encrypt all sensitive information in transit.