Cloud Privilege Escalation
Abusing IAM relationships to gain higher access than originally granted.
What it is
The act of abusing permission misconfigurations, such as the ability to edit policies, create access keys, or pass roles, to elevate from limited access toward administrative control. Escalation paths in the cloud are usually identity logic rather than memory-corruption bugs.
Why it matters
Cloud escalation often hides in legitimate-looking API calls, so mapping the viable escalation paths in an environment is essential for both red teams and responders reconstructing how control was seized.
In practice
An investigator finds the attacker used a single permission to attach an admin policy to their own user, the lone step that unlocked the whole account.
What to look for
- A principal attaching policies to itself or creating new access keys for others.
- Passing a powerful role to a new function or instance.
- Changes to trust policies that let new principals assume a role.
Common mistake
Looking only for admin logins. Escalation usually happens through ordinary IAM API calls that grant more rights.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Over-Permissioned Role: An identity granted far more access than its actual job requires.
- Role Assumption: Temporarily taking on a role's permissions to act as a different identity.
- Access Keys: Static, long-lived credential pairs used to authenticate to cloud APIs.