Google SecOps (Chronicle)

WARNING

For collector v1.63.0 or older, Fallback Log Type is required.

---

Currently v2 of the legacy ingestion API and the alpha version of the DataPlane API are supported

Supported Types

Metrics	Logs	Traces
	✓

Prerequisites

Before setting up the Google SecOps destination, ensure you have a Google Cloud account and access to the Google SecOps security analytics platform. More details on setting this up can be found in the Google Cloud documentation here

Configuration Fields

Protocol

• gRPC selects the legacy API, using the malachite endpoints and gRPC for ingestion

• https selects the DataPlane API, using the DataPlane endpoints and HTTP for ingestion - Setup Walkthrough here

Legacy Ingestion API (Malachite)

Field	Description
Endpoint	The endpoint for sending to Google SecOps.
Authentication Method	Method used for authenticating to Google Cloud: auto, json, file.
Credentials	JSON value from a Google Service Account credential file. Required if Authentication Method is set to 'json'.
Credentials File	Path to a Google Service Account credential file on the collector system. Required if Authentication Method is set to 'file'.
Fallback Log Type	Type of log to be sent to Google SecOps. This field is a fallback if type is not configured using the Google SecOps Standardization processor. The Supported Log Types can be seen here.
Customer ID	The customer ID used for sending logs.
Field to Send	If Send Single Field is selected, Body or Attributes to select the source of the field to send
Body Field or Attribute Field	If Send Single Field is selected, an OTTL formatted field from either the Body or Attributes that contains the raw log data

DataPlane API (https)

Field	Description
Region	The Google SecOps region to send to. Ingestion will only succeed for regions your credentials are provisioned for.
Authentication Method	Method used for authenticating to Google Cloud: auto, json, file.
Credentials	JSON value from a Google Service Account credential file. Required if Authentication Method is set to 'json'.
Credentials File	Path to a Google Service Account credential file on the collector system. Required if Authentication Method is set to 'file'.
Fallback Log Type	Type of log to be sent to Google SecOps. This field is a fallback if type is not configured using the Google SecOps Standardization processor. The Supported Log Types can be seen here.
Customer ID	The customer ID used for sending logs.
GCP Project Number	The GCP Project Number used for sending logs. This can be located in settings on your profile page.
Forwarder Config ID	The Config ID of the forwarder used for sending logs. Found in the Forwarders section of the SecOps Settings.
Field to Send	If Send Single Field is selected, Body or Attributes to select the source of the field to send
Body Field or Attribute Field	If Send Single Field is selected, an OTTL formatted field from either the Body or Attributes that contains the raw log data

Sources

Google SecOps expects to be sent raw unstructured logs. Therefore, when sending logs to SecOps, you should only use the following supported sources:

• Windows Events (With Advanced -> “Raw Logs” enabled)

• Microsoft SQL Server

• Common Event Format

• CSV

• File

• HTTP

• TCP

• UDP

Log Type Handling / Google SecOps Parsing

Google Secops uses the log_type ingestion label to determine which SecOps Parser should be applied to logs. In Bindplane you can set the log_type ingestion label in one of the following ways:

1. Automatic Mapping: Bindplane will automatically create the log_type ingestion label for sources that use one of the following log_types. In these cases, you don’t need to take any action.

   attributes[“log_type”]	chronicle_log_type (Ingestion Label)
   windows_event.security	WINEVTLOG
   windows_event.application	WINEVTLOG
   windows_event.system	WINEVTLOG
   sql_server	MICROSFT_SQL

2. Set Google SecOps Log Type: You can use the Google SecOps Standardization Processor to specify the appropriate SecOps ingestion label (log_type). It’s best practice to always explicitly set this when sending logs to Google Secops. You can optionally specify a namespace to identify an appropriate data domain and add additional ingestion labels to configure custom metadata.

Note: The log_type field will take precedence over any automatic mapping that may occur.

1. Fallback: The Google SecOps Destination has a Fallback Log Type field that you can set as a fallback option, in the case that you did not set chronicle_log_type or Bindplane couldn’t automatically map the log_type for you.

Credentials

This exporter requires a Google Cloud service account with access to the Google SecOps API. The service account must have access to the endpoint specified in the config. For the legacy API (gRPC), besides the default endpoint (https://malachiteingestion-pa.googleapis.com), there are also regional endpoints that can be used here. When using the DataPlane API (https), the available regions can be found here.

For additional information on accessing SecOps, see the Chronicle documentation, and DataPlane documentation

Supported Retry and Queuing Settings

This destination supports the following retry and queuing settings:

Sending Queue	Persistent Queue	Retry on Failure
✓	✓	✓

Log Batch Creation Limits

This exporter supports configuring the batch request size, so as to not exceed the SecOps backend limits. Requests that exceed the configured limit will have their batches recursively split into multiple requests that don't before being sent to Google SecOps. The default limits for this exporter are 4000000 bytes (4 MB) for the request size. This value should not be increased without guidance from your Google SecOps or Bindplane representative.

If the setting is misconfigured to exceed the SecOps backend limit, requests that exceed the backend limit will be rejected and dropped.