> 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-volume-of-files-potentially-containing-credentials-accessed-in-google-drive.md).

# Large volume of files potentially containing credentials accessed in Google Drive

### Synopsis

| Field                | Value                                                          |
| -------------------- | -------------------------------------------------------------- |
| Activation Period    | 14 Days                                                        |
| Training Period      | 30 Days                                                        |
| Test Period          | 1 Hour                                                         |
| Deduplication Period | 1 Day                                                          |
| Required Data        | Google Workspace Audit Logs                                    |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection                  |
| Detector Tags        | Google Workspace, Data Detection & Response                    |
| ATT\&CK Tactic       | Collection (TA0009), Credential Access (TA0006)                |
| ATT\&CK Technique    | Data from Cloud Storage (T1530), Unsecured Credentials (T1552) |
| Severity             | Informational                                                  |

### Description

A user accessed a large volume of files potentially containing credentials in Google Drive.

### Attacker's Goals

An attacker may attempt to gain unauthorized access by leveraging valid credentials found in Google Drive.

### Investigative actions

* Check for signs of account compromise, such as abnormal login activity or unusual behavior.
* Verify if the user account that accessed the files is authorized to access them.
* Review the files accessed and whether it was part of a breach or a legitimate activity.
* Monitor the account for any further suspicious actions.

### Variations

<details>

<summary>Possible credential files harvesting in Google Drive</summary>

**Synopsis**

| Field             | Value                                                          |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic    | Collection (TA0009), Credential Access (TA0006)                |
| ATT\&CK Technique | Data from Cloud Storage (T1530), Unsecured Credentials (T1552) |
| Severity          | Low                                                            |

**Description**

A user accessed a large volume of files potentially containing credentials in Google Drive.

**Attacker's Goals**

An attacker may attempt to gain unauthorized access by leveraging valid credentials found in Google Drive.

**Investigative actions**

* Check for signs of account compromise, such as abnormal login activity or unusual behavior.
* Verify if the user account that accessed the files is authorized to access them.
* Review the files accessed and whether it was part of a breach or a legitimate activity.
* Monitor the account for any further suspicious actions.

</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/large-volume-of-files-potentially-containing-credentials-accessed-in-google-drive.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.