> 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/large-upload-generic.md).
# Large Upload (Generic)
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Day |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Palo Alto Networks Firewall traffic Logs OR XDR Agent
|
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Low |
### Description
The endpoint transferred large amounts of data to an external site using a different protocol from HTTP/s, FTP, or SMTP. (A specific detector is used for each of those protocols.) Cortex XDR Analytics assumes that data transfers out of your network are ordinarily performed using one of those three services, so it expects that data transfers over all other ports to be low. For the same reason, Cortex XDR Analytics also assumes endpoint traffic towards a specific destination should be about the same over long periods of time. An attacker may be exfiltrating data directly to the internet.
### Attacker's Goals
Transfer data he has stolen from your network to a location that is convenient and useful to him.
### Investigative actions
* Check if the traffic is related to SSH activity, it can trigger this alert. It is possible that someone on your network is legitimately engaged in SSH activity.
* Check if the traffic is to/from a misconfigured network.
* Check if the traffic is to a new external service or server that has recently been adopted for use by an organization in your enterprise.
* Identify the process/user performing the data transfer to determine if the transfer is sanctioned.
### Variations
Large Upload (Generic)
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Informational |
**Description**
The endpoint transferred large amounts of data to an external site using a different protocol from HTTP/s, FTP, or SMTP. (A specific detector is used for each of those protocols.) Cortex XDR Analytics assumes that data transfers out of your network are ordinarily performed using one of those three services, so it expects that data transfers over all other ports to be low. For the same reason, Cortex XDR Analytics also assumes endpoint traffic towards a specific destination should be about the same over long periods of time. An attacker may be exfiltrating data directly to the internet.
**Attacker's Goals**
Transfer data he has stolen from your network to a location that is convenient and useful to him.
**Investigative actions**
* Check if the traffic is related to SSH activity, it can trigger this alert. It is possible that someone on your network is legitimately engaged in SSH activity.
* Check if the traffic is to/from a misconfigured network.
* Check if the traffic is to a new external service or server that has recently been adopted for use by an organization in your enterprise.
* Identify the process/user performing the data transfer to determine if the transfer is sanctioned.
Large Upload (Generic) Lower than 100 MB
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Informational |
**Description**
The endpoint transferred large amounts of data to an external site using a different protocol from HTTP/s, FTP, or SMTP. (A specific detector is used for each of those protocols.) Cortex XDR Analytics assumes that data transfers out of your network are ordinarily performed using one of those three services, so it expects that data transfers over all other ports to be low. For the same reason, Cortex XDR Analytics also assumes endpoint traffic towards a specific destination should be about the same over long periods of time. An attacker may be exfiltrating data directly to the internet.
**Attacker's Goals**
Transfer data he has stolen from your network to a location that is convenient and useful to him.
**Investigative actions**
* Check if the traffic is related to SSH activity, it can trigger this alert. It is possible that someone on your network is legitimately engaged in SSH activity.
* Check if the traffic is to/from a misconfigured network.
* Check if the traffic is to a new external service or server that has recently been adopted for use by an organization in your enterprise.
* Identify the process/user performing the data transfer to determine if the transfer is sanctioned.
Large Upload (Generic) to a Frequently Used Upload Target
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Informational |
**Description**
The endpoint transferred large amounts of data to an external site using a different protocol from HTTP/s, FTP, or SMTP. (A specific detector is used for each of those protocols.) Cortex XDR Analytics assumes that data transfers out of your network are ordinarily performed using one of those three services, so it expects that data transfers over all other ports to be low. For the same reason, Cortex XDR Analytics also assumes endpoint traffic towards a specific destination should be about the same over long periods of time. An attacker may be exfiltrating data directly to the internet.
**Attacker's Goals**
Transfer data he has stolen from your network to a location that is convenient and useful to him.
**Investigative actions**
* Check if the traffic is related to SSH activity, it can trigger this alert. It is possible that someone on your network is legitimately engaged in SSH activity.
* Check if the traffic is to/from a misconfigured network.
* Check if the traffic is to a new external service or server that has recently been adopted for use by an organization in your enterprise.
* Identify the process/user performing the data transfer to determine if the transfer is sanctioned.
---
# 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/large-upload-generic.md?ask=&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.