Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers

MediumLevel 1Manual reviewopenshift

Description

Ensure that the Kubelet is configured to only use strong cryptographic ciphers. The benchmark marks this recommendation Manual.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

The set of cryptographic ciphers currently considered secure is the following: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_GCM_SHA256 Ciphers for the API servers, authentication and the ingress controller can be configured using the tlsSecurityProfile parameter as of OpenShfit 4.3.

How it is fixed

Fix method: Guidance or infrastructure patch

Follow the directions above and in the OpenShift documentation to configure the tlsSecurityProfile. Configuring Ingress. Please reference the OpenShift TLS security profile documentation for more detail on each profile.

Properties

Operating systems: Any
Tags: openshiftworker-nodekubelet
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 4.2.12 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers