Under active development Content is continuously updated and improved

V-242390The Kubernetes API server must have anonymous authentication disabled.

CAT I - High
CNTR-K8-000360

>Control Description

The Kubernetes API Server controls Kubernetes via an API interface. A user who has access to the API essentially has root access to the entire Kubernetes cluster. To control access, users must be authenticated and authorized. By allowing anonymous connections, the controls put in place to secure the API can be bypassed. Setting "--anonymous-auth" to "false" also disables unauthenticated requests from kubelets. While there are instances where anonymous connections may be needed (e.g., health checks) and Role-Based Access Controls (RBACs) are in place to limit the anonymous access, this access should be disabled, and only enabled when necessary.

>Check Content

Change to the /etc/kubernetes/manifests directory on the Kubernetes Control Plane.

$grep -i anonymous-auth *

If the setting "--anonymous-auth" is set to "true" in the Kubernetes API Server manifest file, this is a finding.

>Remediation

Edit the Kubernetes API Server manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Control Plane. Set the value of "--anonymous-auth" to "false".

>CCI References

Control Correlation Identifiers (CCIs) map STIG findings to NIST 800-53 controls.

>Cross-Framework Mappings

NIST SP 800-53 r5

via DISA CCI List

Ask AI

Configure your API key to use AI features.