Skip to main content

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.

info

Google Security Operations has its own guide: Google SecOps. This page summarises the connection settings.

CategorySIEM
DirectionQuery source, alert source, rule target and destination
Sign-inService account key
Query languagesUDM search, STIX
Query templates7
Websitehttps://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.

  1. In Google SecOps, go to Settings › SIEM Settings › Profile and copy the Customer ID. Enter it as SecOps customer ID.
  2. 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 a huntbase-reader account with Chronicle API Viewer (roles/chronicle.viewer), an optional huntbase-writer account, and a JSON key for each. See the Google SecOps guide for the options and the manual steps.
  3. Keep huntbase-reader-key.json for the Connect step.

Permissions:

  • Read (required): roles/chronicle.viewer.
  • Rule writing (optional, a separate credential): custom role huntbaseSecOpsRuleWriter (Chronicle API Editor plus chronicle.rules.delete), made by the setup script.
  • Send data (optional, a separate credential): the same custom role.
Watch out for
  • 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.

tip

Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.

Connect Google Security Operations​

  1. Go to Connections and click New connection, or click New connection on the Google Security Operations product page.
  2. On Product, pick Google Security Operations and choose the Owner.
  3. On Details, give the connection a Name and, optionally, a Description.
  4. On Connect, fill in the settings and credentials described below.
  5. 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:

FieldRequiredNotes
RegionYesWhere 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 projectYesThe ID or number of the Google Cloud project linked to your SecOps instance.
SecOps customer IDYesThe Customer ID from Settings › SIEM Settings › Profile in SecOps.

Advanced settings​

These settings are under Advanced. You can usually leave them alone.

FieldRequiredNotes
API versionNoLeave at v1alpha unless Huntbase support asks you to change it. Defaults to v1alpha.
API hostNoNot 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:

FieldRequiredNotes
Service account key (JSON)YesThe 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:

LanguageUse it for
UDM searchNative Google SecOps UDM search, sent as written.
STIXSTIX patterns for indicator sweeps, translated into the product's native 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​