> 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/a-third-party-application-s-access-to-the-google-workspace-domain-s-resources-was-revoked.md).

# A third-party application's access to the Google Workspace domain's resources was revoked

### Synopsis

| Field                | Value                                         |
| -------------------- | --------------------------------------------- |
| Activation Period    | 14 Days                                       |
| Training Period      | 30 Days                                       |
| Test Period          | N/A (single event)                            |
| Deduplication Period | 5 Days                                        |
| Required Data        | Google Workspace Audit Logs                   |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection |
| Detector Tags        | Google Workspace                              |
| ATT\&CK Tactic       | Impact (TA0040)                               |
| ATT\&CK Technique    | Account Access Removal (T1531)                |
| Severity             | Informational                                 |

### Description

An identity removed a third-party application's access to Google Workspace domain's resources.

### Attacker's Goals

An attacker might remove an application to impair the environment.

### Investigative actions

* Check the Google Workspace Application settings to determine which actions were triggered.
* Investigate the source of the request and the user associated with it.
* Review the access control policies to determine if the removal of the application is allowed.


---

# 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/a-third-party-application-s-access-to-the-google-workspace-domain-s-resources-was-revoked.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.