⚠️ IMPORTANT DISCLAIMER: The tools and scripts on this site are provided "AS IS" for educational purposes.
Review destructive commands before executing. By using this site, you assume all risk and agree to our Full Terms of Service.
Wildcards and one or two quiet permissions turn a narrow role into an admin account. Paste an AWS IAM policy (JSON) or Kubernetes Role or ClusterRole (YAML) and get a risk report that flags broad actions, wildcard resources and known privilege-escalation combinations.
It grants every action on every resource in the account, which is full administrator access. Even "Action": "s3:*" on "Resource": "*" lets the holder read and delete every bucket. List the specific actions and the specific ARNs instead.
A user who can pass a powerful role to a service they control, such as a Lambda function or an EC2 instance, can run code with that role’s permissions. Restrict iam:PassRole to the exact role ARNs needed, and add an iam:PassedToService condition.
Wildcard verbs or resources (*), read access to secrets, create on pods/exec, the escalate, bind and impersonate verbs, and any binding to cluster-admin. Creating pods in a namespace is also powerful, because a pod can mount that namespace’s secrets and service accounts.
kubectl auth can-i --list --as=system:serviceaccount:NAMESPACE:NAME lists the permissions of a service account, and kubectl auth can-i delete pods --as=jane -n prod checks one action.
Usually. "Effect": "Allow" with "NotAction" grants everything except the listed actions, including services added later. Use it with Deny statements, not Allow.
Related tools: Terraform Plan Analyzer · Kubernetes Manifest Builder · Cloud VPC Planner · All tools A–Z
Most tools run entirely in your browser. Tools marked 📡 contact outside services, as listed in the Privacy Policy. Review commands before you run them; see the Terms.