> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/docker-state-manipulation-via-docker-sock.md).

# Docker state manipulation via docker.sock

### Synopsis

| Field                | Value                                                                          |
| -------------------- | ------------------------------------------------------------------------------ |
| Activation Period    | 14 Days                                                                        |
| Training Period      | 30 Days                                                                        |
| Test Period          | 10 Minutes                                                                     |
| Deduplication Period | 1 Day                                                                          |
| Required Data        | XDR Agent                                                                      |
| Detector Tags        | Containers                                                                     |
| ATT\&CK Tactic       | Execution (TA0002), Persistence (TA0003), Impact (TA0040)                      |
| ATT\&CK Technique    | Deploy Container (T1610), Implant Internal Image (T1525), Service Stop (T1489) |
| Severity             | Informational                                                                  |

### Description

A process inside a container issued state-changing Docker Engine API requests over the docker.sock to manipulate the state of the Docker environment.

### Attacker's Goals

Manipulate the Docker environment from inside a container (start/stop/restart containers, load or create images, delete networks) to deploy malicious workloads, disrupt services, or escape to the host.

### Investigative actions

* Verify whether the process and container legitimately require write access to docker.sock.
* Inspect the container's mounts to confirm docker.sock is exposed.
* Review the full command-line history of the actor process for follow-on container escape, malicious image deployment, or service-disruption attempts.
* Look for other containers/hosts executing similar docker.sock state-manipulation commands.

### Variations

<details>

<summary>Docker state manipulation via docker.sock using a first-seen command line</summary>

**Synopsis**

| Field             | Value                                                                          |
| ----------------- | ------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Execution (TA0002), Persistence (TA0003), Impact (TA0040)                      |
| ATT\&CK Technique | Deploy Container (T1610), Implant Internal Image (T1525), Service Stop (T1489) |
| Severity          | Low                                                                            |

**Description**

A process inside a container issued state-changing Docker Engine API requests over the docker.sock to manipulate the state of the Docker environment.

**Attacker's Goals**

Manipulate the Docker environment from inside a container (start/stop/restart containers, load or create images, delete networks) to deploy malicious workloads, disrupt services, or escape to the host.

**Investigative actions**

* Verify whether the process and container legitimately require write access to docker.sock.
* Inspect the container's mounts to confirm docker.sock is exposed.
* Review the full command-line history of the actor process for follow-on container escape, malicious image deployment, or service-disruption attempts.
* Look for other containers/hosts executing similar docker.sock state-manipulation commands.

</details>


---

# 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://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/docker-state-manipulation-via-docker-sock.md?ask=<question>&goal=<user_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.