Kubernetes Dashboard reachable without authentication
The Kubernetes Dashboard, when exposed and bound to a privileged service account, lets anyone who reaches it deploy workloads and read secrets across the cluster — a well-known attack path.
Why it matters
Past incidents (including large crypto-mining campaigns) started with a Dashboard exposed to the internet with cluster-admin rights.
Even internal exposure is risky if any compromised pod can reach it.
How to check for it
- Check whether the Dashboard Service is of type LoadBalancer/NodePort or behind an unauthenticated Ingress.
- Review the ClusterRoleBinding on its service account — it should not be cluster-admin.
How to fix it
- Don't expose the Dashboard publicly; reach it via kubectl proxy or an authenticated ingress with SSO.
- Bind it to a least-privilege role, and prefer kubectl / GitOps over the Dashboard for changes.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Should we run the Dashboard at all?
- Many teams skip it in favour of kubectl and GitOps. If you keep it, put it behind SSO and least privilege.