Created by Claudiu Tabac - © 2026
This material is open for educational and research use. Commercial use without explicit permission from the author is not allowed.
Stage 7 Identity-Based Lateral Movement
What Happens in Stage 7
Identity-Based Lateral Movement occurs when adversaries leverage valid, authenticated identity tokens or elevated privileges to traverse cloud services, SaaS applications, enterprise systems, resource tenants, hybrid infrastructure, CI/CD pipelines, and machine identity networks. This represents lateral movement without malware—attackers navigate using identity, not exploits.
Cloud-Native Pivoting
Attackers impersonate legitimate users, administrators, service principals, or machine identities to pivot through any system that trusts those credentials.
Cross-Environment Movement
Movement spans from SaaS to cloud, cloud to SaaS, between tenants, and across user to app to machine identity chains.
Zero Malware Required
Identity serves as the universal passport—no exploits, no abnormal binaries, no EDR triggers, just authenticated movement.
Attacker Objectives
1
Cross-Platform Pivots
Pivot from SaaS to cloud infrastructure, cloud to SaaS applications, and between isolated tenants using identity trust.
2
Identity Chain Escalation
Move strategically from user accounts to application identities to machine credentials, escalating across resource providers.
3
Resource Access
Reach internal systems via SSO trust relationships to access compute resources, storage systems, and sensitive data repositories.
Misconfigurations That Enable Lateral Movement
MC-062: Excessive Cloud IAM Permissions
Overprivileged cloud roles allow attackers to move freely between cloud services, accessing resources far beyond legitimate business requirements.
MC-107: Weak Directory Role Governance
Stale or high-value directory roles enable identity pivoting through dormant administrative accounts that retain excessive privileges.
MC-134: Hidden Role Assignments via Nested Groups
Indirect privilege assignments through deeply nested group memberships create pivot paths that evade traditional security monitoring.
MC-093: Weak Multi-Cloud Integration Governance
Trust misconfigurations in cross-cloud integrations enable attackers to move seamlessly between disparate cloud environments.
MC-146: Inconsistent Identity Trust Boundaries
Poorly defined trust boundaries allow cross-tenant and cross-environment pivoting through misconfigured federation relationships.
MC-138: Overprivileged Machine Identities
Service accounts and API credentials with excessive permissions enable machine-to-machine lateral movement across automated systems.
Detection, Patterns, and Threat Intelligence
Detection Logic for Stage 7
DL-052: Machine Identity Host Anomaly
Detects machine identity tokens used from non-associated hosts, indicating credential theft or replay attacks.
DL-056: Cross-Application Token Replay
Identifies tokens reused across unrelated cloud or SaaS applications, revealing lateral movement patterns.
DL-072: Cross-Cloud Role Activation
Flags privilege activation across different cloud providers, indicating multi-cloud lateral movement.
DL-041: High-Sensitivity Access Spike
Detects sudden spikes in privileged or sensitive operations that deviate from baseline behavior patterns.
Breach Patterns Using Stage 7
BP-015: Machine Identity Token Replay
BP-018: SAML Trust Manipulation
BP-021: App Roles to Admin Escalation
BP-034: Machine Identity Privilege Drift
BP-040: Cross-Cloud Lateral Identity Pivot
Threat Actors Exploiting Stage 7
Volt Typhoon (ICTAM-004)
Sophisticated hybrid identity pivoting across on-premises and cloud infrastructure for espionage operations.
BlackCat (ICTAM-009)
Machine identity movement through automated systems and CI/CD pipelines for ransomware deployment.
APT28 (ICTAM-002)
Federation-based lateral movement exploiting SAML and OAuth trust relationships for persistent access.
LockBit (ICTAM-011)
User-to-app-to-cloud pivots leveraging compromised credentials for widespread encryption campaigns.
Automation Identity Hijacker (ICTAM-023)
Pipeline pivots through DevOps infrastructure targeting software supply chain compromise.
Stage 7 in the Attack Chain
Identity-based movement represents the cloud-native evolution of lateral movement. Unlike traditional network-based pivoting, this stage operates entirely through authentication and authorization mechanisms—no malware, no exploits, no abnormal binaries, and no EDR triggers. Defenders must shift from detecting malicious files to identifying anomalous identity behavior patterns across distributed systems.
1
Stage 5: PrivEsc
2
Stage 6: Token Hijack
3
Stage 7: Lateral
4
Stage 8: Persistence
About
Created by Claudiu Tabac — © 2026
This framework is open for educational and research use. Commercial use without explicit permission from the author is not allowed.
Navigation