Google Security Operations
Google Security Operations (Google SecOps, formerly Chronicle) is Google's cloud SIEM. It ingests security telemetry from endpoints, networks, cloud platforms, identity providers and security tools, normalises it to the Unified Data Model (UDM), and keeps it searchable for a year or more. Detection rules are written in YARA-L 2.0, and Google also ships curated detections that run on your data.
Google Security Operations has its own guide: Google SecOps. This page summarises the connection settings.
| Category | SIEM |
| Direction | Query source, alert source, rule target and destination |
| Sign-in | Service account key |
| Query languages | UDM search, STIX |
| Query templates | 7 |
| Website | https://cloud.google.com/security/products/security-operations |
Before you start
Huntbase signs in to Google Security Operations with Service account key. Create the credential in Google Security Operations first, then keep it to hand for the Connect step.
- In Google SecOps, go to Settings › SIEM Settings › Profile and copy the Customer ID. Enter it as SecOps customer ID.
- In Google Cloud Shell, run the setup script for the project linked to SecOps,
bash google-secops-setup.sh --project <project-id>(download it from https://docs.huntbase.io/scripts/google-secops-setup.sh). It creates ahuntbase-readeraccount with Chronicle API Viewer (roles/chronicle.viewer), an optionalhuntbase-writeraccount, and a JSON key for each. See the Google SecOps guide for the options and the manual steps. - Keep
huntbase-reader-key.jsonfor the Connect step.
Permissions:
- Read (required):
roles/chronicle.viewer. - Rule writing (optional, a separate credential): custom role
huntbaseSecOpsRuleWriter(Chronicle API Editor pluschronicle.rules.delete), made by the setup script. - Send data (optional, a separate credential): the same custom role.
- If your organization enforces Disable service account key creation (
iam.disableServiceAccountKeyCreation), key creation fails. Ask an Organization Policy Administrator for an exception on the SecOps project only. It can take a few minutes to apply. - A 404 usually means the region, project or instance ID doesn't match the instance.
For the vendor's own instructions, see Google SecOps Chronicle API documentation.
Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.
Connect Google Security Operations
- Go to Connections and click New connection, or click New connection on the Google Security Operations product page.
- On Product, pick Google Security Operations and choose the Owner.
- On Details, give the connection a Name and, optionally, a Description.
- On Connect, fill in the settings and credentials described below.
- On Verify, review the summary and click Create & check.
For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.
Settings
Where your Google Security Operations lives:
| Field | Required | Notes |
|---|---|---|
| Region | Yes | Where your instance runs, such as us, eu or europe-west2. It is the region in the API address https://<region>-chronicle.googleapis.com. |
| Google Cloud project | Yes | The ID or number of the Google Cloud project linked to your SecOps instance. |
| SecOps customer ID | Yes | The Customer ID from Settings › SIEM Settings › Profile in SecOps. |
Advanced settings
These settings are under Advanced. You can usually leave them alone.
| Field | Required | Notes |
|---|---|---|
| API version | No | Leave at v1alpha unless Huntbase support asks you to change it. Defaults to v1alpha. |
| API host | No | Not needed for new connections. Leave it empty. |
Credentials
The only Method is Service account key. Enter a Credential label (for example Production), then fill in:
| Field | Required | Notes |
|---|---|---|
| Service account key (JSON) | Yes | The whole JSON key file of the service account, pasted or uploaded. Secret — not shown again after you save it. |
Query it
Once connected, Google Security Operations can serve these languages in a query tab, and Scout can use it when you ask in Auto:
| Language | Use it for |
|---|---|
| UDM search | Native Google SecOps UDM search, sent as written. |
| STIX | STIX patterns for indicator sweeps, translated into the product's native search. |
Example: UDM search
Failed sign-ins from one address — Blocked sign-ins (Windows 4625 and other failed logins).
metadata.event_type = "USER_LOGIN" AND security_result.action = "BLOCK"
Google Security Operations ships with 7 query templates. Find them in Library › Queries — see Query templates.
Next steps
- Connections — health, credentials and settings after you connect
- Query languages — syntax, parameters and time ranges
- Chatting with Scout — ask questions without writing a query
- All integrations — the rest of the catalog