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 Backstory
Identify or create credentials to access Chronicle Backstory with read access, at minimum.
API Calls
The following API calls are used by the Validation Platform.
Purpose | Call |
|---|---|
| To get all events associated | backstory.googleapis.com/v1/asset/listevents |
Update the Validation Platform
Prerequisites
Information to gather before you start:
- Identify the ProjectID associated with your Chronicle Backstory account
- In Chronicle Backstory, download your Service Account JSON file
Configuration
To add the Chronicle Backstory integration
Go to Settings > Integrations.
- Click Add Integration > Integration.
- Enter the Project ID from Chronicle Backstory.
- Upload your Chronicle Backstory Service Account JSON file.
Expand Advanced options and update the information if necessary.
(Optional) Assign a Name.
(Optional) Choose Yes to save suspicious events.
Click Submit.
Set up Proxy Assignment
If all outbound connections go through a proxy, you may want to set up a proxy definition and assignment for your integration. For information on setting up your proxy rules, see Proxy Rules.
Verify connectivity
To verify connectivity to Chronicle Backstory
Click Test to verify that:
- The Director can communicate with the integration host on the port and protocol specified.
- The integration credentials are valid and working.