> 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 |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Impair Defenses (T1562), Impair Defenses: Disable or Modify Cloud Logs (T1562.008) |
| 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 Evasion (TA0005), Discovery (TA0007) |
| ATT\&CK Technique | Impair Defenses (T1562), Impair Defenses: Disable or Modify Cloud Logs (T1562.008), 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 Evasion (TA0005) |
| ATT\&CK Technique | Impair Defenses (T1562), Impair Defenses: Disable or Modify Cloud Logs (T1562.008) |
| 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.