What problem does it solve?
Kubernetes clusters often ship with overly permissive RBAC defaults—wildcard verbs, cluster-admin sprawl, and auto-mounted service account tokens—that enable privilege escalation and lateral movement. This Skill provides a structured methodology to audit, detect, and remediate dangerous RBAC configurations before attackers exploit them.
Core Features & Use Cases
- Misconfiguration Detection: Identify wildcard permissions, escalation verbs (escalate, bind, impersonate), token/exec paths, and aggregated ClusterRoles using kubectl and jq queries.
- Least-Privilege Implementation: Apply namespace-scoped Roles, dedicated service accounts per workload, and restricted permission sets with ready-to-use YAML manifests.
- RBAC Audit Workflow: Run a four-step audit covering binding enumeration, overprivileged service accounts, default service account usage, and token auto-mount verification.
- Use Case: A platform engineer preparing for a CIS Kubernetes Benchmark assessment uses this Skill to enumerate all cluster-admin bindings, replace them with namespace-scoped roles, integrate OIDC authentication, and verify effective access with kubectl auth can-i.
Quick Start
Audit my Kubernetes cluster for overprivileged RBAC bindings and generate least-privilege role manifests to replace cluster-admin grants.