> 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/cloud-storage-delete-protection-disabled.md).

# Cloud storage delete protection disabled

### Synopsis

| Field                | Value                                                                                                      |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                    |
| Training Period      | 30 Days                                                                                                    |
| Test Period          | N/A (single event)                                                                                         |
| Deduplication Period | 5 Days                                                                                                     |
| Required Data        | <p>Requires one of the following data sources:<br>AWS Audit Log OR Azure Audit Log OR Gcp Audit Log</p>    |
| Detection Modules    | Cloud                                                                                                      |
| Detector Tags        | Cloud Data Asset Disaster Recovery Risks, Cloud Data Asset Protection Tampering, Data Detection & Response |
| ATT\&CK Tactic       | Impact (TA0040)                                                                                            |
| ATT\&CK Technique    | Inhibit System Recovery (T1490)                                                                            |
| Severity             | Informational                                                                                              |

### Description

Delete protection of a cloud storage resource was disabled.

### Attacker's Goals

* Impair built-in protection of the cloud environment.
* This action may be a preliminary action before deleting the cloud resource itself.

### Investigative actions

* Confirm that the identity intended to disable deletion protection on this resource.
* Follow further actions done by the identity.
* Monitor this resource for other suspicious activities.

### Variations

<details>

<summary>Cloud storage delete protection disabled by an unusual identity</summary>

**Synopsis**

| Field             | Value                           |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic    | Impact (TA0040)                 |
| ATT\&CK Technique | Inhibit System Recovery (T1490) |
| Severity          | Informational                   |

**Description**

Delete protection of a cloud storage resource was disabled by an unusual identity.

**Attacker's Goals**

* Impair built-in protection of the cloud environment.
* This action may be a preliminary action before deleting the cloud resource itself.

**Investigative actions**

* Confirm that the identity intended to disable deletion protection on this resource.
* Follow further actions done by the identity.
* Monitor this resource for other suspicious activities.

</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/cloud-storage-delete-protection-disabled.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.
