> 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/massive-upload-to-saas-service.md).
# Massive upload to SaaS service
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 3 Hours |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Box Audit Log OR DropBox OR Google Workspace Audit Logs OR Office 365 Audit
|
| Detection Modules | Identity Threat Module, SaaS Threat Detection |
| Detector Tags | Data Detection & Response |
| ATT\&CK Tactic | Exfiltration (TA0010), Collection (TA0009) |
| ATT\&CK Technique | Exfiltration Over Web Service (T1567), Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002), Data Staged: Remote Data Staging (T1074.002) |
| Severity | Informational |
### Description
A user uploaded a large amount of data to an organizational cloud storage. This behavior may indicate that the data is being exfiltrated or staged.
### Attacker's Goals
An attacker may upload files to a SaaS service to stage and exfiltrate data from the organization.
### Investigative actions
* Check for signs of account compromise, such as abnormal login activity or unusual behavior.
* Review the files that were uploaded to determine if they contain sensitive data.
* Verify if the user account that uploaded the files is authorized to access them.
* Analyze the file types that were uploaded.
* Monitor the account for any further suspicious actions.
### Variations
Massive upload to SaaS service by suspicious user
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010), Collection (TA0009) |
| ATT\&CK Technique | Exfiltration Over Web Service (T1567), Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002), Data Staged: Remote Data Staging (T1074.002) |
| Severity | Low |
**Description**
A suspicious user uploaded a large amount of data to an organizational cloud storage. This behavior may indicate that the data is being exfiltrated or staged.
**Attacker's Goals**
An attacker may upload files to a SaaS service to stage and exfiltrate data from the organization.
**Investigative actions**
* Check for signs of account compromise, such as abnormal login activity or unusual behavior.
* Review the files that were uploaded to determine if they contain sensitive data.
* Verify if the user account that uploaded the files is authorized to access them.
* Analyze the file types that were uploaded.
* Monitor the account for any further suspicious actions.
---
# 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/massive-upload-to-saas-service.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.