> 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/email-with-file-sharing-link-containing-auto-download-parameter.md).

# Email with file-sharing link containing auto-download parameter

### 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        | Malicious URLs                                                                       |
| ATT\&CK Tactic       | Initial Access (TA0001), Execution (TA0002)                                          |
| ATT\&CK Technique    | Phishing: Spearphishing Link (T1566.002), User Execution: Malicious File (T1204.002) |
| Severity             | Low                                                                                  |

### Description

The email contains a link to a file-sharing service that includes parameters likely to trigger automatic download.

### Attacker's Goals

The attacker may be attempting to deliver malware or exfiltrate data using auto-download file-sharing links.

### Investigative actions

* Analyze the linked file(s) to determine if they pose any security risk.
* Check the sender's communication history within the organization.
* Analyze the file reputation using sandbox or threat intelligence sources.
* Verify whether similar links were sent to other users.

### Variations

<details>

<summary>External email with file-sharing link containing auto-download parameter</summary>

**Synopsis**

| Field             | Value                                                                                |
| ----------------- | ------------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Initial Access (TA0001), Execution (TA0002)                                          |
| ATT\&CK Technique | Phishing: Spearphishing Link (T1566.002), User Execution: Malicious File (T1204.002) |
| Severity          | Low                                                                                  |

**Description**

The email contains a link to a file-sharing service that includes parameters likely to trigger automatic download.

**Attacker's Goals**

The attacker may be attempting to deliver malware or exfiltrate data using auto-download file-sharing links.

**Investigative actions**

* Analyze the linked file(s) to determine if they pose any security risk.
* Check the sender's communication history within the organization.
* Analyze the file reputation using sandbox or threat intelligence sources.
* Verify whether similar links were sent to other users.

</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/email-with-file-sharing-link-containing-auto-download-parameter.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.
