> 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/gcp-logging-sink-modification.md).
# GCP logging sink modification
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 5 Days |
| Required Data | Gcp Audit Log |
| Detection Modules | Cloud |
| Detector Tags | Cloud Log Tampering Analytics |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002) |
| Severity | Informational |
### Description
A GCP logging sink entity was modified. Logs that match the logging sink rule will not arrive at their destination. An attacker might use this technique to evade detection.
### Attacker's Goals
Evade detection by limiting collected data.
### Investigative actions
* Identify the relevant logs impacted by the modification.
* Review The cloud identity activity before and after the logging sink modification.
### Variations
GCP logging sink modification
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Impairment (TA0112), Discovery (TA0007) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002), Cloud Service Discovery (T1526) |
| Severity | Medium |
**Description**
A GCP logging sink entity was modified. Logs that match the logging sink rule will not arrive at their destination. An attacker might use this technique to evade detection.
**Attacker's Goals**
Evade detection by limiting collected data.
**Investigative actions**
* Identify the relevant logs impacted by the modification.
* Review The cloud identity activity before and after the logging sink modification.
GCP logging sink modification
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Disable or Modify Tools: Disable or Modify Cloud Log (T1685.002) |
| Severity | Low |
**Description**
A GCP logging sink entity was modified. Logs that match the logging sink rule will not arrive at their destination. An attacker might use this technique to evade detection.
**Attacker's Goals**
Evade detection by limiting collected data.
**Investigative actions**
* Identify the relevant logs impacted by the modification.
* Review The cloud identity activity before and after the logging sink modification.
---
# 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/gcp-logging-sink-modification.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.