> 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-resource-deletion-via-docker-sock.md).

# Docker resource deletion via docker.sock

### Synopsis

| Field                | Value                                                                                                      |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                    |
| Training Period      | 30 Days                                                                                                    |
| Test Period          | N/A (single event)                                                                                         |
| Deduplication Period | 1 Day                                                                                                      |
| Required Data        | XDR Agent                                                                                                  |
| Detector Tags        | Containers                                                                                                 |
| ATT\&CK Tactic       | Impact (TA0040), Stealth (TA0005), Defense Impairment (TA0112)                                             |
| ATT\&CK Technique    | Service Stop (T1489), Indicator Removal (T1070), Data Destruction (T1485), Disable or Modify Tools (T1685) |
| Severity             | Informational                                                                                              |

### Description

A process inside a container sent an HTTP DELETE request to the Docker Engine API over a container runtime socket to delete a container, image, network or volume. The command line is rare in the organization.

### Attacker's Goals

Delete Docker resources (containers, images, networks, volumes) from inside a container to disrupt services, destroy evidence, or remove a security agent.

### 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.
* Identify the deleted resource and whether it was a security, monitoring or production workload container.
* Review the full command-line history of the actor process for follow-on container escape or evidence-destruction attempts.
* Look for other containers/hosts executing similar docker.sock delete operations.

### Variations

<details>

<summary>Docker resource deletion via docker.sock targeting a security agent container</summary>

**Synopsis**

| Field             | Value                                                                                                      |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Impact (TA0040), Stealth (TA0005), Defense Impairment (TA0112)                                             |
| ATT\&CK Technique | Service Stop (T1489), Indicator Removal (T1070), Data Destruction (T1485), Disable or Modify Tools (T1685) |
| Severity          | Medium                                                                                                     |

**Description**

A process inside a container sent an HTTP DELETE request to the Docker Engine API over a container runtime socket to delete a container whose name matches a security or monitoring agent.

**Attacker's Goals**

Delete Docker resources (containers, images, networks, volumes) from inside a container to disrupt services, destroy evidence, or remove a security agent.

**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.
* Identify the deleted resource and whether it was a security, monitoring or production workload container.
* Review the full command-line history of the actor process for follow-on container escape or evidence-destruction attempts.
* Look for other containers/hosts executing similar docker.sock delete operations.

</details>

<details>

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

**Synopsis**

| Field             | Value                                                                                                      |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Impact (TA0040), Stealth (TA0005), Defense Impairment (TA0112)                                             |
| ATT\&CK Technique | Service Stop (T1489), Indicator Removal (T1070), Data Destruction (T1485), Disable or Modify Tools (T1685) |
| Severity          | Low                                                                                                        |

**Description**

A process inside a container sent an HTTP DELETE request to the Docker Engine API over a container runtime socket to delete a container, image, network or volume. The command line is rare in the organization.

**Attacker's Goals**

Delete Docker resources (containers, images, networks, volumes) from inside a container to disrupt services, destroy evidence, or remove a security agent.

**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.
* Identify the deleted resource and whether it was a security, monitoring or production workload container.
* Review the full command-line history of the actor process for follow-on container escape or evidence-destruction attempts.
* Look for other containers/hosts executing similar docker.sock delete operations.

</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-resource-deletion-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.
