GCP logs to Chronicle

This article covers how to ingest GCP logs to Chronicle. 

This SOP shows how to enable and disable the ingestion of your GCP telemetry into Chronicle. Chronicle enables you to store, search and examine the aggregated security information for your enterprise going back for months or longer.

Ingesting GCP Logs to Chronicle

Before you can ingest your GCP telemetry into your Chronicle account, you must complete the following steps:

• Contact your Chronicle representative and obtain the one-time access code you need to ingest your GCP telemetry.
• Grant the IAM roles required for you to access the Chronicle section:
• Chronicle Service Admin IAM role for performing all activities.
• Chronicle Service Viewer IAM role to only view the state of ingestion.

Granting IAM Roles

You can grant the required IAM roles using either the Google Cloud console or using the gcloud CLI.

To grant IAM roles using Google Cloud console, complete the following steps:

• Log on to the GCP Organization you want to connect to and navigate to the IAM screen using Products > IAM & Admin > IAM.
• From the IAM screen, select the user and click Edit Member.
  Note: If you are not in the Organization view of IAM, the Edit Member button is disabled and you need to navigate to the organization's IAM screen.

• In the Edit Permissions screen, click Add Another Role and search for Chronicle to find the IAM roles.
• Once you have assigned the roles, click Save.

To grant IAM roles using the Google Cloud CLI, complete the following steps:

• Ensure you are logged into the correct organization. Verify this by running the gcloud init command.
• To grant the admin IAM role from the gCloud tool, run the following command:
  • $ gcloud organizations add-iam-policy-binding <ORGANIZATION_ID> --member user:<USER_EMAIL> --role roles/chroniclesm.admin
• To grant the viewer IAM role from the gCloud tool, run the following command:
  • $ gcloud organizations add-iam-policy-binding <ORGANIZATION_ID> --member user:<USER_EMAIL> --role roles/chroniclesm.viewer

Enabling GCP Telemetry Ingestion

To enable GCP telemetry ingestion into your Chronicle account, complete the following steps:

• Navigate to the Chronicle page for the Google Cloud console. 
  Go to the Chronicle page
• Enter your one-time access code in the 1-time Chronicle access code field.
• Check the box labeled I consent to the terms and conditions of Chronicle's usage of my Google Cloud data.
• Click Connect Chronicle.
• Send an email requesting Chronicle access key for google support.

   

• Your GCP telemetry is now going to be sent to Chronicle. You can use Chronicle's analysis features to investigate any security related issues. The sections that follow describe ways to adjust the types of GCP telemetry that are going to be sent to Chronicle.

Export Filter Settings

By default, your Cloud Audit logs (admin activity and system event) and Cloud DNS logs are sent to your Chronicle account. However, you can customize the export filter to include or exclude specific types of logs. The export filter is based on the Google logging query language.

To define a custom filter for your logs, complete the following steps:

• Define your filter by creating a custom filter for your logs using the logging query language.
  The following documentation describes how to define this type of filter: https://cloud.google.com/logging/docs/view/logging-query-language.
• Navigate to the Logs Explorer using the link provided on the EXPORT FILTER SETTINGS tab, copy your new query into the Query field and click Run Query to test it.
• Verify that the matched logs displayed in the Logs Explorer are exactly what you intend to export to Chronicle.

Export Filter Settings tab

Complete the following steps from the Export Filter Settings tab.

• When the filter is ready, click the edit icon and paste the filter to the Export filter field on the EXPORT FILTER SETTINGS tab.
• Click Save Custom Filter.
  Your new custom filter works against all new logs exported to your Chronicle account.
• You can reset the export filter to the default version by clicking Reset to Default.
  Be sure to save a copy of your custom filter first.

To enable GCP logs follow these steps:

• Under Security Tab, navigate to Detections and Controls --> Chronicle Secops. The following images show you the procedural steps.

To export your Google Cloud logs to Chronicle, set the Google Cloud logs toggle to enabled.
All of the Google Cloud log types listed above will be exported to your Chronicle account.

To enable google cloud logging, see the below screenshot.