STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Kubernetes Security Technical Implementation Guide

V-242404

CAT II (Medium)

Kubernetes Kubelet must deny hostname override.

Rule ID

SV-242404r960960_rule

STIG

Kubernetes Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001499

Discussion

Kubernetes allows for the overriding of hostnames. Allowing this feature to be implemented within the kubelets may break the TLS setup between the kubelet service and the API server. This setting also can make it difficult to associate logs with nodes if security analytics needs to take place. The better practice is to setup nodes with resolvable FQDNs and avoid overriding the hostnames.

Check Content

On the Control Plane and Worker nodes, run the command:
ps -ef | grep kubelet

If the option "--hostname-override" is present, this is a finding.

Fix Text

Run the command:  
systemctl status kubelet.  
Note the path to the drop-in file.

Determine the path to the environment file(s) with the command: 
grep -i EnvironmentFile <path_to_drop_in_file>.

Remove the "--hostname-override" option from any environment file where it is present.  

Restart the kubelet service using the following command:
systemctl daemon-reload && systemctl restart kubelet