> 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/user-moved-exchange-sent-messages-to-deleted-items.md).

# User moved Exchange sent messages to deleted items

### Synopsis

| Field                | Value                                             |
| -------------------- | ------------------------------------------------- |
| Activation Period    | 14 Days                                           |
| Training Period      | 30 Days                                           |
| Test Period          | 10 Minutes                                        |
| Deduplication Period | 1 Day                                             |
| Required Data        | Office 365 Audit                                  |
| Detection Modules    | Identity Threat Module, Email                     |
| ATT\&CK Tactic       | Defense Evasion (TA0005)                          |
| ATT\&CK Technique    | Indicator Removal: Clear Mailbox Data (T1070.008) |
| Severity             | Informational                                     |

### Description

A user moved sent messages to deleted items in Exchange.

### Attacker's Goals

An attacker is attempting to hide newly sent email messages for evasion purposes.

### Investigative actions

* Look for signs that the user account and mailboxes are compromised (e.g. abnormal logins, unusual activity).
* Investigate the IP address associated with the activity.
* Follow further actions done by the account.
* Look for unusual email patterns from the affected mailbox (e.g. unusual email contents).
* Examine the user's email activity history for suspicious behavior.

### Variations

<details>

<summary>Sensitive Exchange sent messages moved to deleted items from unusual source</summary>

**Synopsis**

| Field             | Value                                             |
| ----------------- | ------------------------------------------------- |
| ATT\&CK Tactic    | Defense Evasion (TA0005)                          |
| ATT\&CK Technique | Indicator Removal: Clear Mailbox Data (T1070.008) |
| Severity          | Low                                               |

**Description**

A user moved sensitive sent messages to deleted items in Exchange.

**Attacker's Goals**

An attacker is attempting to hide newly sent email messages for evasion purposes.

**Investigative actions**

* Look for signs that the user account and mailboxes are compromised (e.g. abnormal logins, unusual activity).
* Investigate the IP address associated with the activity.
* Follow further actions done by the account.
* Look for unusual email patterns from the affected mailbox (e.g. unusual email contents).
* Examine the user's email activity history for suspicious behavior.

</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/user-moved-exchange-sent-messages-to-deleted-items.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.
