Cloud Storage (GCS) Source
Onboarding GCS as a Data Transport log source in the Panther Console
Last updated
Was this helpful?
Onboarding GCS as a Data Transport log source in the Panther Console
Last updated
Was this helpful?
Panther supports configuring Google Cloud Storage (GCS) as a Data Transport to pull log data directly from GCS buckets, write rules, and run queries on this processed data. Panther uses to be notified of new data in your bucket that is ready to be consumed.
Data can be sent compressed (or uncompressed). Learn more about compression specifications in .
In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.
In the upper-right corner, click Create New.
Click the Custom Log Formats tile.
On the Google Cloud Storage tile, click Start.
On the Basic Info page, fill in the fields:
Name: Enter a descriptive name for the GCS log source.
Prefixes & Schemas: Define combinations of prefixes, schemas, and exclusion filters, according the structure of your data storage in GCS.
To attach one or more schemas to all data in the bucket, leave the GCS Prefix field blank. This will create a wildcard (*) prefix.
Click Setup.
On the Log Format page, select the of the incoming logs:
Auto
Lines
JSON
JSON Array
Click Continue.
On the "Infrastructure & Credentials" page, click Terraform Template to download the Terraform template.
Fill out the fields in the panther.tfvars
file with your configuration.
Initialize a working directory containing Terraform configuration files by running the Terraform Command schema provided.
Copy the corresponding Terraform of gcloud command schema provided and run it in your CLI.
Generate a JSON key file by replacing the value for your service account email in the gcloud command code listed.
You can find the key file in the output of the Terraform run.
Under Provide pulling configuration & JSON Keyfile, upload your JSON key file.
Click Setup. You will be directed to a success screen:
If you have not done so already, click Attach or Infer Schemas to attach one or more schemas to the source.
The Trigger an alert when no events are processed setting defaults to YES. We recommend leaving this enabled, as you will be alerted if data stops flowing from the log source after a certain period of time. The timeframe is configurable, with a default of 24 hours.
You can set up required GCP infrastructure by , or .
You can also find the Terraform template at .
If you have not created a bucket yet, please see .
for the notifications.
for new files to the topic you created.
to be used with the topic you created. Note: This subscription should not be used by any other service or source.
.
. To create the account using the gcloud
CLI tool, use the following command format:
Note: You can set conditions or IAM policies on permissions for specific resources. This can be done either in the IAM page of the service account (as seen in the example screenshot below) or in the specific resource's page.
for the service account, which will be used in Panther to authenticate to the GCP infrastructure.
Enter your GCS Bucket Name and Pub/Sub Subscription ID, found in the Subscriptions section of your Google Cloud account.
You can optionally enable one or more .
After your log source is configured, you can search ingested data using or .