Title

Kubernetes Controller Manager must have the SSL Certificate Authority set. (Cat II impact)

Discussion

The Kubernetes Controller Manager is responsible for creating service accounts and tokens for the API Server, maintaining the correct number of pods for every replication controller and provides notifications when nodes are offline. Anyone who gains access to the Controller Manager can generate backdoor accounts, take possession of, or diminish system performance without detection by disabling system notification. Using authenticity protection, the communication can be protected against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. The communication session is protected by utilizing transport encryption protocols, such as TLS. TLS provides the Kubernetes Controller Manager with a means to be able to authenticate sessions and encrypt traffic.

Check Content

Change to the /etc/kubernetes/manifests/ directory on the Kubernetes Control Plane. Run the command: grep -i root-ca-file * If the setting client-ca-file is not set in the Kubernetes Controller Manager manifest file or contains no value, this is a finding.

Fix Text

Edit the Kubernetes Controller Manager manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Control Plane. Set the value of root-ca-file to path containing Approved Organizational Certificate.

Additional Identifiers

Rule ID: SV-242421r879636_rule

Vulnerability ID: V-242421

Group Title: SRG-APP-000219-CTR-000550

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.