Skip to main content

Security Exposure

Kubernetes documentation calls controlling who can access the API, and what they are allowed to do, the first line of defense for a cluster. Anonymous access is enabled by default when an authorization mode other than AlwaysAllow is used, and RBAC grants anonymous requests whatever is explicitly bound to system:anonymous or system:unauthenticated. Shadowserver reports API servers on 6443 and 443 that answer unauthenticated /version requests, noting they leak version and build details.

Hardening

  • Restrict 6443 to administrator networks, node subnets and CI systems with firewall or cloud security group rules.
  • Disable anonymous authentication with --anonymous-auth=false where health checks do not need it.
  • Use RBAC with least privilege and review bindings for system:anonymous and system:unauthenticated.
  • Enable API server audit logging, which Kubernetes describes as a chronological record of actions by users, applications and the control plane.
  • Keep the control plane on a supported Kubernetes release.

Monitoring

Enable Kubernetes audit logs and alert on requests from system:anonymous, failed authentications and changes to RBAC bindings or secrets.

Frequently Asked Questions

What is port 6443 used for?→

It is the default secure port of the Kubernetes API server. Kubernetes documentation notes that in a typical production cluster the API serves on 443, and the port is set with --secure-port.

Should the Kubernetes API be reachable from the internet?→

Shadowserver treats internet-accessible API servers as unnecessarily exposed attack surface, so access should be limited to trusted networks.

Port assignments from the IANA Service Name and Transport Protocol Port Number Registry. Services can be configured to run on any port, so traffic on port 6443 is not guaranteed to be Kubernetes API. Exploited-in-the-wild data from the CISA KEV catalog (CC0).