GCP Logs

Connecting GCP logs to your Panther Console

Overview

Panther supports ingesting Google Cloud Platform (GCP) logs via common Data Transport options: Amazon Web Services (AWS) S3, AWS SQS, and Google Cloud Storage (GCS).

How to onboard GCP logs to Panther

To connect these logs into Panther:

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

  2. Click Create New.

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

  4. Select the data transport method you wish to use for this integration, then follow Panther's instructions for configuring the method:

  5. Configure GCP to push logs to the Data Transport source.

    • See GCP's documentation for instructions on pushing logs to your selected Data Transport source.

GCP Logs Video Walkthrough

The video below walks through a configuration using GCS as the data transport method.

Walkthrough video showing how to onboard GCP logs to Panther

Panther-Built Detections

See Panther's built in rules for GCP in panther-analysis in Github.

Supported log types

Required fields in the table are in bold.

GCP.AuditLog

Cloud Audit Logs maintains three audit logs for each Google Cloud project, folder, and organization: Admin Activity, Data Access, and System Event. Google Cloud services writes audit log entries to these logs to help answer the questions of "who did what, where, and when?" within your Google Cloud resources.

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

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?