> 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/exchange-mailbox-delegation-permissions-added.md).

# Exchange mailbox delegation permissions added

### Synopsis

| Field                | Value                                                                   |
| -------------------- | ----------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                 |
| Training Period      | 30 Days                                                                 |
| Test Period          | 4 Hours                                                                 |
| Deduplication Period | 1 Day                                                                   |
| Required Data        | Office 365 Audit                                                        |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection, Email                    |
| ATT\&CK Tactic       | Persistence (TA0003)                                                    |
| ATT\&CK Technique    | Account Manipulation: Additional Email Delegate Permissions (T1098.002) |
| Severity             | Informational                                                           |

### Description

A user added delegation permissions to an Exchange mailbox.

### Attacker's Goals

Add delegation permissions to a mailbox for persistence reasons.

### 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).

### Variations

<details>

<summary>Addition of Exchange mailbox delegation permissions with suspicious characteristics</summary>

**Synopsis**

| Field             | Value                                                                   |
| ----------------- | ----------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003)                                                    |
| ATT\&CK Technique | Account Manipulation: Additional Email Delegate Permissions (T1098.002) |
| Severity          | Low                                                                     |

**Description**

A user added delegation permissions to an Exchange mailbox.

**Attacker's Goals**

Add delegation permissions to a mailbox for persistence reasons.

**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).

</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/exchange-mailbox-delegation-permissions-added.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.
