Collect Google Cloud Abuse Events logs

This document describes how you can collect Google Cloud Abuse Events logs by enabling Google Cloud telemetry ingestion to Google SecOps and how log fields of Google Cloud Abuse Events logs map to Google SecOps Unified Data Model (UDM) fields.

For more information, see Data ingestion to Google Security Operations .

The deployment contains the following components:

• Google Cloud: The Google Cloud services and products from which you collect logs.

• Google Cloud Abuse Events logs: The Google Cloud Abuse Events logs that are enabled for ingestion to Google SecOps.

• Google SecOps: Google SecOps retains and analyzes the logs from Google Cloud Abuse Events.

An ingestion label identifies the parser which normalizes raw log data to structured UDM format. The information in this document applies to the parser with the GCP_ABUSE_EVENTS ingestion label.

Before you begin

Make sure all systems in the deployment architecture are configured in the UTC time zone.

Configure Google Cloud to ingest Google Cloud Abuse Events logs

To ingest Google Cloud Abuse Events logs to Google SecOps, follow the steps in Ingest Google Cloud logs to Google SecOps .

A typical deployment consists of Google Cloud Abuse Events logs enabled for ingestion to Google SecOps. Each customer deployment might differ from this representation and might be more complex.

If you encounter issues when you ingest Google Cloud Abuse Events logs, contact Google SecOps support .

Supported Google Cloud Abuse Events log format and sample

The Google Cloud Abuse Events parser supports logs in JSON format. The following is an example:

 {
        "insertId": "dummy-insert-id",
        "jsonPayload": {
            "action": "NOTIFY",
            "@type": "type.googleapis.com/google.cloud.abuseevent.logging.v1.AbuseEvent",
            "cryptoMiningEvent": {
                "detectedMiningEndTime": "2048-03-18T07: 10: 00Z",
                "detectedMiningStartTime": "2016-07-10T05: 24: 00Z",
                "vmIp": [
                    "dummy.ip.address.1",
                    "dummy.ip.address.2",
                    "dummy.ip.address.3"
                ],
                "vmResource": [
                    "projects/dummy-project-id/zones/dummy-zone/instances/dummy-instance-id"
                ]
            },
            "detectionType": "CRYPTO_MINING",
            "reason": "The monitored resource is mining cryptocurrencies",
            "remediationLink": "https://dummy-remediation-link"
        },
        "resource": {
            "type": "abuseevent.googleapis.com/Location",
            "labels": {
                "location": "global",
                "resource_container": "projects/dummy-resource-container-id"
            }
        },
        "timestamp": "2025-07-10T17:31:53.966189618Z",
        "severity": "NOTICE",
        "labels": {
            "abuseevent.googleapis.com/vm_resource": "projects/dummy-project-id/zones/dummy-zone/instances/dummy-instance-id"
        },
        "logName": "projects/dummy-project-id/logs/abuseevent.googleapis.com%2Fabuse_events",
        "receiveTimestamp": "2025-07-10T17:31:54.754890208Z"
    } 

Field mapping reference

Field mapping reference: GCP_ABUSE_EVENTS

The following table lists the log fields and their corresponding UDM fields.

What's next

• Data ingestion to Google SecOps

Need more help? Get answers from Community members and Google SecOps professionals.