> 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/ml-artifacts-destruction.md).

# ML artifacts destruction

### Synopsis

| Field                | Value                                                                                |
| -------------------- | ------------------------------------------------------------------------------------ |
| Activation Period    | 14 Days                                                                              |
| Training Period      | 30 Days                                                                              |
| Test Period          | 1 Hour                                                                               |
| Deduplication Period | 5 Days                                                                               |
| Required Data        | <p>Requires one of the following data sources:<br>AWS Audit Log OR Gcp Audit Log</p> |
| Detection Modules    | Cloud                                                                                |
| Detector Tags        | Cloud AI Infrastructure Analytics                                                    |
| ATT\&CK Tactic       | Impact (TA0040)                                                                      |
| ATT\&CK Technique    | Data Destruction (T1485)                                                             |
| Severity             | Low                                                                                  |

### Description

An identity deleted multiple ML artifacts.

### Attacker's Goals

Leverage access to the cloud to delete resources and cause damage to an organization's infrastructure.

### Investigative actions

* Confirm the legitimacy of the suspected identity and what cloud resources have been deleted by the identity.
* Look for any unusual activity associated with the suspected identity and determine whether they are compromised.

### Variations

<details>

<summary>Unusual ML artifacts destruction</summary>

**Synopsis**

| Field             | Value                    |
| ----------------- | ------------------------ |
| ATT\&CK Tactic    | Impact (TA0040)          |
| ATT\&CK Technique | Data Destruction (T1485) |
| Severity          | Medium                   |

**Description**

An identity deleted multiple ML artifacts. This large volume of deleted ML artifacts had not been seen across all projects for the last 30 days.

**Attacker's Goals**

Leverage access to the cloud to delete resources and cause damage to an organization's infrastructure.

**Investigative actions**

* Confirm the legitimacy of the suspected identity and what cloud resources have been deleted by the identity.
* Look for any unusual activity associated with the suspected identity and determine whether they are compromised.

</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/ml-artifacts-destruction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
