Cloud Lateral Movement
Pivoting between cloud workloads, accounts, or identities after initial access.
What it is
The act of moving from an initial foothold to additional resources, accounts, or identities within a cloud environment, often by abusing trust relationships, network reach, or chained roles. It is how a single compromise spreads across the estate.
Why it matters
Cloud movement frequently rides on legitimate identity and network paths rather than malware, so mapping trust and reachability is essential to predicting and reconstructing how an attacker spread.
In practice
An analyst traces movement from a compromised function, across an assumed role, into a separate account holding the prize data.
What to look for
- Role assumptions across accounts or projects in a short window.
- Use of instance credentials to reach other services.
- Access to secrets followed by logins elsewhere.
Common mistake
Scoping the incident to one account. Cloud trust relationships often reach further than the network does.
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
- Role Assumption: Temporarily taking on a role's permissions to act as a different identity.
- Security Groups and NACLs: Virtual firewall rules that filter traffic to cloud workloads and subnets.