> 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/data-sharing-between-gcp-and-google-workspace-was-disabled.md).
# Data Sharing between GCP and Google Workspace was disabled
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 2 Days |
| Required Data | Google Workspace Audit Logs |
| Detection Modules | Identity Threat Module, SaaS Threat Detection, Email |
| Detector Tags | Google Workspace |
| ATT\&CK Tactic | Stealth (TA0005), Impact (TA0040), Defense Impairment (TA0112) |
| ATT\&CK Technique | Indicator Removal (T1070), Disable or Modify Tools (T1685), Data Manipulation (T1565), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002) |
| Severity | Informational |
### Description
An identity has modified data sharing settings between GCP and Google Workspace.
### Attacker's Goals
Adversaries may stop audit log events from being sent to remove evidence of their presence or hinder defenses.
### Investigative actions
* Check if the identity intended to perform this action or look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Check whether Google Workspace audit log events were configured to be sent to Google Cloud.
* Follow further actions done by the account.
### Variations
Data Sharing between GCP and Google Workspace was disabled by a suspicious identity
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005), Impact (TA0040), Defense Impairment (TA0112) |
| ATT\&CK Technique | Indicator Removal (T1070), Disable or Modify Tools (T1685), Data Manipulation (T1565), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002) |
| Severity | Low |
**Description**
An identity has modified data sharing settings between GCP and Google Workspace.
**Attacker's Goals**
Adversaries may stop audit log events from being sent to remove evidence of their presence or hinder defenses.
**Investigative actions**
* Check if the identity intended to perform this action or look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Check whether Google Workspace audit log events were configured to be sent to Google Cloud.
* Follow further actions done by the account.
Data Sharing between GCP and Google Workspace was disabled by a non Google Workspace administrative user
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005), Impact (TA0040), Defense Impairment (TA0112) |
| ATT\&CK Technique | Indicator Removal (T1070), Disable or Modify Tools (T1685), Data Manipulation (T1565), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002) |
| Severity | Low |
**Description**
An identity has modified data sharing settings between GCP and Google Workspace.
**Attacker's Goals**
Adversaries may stop audit log events from being sent to remove evidence of their presence or hinder defenses.
**Investigative actions**
* Check if the identity intended to perform this action or look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Check whether Google Workspace audit log events were configured to be sent to Google Cloud.
* Follow further actions done by the account.
Data Sharing between GCP and Google Workspace was disabled from an unusual ASN
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005), Impact (TA0040), Defense Impairment (TA0112) |
| ATT\&CK Technique | Indicator Removal (T1070), Disable or Modify Tools (T1685), Data Manipulation (T1565), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002) |
| Severity | Low |
**Description**
An identity has modified data sharing settings between GCP and Google Workspace.
**Attacker's Goals**
Adversaries may stop audit log events from being sent to remove evidence of their presence or hinder defenses.
**Investigative actions**
* Check if the identity intended to perform this action or look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Check whether Google Workspace audit log events were configured to be sent to Google Cloud.
* Follow further actions done by the account.
---
# 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/data-sharing-between-gcp-and-google-workspace-was-disabled.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.