CNTR-K8-000310 - The Kubernetes Controller Manager must have secure binding.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Limiting the number of attack vectors and implementing authentication and encryption on the endpoints available to external sources is paramount when securing the overall Kubernetes cluster. The Controller Manager API service exposes port 10252/TCP by default for health and metrics information use. This port does not encrypt or authenticate connections. If this port is exposed externally, an attacker can use this port to attack the entire Kubernetes cluster. By setting the bind address to only localhost (i.e., 127.0.0.1), only those internal services that require health and metrics information can access the Control Manager API.

Solution

Edit the Kubernetes Controller Manager manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Control Plane. Set the argument '--bind-address' to '127.0.0.1'.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Kubernetes_V1R8_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000213, Rule-ID|SV-242385r863961_rule, STIG-ID|CNTR-K8-000310, Vuln-ID|V-242385

Plugin: Unix

Control ID: adb8c3aac316b66c1eda4fbdb0d66854b3450887242b8d10b822e098f1d46885