---
title: "Kubernetes Security: Lateral Movement Detection and Defense"
source: "https://www.tigera.io/blog/kubernetes-security-lateral-movement-detection-and-defense/"
description: "Watch this on-demand webinar, Detecting Lateral Movement and Defending Against Attackers, presented by Tigera security threat researcher Garwood Pang"
---

[Technical Blog](https://www.tigera.io/category/technical-blog/)

# Kubernetes Security: Lateral Movement Detection and Defense

By [John Armstrong](https://www.tigera.io/blog/author/john-armstrong/) on Jun 11, 2020 • 3 min read

**What is Lateral Movement?**

Lateral movement refers to the techniques that a cyber-attacker uses, after gaining initial access, to move deeper into a network in search of sensitive data and other high-value assets. [Lateral movement techniques](http://attack.mitre.org/tactics/TA0008/) are widely used in sophisticated cyber-attacks such as [advanced persistent threats (APTs)](http://en.wikipedia.org/wiki/Advanced_persistent_threat). An adversary uses these techniques to access other hosts from a compromised system and get access to sensitive resources, such as mail systems, shared folders, and legitimate credentials, ultimately gaining access to the identified target. Lateral movement techniques enable a threat actor to avoid detection and retain access over an extended dwell time of weeks, or even months, after the initial breach.

**What are the Stages of Lateral Movement?**

There are three primary stages of lateral movement: reconnaissance, credential/privilege gathering, and gaining access to other resources in the network.

**How Does an Adversary Gain Unauthorized Access to a Kubernetes Cluster?**

In a [Kubernetes](http://kubernetes.io/) cluster, an attacker will gain initial access by compromising a pod. Once the pod is compromised, there are three main areas where the attacker can begin reconnaissance and move through the lateral movement stages to learn more about the cluster: the cloud provider metadata service, the pod networking and filesystem, and the Kubernetes API service.

- The cloud provider metadata service is used by DevOps to manage and scale instances running in the cloud, and provides the attacker with access to hostname, network IP, custom attributes and IAM role credentials. The IAM credentials, in turn, enable access to other resources like S3 buckets, which the attacker can then probe.

- Breaching the pod networking and filesystem provides an attacker with access to IP, subnet, hostname, applications, capabilities and secrets. The attacker’s methodology is to gain as many permissions as possible within the pod.

- Lastly, the attacker can probe the Kubernetes API service, which can be found in the pod’s environment variable. Kubernetes APIs with Custom Resource Definitions (CRDs) are prime targets because they can enable an attacker to leverage other Kubernetes features like the CLI, API services, RBAC, etc.

Once an attacker secures administrative privileges and gains deeper access into a network, malicious lateral movement can be very difficult to detect because it can appear to be “normal” network traffic. Left undetected, an attacker using lateral movement techniques can cause significant disruption. So it’s essential to find and remove these intruders as quickly as possible to avoid costly losses.

**Detecting and Defending Against Lateral Movement**

Fortunately there are effective ways to detect lateral movement in a Kubernetes cluster. [Global Alerts](https://www.tigera.io/blog/five-ways-to-quickly-uncover-malicious-activity-and-protect-your-kubernetes-workloads/), a unique feature in Calico Enterprise, provides advanced threat and lateral movement detection capabilities for Kubernetes workloads in the private and public cloud. With [Calico Enterprise](https://www.tigera.io/tigera-products/calico-commercial-editions/) Global Alerts, you can quickly identify malicious behavior and significantly reduce dwell time by uncovering this activity in its early stages.

Ready to learn more about Calico? [Request a demo](https://www.tigera.io/demo/).

[Products](https://www.tigera.io/tags/products/)

## Related posts

[![Meet Mylo: An AI-native way to work with Calico](https://www.tigera.io/app/uploads/2026/09/Meet-Mylo-An-AI-native-way-to-work-with-Calico.png)](https://www.tigera.io/blog/meet-mylo-an-ai-native-way-to-work-with-calico/)

#### [Meet Mylo: An AI-native way to work with Calico](https://www.tigera.io/blog/meet-mylo-an-ai-native-way-to-work-with-calico/)

By [Phil DiCorpo](https://www.tigera.io/blog/author/phil-dicorpo/)
on Sep 3, 2026

A library of Calico tools and skills — delivered through the Calico MCP Server What if your hardest network question took ten minutes instead of ten days? Anyone who has operated Kubernetes networking at scale...

[Read more](https://www.tigera.io/blog/meet-mylo-an-ai-native-way-to-work-with-calico/)

[![The Safest Place to Run an AI Agent Is On a Cluster That Doesn’t Trust It](https://www.tigera.io/app/uploads/2026/08/The-Safest-Place-to-Run-an-AI-Agent-Is-On-a-Cluster-That-Doesnt-Trust-It.png)](https://www.tigera.io/blog/the-safest-place-to-run-an-ai-agent-is-on-a-cluster-that-doesnt-trust-it/)

#### [The Safest Place to Run an AI Agent Is On a Cluster That Doesn’t Trust It](https://www.tigera.io/blog/the-safest-place-to-run-an-ai-agent-is-on-a-cluster-that-doesnt-trust-it/)

By [Alister Baroi](https://www.tigera.io/blog/author/alister-baroi/)
on Aug 27, 2026

Every organization running AI agents has already made a hosting decision. Most made it by accident. The sales team switched on the agent built into their CRM. Engineering is piloting a coding agent in a...

[Read more](https://www.tigera.io/blog/the-safest-place-to-run-an-ai-agent-is-on-a-cluster-that-doesnt-trust-it/)

[![AI Red Team Agents Automate Attacks on your AI Agents. Runtime Policies Automate their Defense.](https://www.tigera.io/app/uploads/2026/08/AI-Red-Team-Agents-Automate-Attacks-on-your-AI-Agents.-Runtime-Policies-Automate-their-Defense.png)](https://www.tigera.io/blog/ai-red-team-agents-automate-attacks-on-your-ai-agents-runtime-policies-automate-their-defense/)

#### [AI Red Team Agents Automate Attacks on your AI Agents. Runtime Policies Automate their Defense.](https://www.tigera.io/blog/ai-red-team-agents-automate-attacks-on-your-ai-agents-runtime-policies-automate-their-defense/)

By [Alister Baroi](https://www.tigera.io/blog/author/alister-baroi/)
on Aug 24, 2026

The AI red teaming market grew up fast this year. OpenAI bought Promptfoo, Cisco and Microsoft shipped automated attack suites, and a seed-stage startup publicly compromised 50 of 55 live customer service bots. These platforms...

[Read more](https://www.tigera.io/blog/ai-red-team-agents-automate-attacks-on-your-ai-agents-runtime-policies-automate-their-defense/)

<!-- plugin=object-cache-pro client=phpredis metric#hits=3143 metric#misses=33 metric#hit-ratio=99.0 metric#bytes=1552442 metric#prefetches=0 metric#store-reads=174 metric#store-writes=11 metric#store-hits=166 metric#store-misses=22 metric#sql-queries=28 metric#ms-total=616.78 metric#ms-cache=55.53 metric#ms-cache-avg=0.3018 metric#ms-cache-ratio=9.0 sample#redis-hits=33821894 sample#redis-misses=9499611 sample#redis-hit-ratio=78.1 sample#redis-ops-per-sec=69 sample#redis-evicted-keys=0 sample#redis-used-memory=138462624 sample#redis-used-memory-rss=110817280 sample#redis-memory-fragmentation-ratio=0.8 sample#redis-connected-clients=1 sample#redis-tracking-clients=0 sample#redis-rejected-connections=0 sample#redis-keys=124798 -->
