This page 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.
Before you begin
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.
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 gCloud command-line tool, complete the following steps:
- Ensure you are logged into the correct organization. Verify this by running the
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.
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
Exporting Google Cloud Logs to Chronicle
To export your Google Cloud Logs to Chronicle, set the Export Cloud logs to Chronicle toggle to enabled.
Exporting Google Cloud Asset Metadata to Chronicle
You can export your Google Cloud Asset metadata to Chronicle. This asset metadata is drawn from your Google Cloud Asset Inventory and consists of information about your assets, resources, and identities including the following:
- Hardware models
Here are some examples of Google Cloud Asset metadata:
- Application name—
- Project name—
To export your Google Cloud Asset metadata to Chronicle, set the Export Cloud Asset Metadata to Chronicle toggle to enabled.
Exporting Security Command Center findings to Chronicle
You can export the following SCC Premium Event Threat Detection (ETD) findings to Chronicle:
- Malware: Bad IP
- Malware: Bad Domain
- Persistence: IAM Anomalous Grant
- Bruteforce: SSH
- Exfiltration: BigQuery Data Exfiltration
For more information about ETD, see here.
To export your SCC Premium ETD findings to Chronicle, set the Export Security Command Center Premium Findings to Chronicle toggle to enabled.
Disabling GCP Telemetry Ingestion
Check the box labeled I want to disconnect Chronicle and stop sending Google Cloud Logs into Chronicle.
Click Disconnect Chronicle.
- Open your Chronicle account using the customer specific URL provided by your Chronicle representative.
- Learn more about Chronicle.