> 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/sending-unusual-file-s-to-an-external-address.md).

# Sending unusual file(s) to an external address

### Synopsis

| Field                | Value                                                            |
| -------------------- | ---------------------------------------------------------------- |
| Activation Period    | 14 Days                                                          |
| Training Period      | 30 Days                                                          |
| Test Period          | N/A (single event)                                               |
| Deduplication Period | 1 Hour 30 Minutes                                                |
| Required Data        | Microsoft 365 Emails                                             |
| Detection Modules    | Email                                                            |
| Detector Tags        | Exfiltration                                                     |
| ATT\&CK Tactic       | Initial Access (TA0001), Exfiltration (TA0010)                   |
| ATT\&CK Technique    | Phishing (T1566), Exfiltration Over Alternative Protocol (T1048) |
| Severity             | Low                                                              |

### Description

Unusual files sent to an external address.

### Attacker's Goals

* Extracting sensitive credentials, potentially leading to account takeover or unauthorized access to internal services.
* Extracting valuable information outside the company.

### Investigative actions

* Check the content of the unusual files that were sent.
* Review the external recipient address and assess its reputation.
* Review past emails sent from this mailbox for any suspicious activity.
* Check for unusual emails sent to this recipient's address.
* Monitor further actions taken, such as accessing private keys, API tokens and sensitive data.


---

# 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/sending-unusual-file-s-to-an-external-address.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.