Cluster-to-Cloud Lateral Movement

Cluster-to-Cloud Lateral Movement

A pod takes the node's cloud identity and walks out of the cluster.

What Is Cluster-to-Cloud Lateral Movement?

The cluster boundary is not the cloud boundary. From code execution in one low-value pod, you'll complete a metadata token exchange a pod should never reach, take the node's IAM role and read a claims archive the pod never touches. Then you'll lower the metadata hop limit, detach the workload permissions that never belonged on the node role, and revoke the sessions already issued, proving a pod request to metadata times out and the node role is denied the archive. Maps to OWASP Kubernetes Top Ten K08, Cluster-to-Cloud Lateral Movement.

What You'll Learn in Cluster-to-Cloud Lateral Movement

Cluster-to-Cloud Lateral Movement — Training Steps

  1. Inside a small pod

    Bob has code execution in one pod at Pemberlode, a health and travel insurer. The pod is nothing special: it resizes profile images for the member portal. He has a shell inside the container and starts by confirming where he is. The pod itself holds nothing worth taking. What matters is what the machine under it can reach.

  2. Ask for a metadata token

    The metadata service requires a session token first, so a single stray request cannot read it. Bob asks for one from inside the pod.

  3. Whose identity is on this node

    With the token, Bob asks the metadata service which role the node carries.

  4. Read the node's credentials

    The metadata service hands out the node role's temporary credentials to anything on the machine that asks with the token.

  5. Become the node

    Bob saves the three values into a profile and asks the cloud who he now is.

  6. Read what the node can reach

    Bob goes looking for data the pod never touches but the node role can. He streams the claims archive manifest straight to his terminal. It holds health and travel-medical claims: members, policy numbers, what was treated and what it cost.

  7. Check your understanding

  8. Node credentials used from outside

    Pemberlode's cloud threat detection flags the node role being used from an address that is not part of AWS.

  9. Can a pod reach metadata

    Alice establishes the first half: does a pod on that node reach the metadata service. She runs the token request from inside the thumbnailer pod herself.

  10. What the node role carries

    The second half: what can the node role actually do. Alice lists the policies attached to it.

Security Framework Coverage

OWASP Kubernetes Top 10

  • K08:2025 Cluster-to-Cloud Lateral Movement

CWE

  • CWE-522 Insufficiently Protected Credentials
  • CWE-668 Exposure of Resource to Wrong Sphere

MITRE ATT&CK

  • T1552.005 Unsecured Credentials: Cloud Instance Metadata API
  • T1078.004 Valid Accounts: Cloud Accounts

CIS Controls

  • CIS 4 Secure Configuration of Enterprise Assets and Software

NIST CSF

  • PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
  • PR.PS Platform Security

NICE Framework

  • IO-WRL-005 Systems Administration
  • DD-WRL-001 Cybersecurity Architecture