Alibaba Cloud Kubernetes Engine clusters should not have the Kubernetes Dashboard (web UI) enabled. The Dashboard uses a highly privileged Service Account that can perform administrative operations across the cluster. Use the ACK Console instead, which provides fine-grained access control through RAM policies and RBAC integration.
Risk
The Kubernetes Dashboard uses a highly privileged Service Account with broad cluster access. If compromised through a vulnerability or unauthorized access, an attacker could gain full control over the cluster, deploy malicious workloads, exfiltrate secrets, and escalate privileges, impacting confidentiality, integrity, and availability of all workloads and data.
prowler alibabacloud --checks cs_kubernetes_dashboard_disabled
Recommendation
Delete the Kubernetes Dashboard deployment from the kube-system namespace using kubectl or the ACK Console. Use the ACK Console for cluster management instead of the Kubernetes Dashboard.
Remediation
kubectl delete deployment kubernetes-dashboard -n kube-system
- Log on to the ACK Console.
- Select the target cluster and select the
kube-systemnamespace in the Namespace pop-menu. - Input
dashboardin the deploy filter bar. - Make sure there is no result after the filter.
- If dashboard exists, delete the deployment by selecting Delete in the More pop-menu.
Source Code
Resource Type
ALIYUN::CS::ManagedKubernetesCluster