Collect Google Cloud DNS logs

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

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

A typical deployment consists of Cloud DNS 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.

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

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

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

Before you begin

• Ensure that you have set up Google Cloud .

• Ensure that the Cloud DNS service is properly deployed and configured. For detailed setup instructions, refer to the Cloud DNS documentation .

• Ensure that you are using Cloud DNS version 1.

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

Configure Google Cloud to ingest Cloud DNS logs

To ingest Cloud DNS 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 Cloud DNS logs, contact Google Security Operations support .

Supported Cloud DNS log formats

The Google Cloud DNS parser supports logs in both JSON format.

Supported Cloud DNS Sample Logs

• JSON

   {
      "insertId": "of4onjd9km0",
      "jsonPayload": {
        "authAnswer": true,
        "serverLatency": 0.0,
        "queryName": "dNs.DataSOfT.cLoUDnS.pH.",
        "vmProjectId": "abc12-123456",
        "vmZoneName": "us-central1-c",
        "vmInstanceName": "329088982544.vm-707dd8df-9e19-4537-410d-e2b5597f49b8",
        "authAnswer": true,
        "responseCode": "BADCOOKIE",
        "destinationIP": "198.51.100.5",
        "protocol": "UDP",
        "structuredRdata": [
          {
            "class": "IN",
            "ttl": "300",
            "domainName": "dummy.domain.name.com.",
            "rvalue": "198.51.100.4",
            "type": "A"
          }
        ],
        "queryType": "AAAA"
      },
      "resource": {
        "type": "dns_query",
        "labels": {
          "target_type": "public-zone",
          "location": "global",
          "source_type": "internet",
          "project_id": "chronical-34531",
          "target_name": "clouddns-zone"
        }
      },
      "timestamp": "2023-08-01T10:24:59.349280070Z",
      "severity": "INFO",
      "logName": "projects/chronical-34531/logs/dns.googleapis.com%2Fdns_queries",
      "receiveTimestamp": "2023-08-01T10:25:00.651062191Z"
    } 
  

Field mapping reference

This section explains how the Google Security Operations parser maps Google Cloud DNS fields to Google Security Operations Unified Data Model (UDM) fields.

The following labels fields for UDM nouns are deprecated: about.labels , intermediary.labels , observer.labels , principal.labels , src.labels , security_result.about.labels , and target.labels . For existing parsers, in addition to these UDM fields, the logs fields are also mapped to key/value additional.fields UDM fields. For new parsers, the key/value settings in additional.fields UDM fields are used instead of the deprecated labels UDM fields. We recommend that you update the existing rules to use the key/value settings in the additional.fields UDM fields instead of the deprecated labels UDM fields.

What's next

• Data ingestion to Google Security Operations

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