> 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/deletion-of-multiple-cloud-resources.md).
# Deletion of multiple cloud resources
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 30 Minutes |
| Deduplication Period | 5 Days |
| Required Data | Requires one of the following data sources:
AWS Audit Log OR Azure Audit Log OR Gcp Audit Log
|
| Detection Modules | Cloud |
| Detector Tags | OCI Analytics |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Data Destruction (T1485) |
| Severity | Informational |
### Description
An identity deleted multiple cloud resources.
### 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
Deletion of multiple cloud resources
**Synopsis**
| Field | Value |
| ----------------- | ------------------------ |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Data Destruction (T1485) |
| Severity | Medium |
**Description**
An identity deleted multiple cloud resources. This large volume of deleted cloud resources 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.
Deletion of multiple cloud resources
**Synopsis**
| Field | Value |
| ----------------- | ------------------------ |
| ATT\&CK Tactic | Impact (TA0040) |
| ATT\&CK Technique | Data Destruction (T1485) |
| Severity | Low |
**Description**
An identity deleted multiple cloud resources. This large volume of deleted cloud resources had not been seen in this project 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.
---
# 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/deletion-of-multiple-cloud-resources.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.