Elastic Security Detection Rules

GCP Logging Sink Modification

Last updated 6 months ago on 2025-01-15
Created 5 years ago on 2020-09-22

About

Identifies a modification to a Logging sink in Google Cloud Platform (GCP). Logging compares the log entry to the sinks in that resource. Each sink whose filter matches the log entry writes a copy of the log entry to the sink's export destination. An adversary may update a Logging sink to exfiltrate logs to a different export destination.
Tags
Domain: CloudData Source: GCPData Source: Google Cloud PlatformUse Case: Log AuditingTactic: ExfiltrationLanguage: kuery
Severity
low
Risk Score
21
MITRE ATT&CK™

Exfiltration (TA0010)(opens in a new tab or window)

↳ Transfer Data to Cloud Account (T1537)(opens in a new tab or window)

False Positive Examples
Logging sink modifications may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Sink modifications from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
License
Elastic License v2(opens in a new tab or window)

Definition

Rule Type
Query (Kibana Query Language)
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
filebeat-*logs-gcp*
Related Integrations

gcp(opens in a new tab or window)

Query
event.dataset:gcp.audit and event.action:google.logging.v*.ConfigServiceV*.UpdateSink and event.outcome:success

Install detection rules in Elastic Security

Detect GCP Logging Sink Modification in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).