> 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/user-accessed-saas-resource-via-anonymous-link.md).

# User accessed SaaS resource via anonymous link

### Synopsis

| Field                | Value                                                                                                 |
| -------------------- | ----------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                               |
| Training Period      | 30 Days                                                                                               |
| Test Period          | N/A (single event)                                                                                    |
| Deduplication Period | 1 Day                                                                                                 |
| Required Data        | <p>Requires one of the following data sources:<br>Google Workspace Audit Logs OR Office 365 Audit</p> |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection                                                         |
| ATT\&CK Tactic       | Collection (TA0009)                                                                                   |
| ATT\&CK Technique    | Data from Cloud Storage (T1530)                                                                       |
| Severity             | Informational                                                                                         |

### Description

A user accessed a SaaS resource via an anonymous link.

### Attacker's Goals

An attacker is attempting to collect sensitive data.

### Investigative actions

* Check the IP address from which the access originated.
* Examine the file that was accessed for any sensitive indicators.
* Follow further actions taken, such as downloading files.

### Variations

<details>

<summary>External user accessed a sensitive SaaS file via anonymous link</summary>

**Synopsis**

| Field             | Value                           |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic    | Collection (TA0009)             |
| ATT\&CK Technique | Data from Cloud Storage (T1530) |
| Severity          | Low                             |

**Description**

An external user accessed a sensitive SaaS file via an anonymous link.

**Attacker's Goals**

An attacker is attempting to collect sensitive data.

**Investigative actions**

* Check the IP address from which the access originated.
* Examine the file that was accessed for any sensitive indicators.
* Follow further actions taken, such as downloading files.

</details>

<details>

<summary>User accessed a public Google Drive document</summary>

**Synopsis**

| Field             | Value                           |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic    | Collection (TA0009)             |
| ATT\&CK Technique | Data from Cloud Storage (T1530) |
| Severity          | Informational                   |

**Description**

A user accessed a Google Drive document that is public on the web.

**Attacker's Goals**

An attacker is attempting to collect sensitive data.

**Investigative actions**

* Check the IP address from which the access originated.
* Examine the file that was accessed for any sensitive indicators.
* Follow further actions taken, such as downloading files.

</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/user-accessed-saas-resource-via-anonymous-link.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.
