Google Chronicle

Google Chronicle SecOps SIEM. Pulls detections and supports UDM searches. Auth is via a Google Cloud service account JSON key with chronicle.* roles.

• Connector id: chronicle
• Category: siem

Configuration

Field	Label	Type	Required	Default	Notes
region	Region	select	yes	—	one of: us, europe, asia-southeast1, asia-northeast1, australia-southeast1
project_id	GCP Project ID	string	yes	—	—
customer_id	Chronicle Customer ID	string	yes	—	UUID of your Chronicle tenant.
service_account_json	Service Account JSON	secret	yes	—	encrypted at rest · Paste the entire service-account JSON key.

Credential handling

service_account_json is encrypted at rest by the credential vault before the row is written, and decrypted only at poll time. The value is never logged and never returned by the API — a read of the saved connector shows the field as set, not its contents. See credential vault.

Setup

1. In the console, go to Connectors → Add connector and pick Google Chronicle.
2. Fill in the fields above and run Test connection. The test is read-only and does not save anything.
3. Save. Polling starts on a jittered schedule within about a minute; the connector row shows last_sync once the first poll completes.

If last_sync stays empty

The first poll is the honest signal that the credential works. A connector that saves cleanly and never syncs usually means the credential lacks a scope the vendor requires for reads — check the connectors service log for the vendor's own error, which is passed through verbatim rather than summarised.

Vendor-specific setup notes go here: which console page issues the credential, which scopes to grant, rate limits, and anything the schema cannot express. This section is preserved when the page is regenerated.