Collect Google Cloud Firewall logs

This document describes how you can collect Google Cloud Firewall logs by enabling Google Cloud telemetry ingestion to Google Security Operations and how log fields of Google Cloud Firewall logs map to Google Security Operations Unified Data Model (UDM) fields. This document also lists the supported Google Cloud Firewall version.

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

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

The deployment contains the following components:

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

• Google Cloud Firewall logs: The Google Cloud Firewall logs that are enabled for ingestion to Google Security Operations.

• Google Security Operations: Google Security Operations retains and analyzes the logs from Google Cloud Firewall.

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_FIREWALL ingestion label.

Before you begin

• Ensure that you are using Google Cloud Firewall version 1.

• Ensure that all systems in the deployment architecture are configured in the UTC time zone.

Configure Google Cloud to ingest Google Cloud Firewall logs

To ingest Google Cloud Firewall logs to Google Security Operations, follow the steps on the Ingest Google Cloud logs to Google Security Operations page.

If you encounter issues when you ingest Google Cloud Firewall logs, contact Google Security Operations support .

Supported Google Cloud Firewall log formats

The Google Cloud Firewall parser supports logs in JSON format.

Supported Google Cloud Firewall sample logs

• JSON:

   {
    "insertId": "1o2en3g1af0lkj",
    "jsonPayload": {
      "connection": {
        "dest_ip": "198.51.100.0",
        "dest_port": 22,
        "protocol": 6,
        "src_ip": "198.51.100.1",
        "src_port": 43144
      },
      "disposition": "ALLOWED",
      "instance": {
        "project_id": "logging-271618",
        "region": "us-central1",
        "vm_name": "elastic-siem-01",
        "zone": "us-central1-a"
      },
      "remote_location": {
        "city": "Adana",
        "continent": "Asia",
        "country": "tur",
        "region": "Adana"
      },
      "rule_details": {
        "action": "ALLOW",
        "direction": "INGRESS",
        "ip_port_info": [
          {
            "ip_protocol": "TCP",
            "port_range": [
              "22"
            ]
          }
        ],
        "priority": 65534,
        "reference": "network:default/firewall:default-allow-ssh",
        "source_range": [
          "0.0.0.0/0"
        ]
      },
      "vpc": {
        "project_id": "logging-271618",
        "subnetwork_name": "default",
        "vpc_name": "default"
      }
    },
    "logName": "projects/logging-271618/logs/compute.googleapis.com%2Ffirewall",
    "receiveTimestamp": "2020-04-14T09:00:11.292726397Z",
    "resource": {
      "labels": {
        "location": "us-central1-a",
        "project_id": "logging-271618",
        "subnetwork_id": "4738025575977389850",
        "subnetwork_name": "default"
      },
      "type": "gce_subnetwork"
    },
    "timestamp": "2020-04-14T09:00:05.889200827Z"
  } 
  

Field mapping reference

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

What's next

• Data ingestion to Google Security Operations

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