This document applies to Classic/Legacy Integrations. You may continue to use these integration configurations. While no active development is happening for these integrations, we continue to provide Classic/Legacy Integrations in the product. You do not have to move to MSI Integrations. If your support engineer or TSC recommends or you choose to move to MSI Integrations, you can take advantage of the latest features and functionality. For more information, see the MSI Integration documentation in the Integrations Overview.
Update Google BigQuery
Identify or create the service account credentials to access BigQuery.
- BigQuery does not support API keys, you must use a service account.
- Authentication requires the json file for the service account for the BigQuery project.
Update the Validation Platform
Prerequisites
Information to gather before you start:
- Identify the BigQuery project ID.
- Identify the BigQuery data set ID.
- Identify the table and schema used in the data set.
- Identify the json file for the service account authentication.
Identify the field name mappings for the following:
- Source IP
- Destination IP
- Source Port
- Destination Port
- Event Start Time (timestamp)
- Event Unique ID
- Event Signature ID
- Event Description
Configuration
To add the Google BigQuery integration
Go to Settings > Integrations.
Click Add Integration > Google BigQuery.
- Enter the Project ID, DataSet ID, and upload the json file for the service account.
Modify the Query with the appropriate columns for the table's schema.
Do not change the words inside the percent (%) symbolsExpand Advanced options.
(Optional) Update Query time and Delay time.
The Query time is the amount of time (minutes) before and after the query runs that the looks for events, while the Delay time is the amount of time (minutes) that the platform waits to run the query after a Job Action. For example, you configure your integration with the following values: Query time = 5, Query interval = 30 seconds, and Delay time = 0. When a Job Actions starts at 12:00:00, the first time the query runs, the platform looks for events from 11:55:00 to 12:00:00. Then 30 seconds later, it looks for events from 11:55:30 to 12:00:30. This interval continues, with the last query looking from 12:00:00 to 12:05:00. If you instead configured the Delay time to equal 10, it would run the same query, but it wouldn't start that query until 12:10:00.If your monitors are set to run more frequently than the query time, it will impact the pass/fail results for AEDA monitors.(Optional) Select Enable query for Malicious DNS Actions and configure the Query. This query will only be used when you run Malicious DNS Actions or Captive DNS Actions.
(Optional) Select Enable query for Email Actions and configure the Query. This query will be only be used when you run Email Actions.
Review the field name mappings and update as necessary.
- The field should only contain the name of the column in your table schema that maps to the given field name.
- Example:
Source IP: source_ip
(Optional) Select Discover network devices automatically.
If this is not selected, new events processed by the integration will not have discovered or related network or endpoint security technologies.
Modify the Query Interval and Event Time Adjustment, if necessary.
(Optional) Assign a Name.
(Optional) Choose Yes to save suspicious events.
Click Submit.
Verify connectivity
To verify connectivity to Google BigQuery
Click Test to verify that:
- The Director can communicate with Google BigQuery, and the Project ID and DataSet ID are correct.
- The service account credentials provided can perform queries on the project, dataset, and table.
Run a Malicious or Captive DNS Action and then review the last run query to verify:
- The custom DNS query works as expected (if configured).