> 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-user-performed-multiple-actions-that-were-denied.md).

# Cloud user performed multiple actions that were denied

### Synopsis

| Field                | Value                                                                                                   |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                 |
| Training Period      | 30 Days                                                                                                 |
| Test Period          | 10 Minutes                                                                                              |
| 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                                                                                                   |
| ATT\&CK Tactic       | Discovery (TA0007)                                                                                      |
| ATT\&CK Technique    | Account Discovery (T1087), Permission Groups Discovery (T1069)                                          |
| Severity             | Informational                                                                                           |

### Description

An identity performed multiple actions that were denied, which may indicate it is being misused.

### Attacker's Goals

Execute various commands to explore the cloud environment.

### Investigative actions

Check if the API calls were made by the identity. Check if there are additional calls executed by the identity.

### Variations

<details>

<summary>Cloud non-user identity performed multiple actions that were denied</summary>

**Synopsis**

| Field             | Value                                                          |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic    | Discovery (TA0007)                                             |
| ATT\&CK Technique | Account Discovery (T1087), Permission Groups Discovery (T1069) |
| Severity          | Low                                                            |

**Description**

An identity performed multiple actions that were denied, which may indicate it is being misused.

**Attacker's Goals**

Execute various commands to explore the cloud environment.

**Investigative actions**

Check if the API calls were made by the identity. Check if there are additional calls executed by the identity.

</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/cloud-user-performed-multiple-actions-that-were-denied.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.
