GCP Logs

Connecting GCP logs to your Panther Console

Overview

Panther supports ingesting Google Cloud Platform (GCP) logs via common Data Transport options.

To connect GCP logs with Panther, it's recommended to use the Pub/Sub Data Transport source with a log sink, as it results in the lowest latency—roughly five minutes.

Alternatively, using the Google Cloud Storage (GCS) Data Transport source with a log sink will result in logs being delivered to Panther only on an hourly basis.

How to onboard GCP logs to Panther

Prerequisite

  • Set a default Data Access audit logging configuration for your Google Cloud services:

    1. In your GCP console, navigate to the IAM & Admin service. In the navigation bar, click Audit Logs.

    2. Click Set Default Configuration. The GCP IAM & Access console is shown. An arrow is drawn from the "Audit Log" option in the navigation bar to a "Set default configuration" button.

    3. In the Log Types tab, check the boxes for the following types: Admin Read, Data Read, and Data Write. A page title reads "Set default Data Access audit log configuration." Under a "Log types" header are three checked boxes—their labels read "Admin Read," "Data Read," and "Data Write"

    4. Click Save.

These instructions for setting a default Data Access audit log configuration for your Google Cloud services are also found in the GCP documentation: Set the default configuration.

Step 1: Create a Google Cloud source in Panther

  1. In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.

  2. Click Create New.

  3. Search for "GCP" then click the Google Cloud tile.

  4. In the slide-out panel, in the Transport Mechanism dropdown in the upper right corner, select Google Cloud Pub/Sub.

    • It is possible to use any of the Data Transport options, but is recommended to use Pub/Sub in conjunction with a log sink, which you will configure in the next step.

  5. Follow the Panther documentation for configuring your selected Data Transport.

Step 2: Configure GCP to push logs to the Data Transport source

Video walkthrough: Setup using GCS

Panther-managed detections

See Panther-managed rules for Google Cloud Platform in the panther-analysis GitHub repository.

Supported log types

GCP.AccessTransparency

Access Transparency logs record activities taken by Google personnel when accessing customer content. These logs provide visibility into Google Cloud support operations and help meet compliance requirements by recording things like justification for access and what actions were performed.

For more information, see the GCP Documentation on Access Transparency logs.

GCP.AuditLog

The GCP.AuditLog schema supports ingesting all four types of Google Cloud audit logs:

For more information, see the GCP Documentation on Cloud Audit Logs.

GCP.DNS

Google Cloud DNS query logs contain detailed information about DNS queries that your Cloud DNS zones receive. These logs help you monitor DNS activity and troubleshoot DNS-related issues by capturing things like query names, source and destination IP addresses, and protocol information.

For more information, see the GCP Documentation on DNS query logging.

GCP.Firewall

Google Cloud VPC Firewall Rules Logging allows you to audit, verify, and analyze the effects of your firewall rules. These logs capture information about network connections that match firewall rules.

For more information, see the GCP Documentation on VPC Firewall Rules Logging.

GCP.HTTPLoadBalancer

External HTTP(S) Load Balancing distributes HTTP and HTTPS traffic to backends hosted on a variety of Google Cloud platforms (such as Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and so on), as well as external backends connected over the internet or via hybrid connectivity. HTTP(S) load balancing logs provide information for monitoring and debugging web traffic.

For more information, see the HTTPLoadBalancer documentation.

Last updated

Was this helpful?