> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/runtime-defense/incident-types/lateral-movement.md).
# Lateral movement
Lateral movement incidents indicate that an attacker is using tools and techniques that enable movement between resources on a network.
## Investigation
The following incident shows that netcat was used to establish a listener on port 9000.
This behavior is a probable precursor to creating a reverse shell, allowing network-based remote control of another resource.
Your investigation should focus on:
* Determining how the process in the alert, such as *nc.openbsd*, was executed. Review additional entries in Incident Explorer and other audits from the source, looking for unusual process execution, and explicit execution of commands.
* Reviewing container runtime audits to determine if the target successfully connected.
* If the target did successfully connect, determine what the attacker was able to do and if they were able to move further through the network.
## Mitigation
After determining the cause of the process execution, resolve the problem, whether it be an exposed vulnerability, a configuration issue, or something else.
For additional protection, enable the *prevent* or *block* actions in the applicable runtime rules to take action when anomalous processes, such as *netcat*, are executed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.prismacloud.io/admin-guide/runtime-defense/incident-types/lateral-movement.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
