Back to all scenarios
Scenario #243
Security
K8s v1.19, GKE
Exposed Dashboard Without Authentication
Kubernetes dashboard was exposed to the internet without authentication, allowing unauthorized users to access cluster information and potentially take control.
Find this helpful?
What Happened
The Kubernetes Dashboard was exposed to the public internet without proper authentication or authorization mechanisms, allowing attackers to view sensitive cluster information and even execute actions like deploying malicious workloads.
Diagnosis Steps
- 1Verified that the Kubernetes Dashboard was exposed via an insecure ingress.
- 2Discovered that no authentication or role-based access controls (RBAC) were applied to restrict access.
Root Cause
Misconfiguration of the Kubernetes Dashboard exposure settings allowed it to be publicly accessible.
Fix/Workaround
• Restricted access to the Kubernetes Dashboard by securing the ingress and requiring authentication via RBAC or OAuth.
• Implemented a VPN and IP whitelisting to ensure that only authorized users could access the dashboard.Lessons Learned
Always secure the Kubernetes Dashboard with proper authentication mechanisms and limit exposure to trusted users.
How to Avoid
- 1Use authentication and authorization to protect access to the Kubernetes Dashboard.
- 2Apply proper ingress and network policies to prevent exposure of critical services.