> 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-https.md).
# Large Upload (HTTPS)
### 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 OR Third-Party Firewalls
|
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Low |
### Description
The endpoint transferred an excessive amount of data to an external site over HTTPS. The destination is not a popular upload site for endpoints on your network, and the endpoint performing the upload has not previously downloaded a large amount of data from the site. The upload is considered excessive based on comparison to baseline measurements of HTTPS data transfers on your network. An attacker may be exfiltrating data directly to the internet.
### Attacker's Goals
Transfer data she has stolen from your network to a location that is convenient and useful to her.
### Investigative actions
* Check if this alert has been falsely triggered by DNS load balancers. If an endpoint routinely uploads data to a site that uses load balancers, the transfer might ordinarily be split into multiple sessions and across multiple subdomains, which can cause the baseline measurement to be incorrect. In that situation, a routine upload that randomly places the bulk of the data in a single session to a single subdomain can look excessive to the Cortex XDR Analytics detector.
* Check if the device performing the data transfer is a mobile phone performing a backup. Cortex XDR Analytics will not always measure the baseline properly for mobile devices, especially if the backups are performed infrequently and contain a great deal of data. If the data transfer is a mobile device running a backup, check to ensure that only appropriate data is included in the backup.
* Identify the process/user performing the data transfer to determine if the transfer is sanctioned.
### Variations
Large Upload (HTTPS)
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Informational |
**Description**
The endpoint transferred an excessive amount of data to an external site over HTTPS. The destination is not a popular upload site for endpoints on your network, and the endpoint performing the upload has not previously downloaded a large amount of data from the site. The upload is considered excessive based on comparison to baseline measurements of HTTPS data transfers on your network. An attacker may be exfiltrating data directly to the internet.
**Attacker's Goals**
Transfer data she has stolen from your network to a location that is convenient and useful to her.
**Investigative actions**
* Check if this alert has been falsely triggered by DNS load balancers. If an endpoint routinely uploads data to a site that uses load balancers, the transfer might ordinarily be split into multiple sessions and across multiple subdomains, which can cause the baseline measurement to be incorrect. In that situation, a routine upload that randomly places the bulk of the data in a single session to a single subdomain can look excessive to the Cortex XDR Analytics detector.
* Check if the device performing the data transfer is a mobile phone performing a backup. Cortex XDR Analytics will not always measure the baseline properly for mobile devices, especially if the backups are performed infrequently and contain a great deal of data. If the data transfer is a mobile device running a backup, check to ensure that only appropriate data is included in the backup.
* Identify the process/user performing the data transfer to determine if the transfer is sanctioned.
Large Upload (HTTPS) to non-standard port
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Low |
**Description**
The endpoint transferred an excessive amount of data to an external site over HTTPS. The destination is not a popular upload site for endpoints on your network, and the endpoint performing the upload has not previously downloaded a large amount of data from the site. The upload is considered excessive based on comparison to baseline measurements of HTTPS data transfers on your network. An attacker may be exfiltrating data directly to the internet.
**Attacker's Goals**
Transfer data she has stolen from your network to a location that is convenient and useful to her.
**Investigative actions**
* Check if this alert has been falsely triggered by DNS load balancers. If an endpoint routinely uploads data to a site that uses load balancers, the transfer might ordinarily be split into multiple sessions and across multiple subdomains, which can cause the baseline measurement to be incorrect. In that situation, a routine upload that randomly places the bulk of the data in a single session to a single subdomain can look excessive to the Cortex XDR Analytics detector.
* Check if the device performing the data transfer is a mobile phone performing a backup. Cortex XDR Analytics will not always measure the baseline properly for mobile devices, especially if the backups are performed infrequently and contain a great deal of data. If the data transfer is a mobile device running a backup, check to ensure that only appropriate data is included in the backup.
* 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 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/large-upload-https.md?ask=&goal=
```
`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.