Google SecOps

Step-by-step guides for configuring Bindplane with Google SecOps.

Google SecOps with Bindplane Quick Start

The fastest way to configure Bindplane with Google SecOps and start ingesting telemetry right away. See Google SecOps with Bindplane Quick Start for details.

Using Google SecOps with Bindplane Best Practices

Best practices and considerations when deploying Bindplane to capture logging data for Google SecOps (SIEM). See Using Google SecOps with Bindplane for details.

Google SecOps Silent Host Monitoring

Using Silent Host Monitoring for Google SecOps allows you to create alerts for changes in ingestion rates through Google Cloud Monitoring. See Google SecOps Silent Host Monitoring for details.

Google SecOps Configuring the 'HTTPS' (Dataplane API) protocol

The Google SecOps Destination can use either gRPC or HTTPS connection methods. Learn how to connect HTTPS when there are limitations in the environment that make a gRPC connection impossible. See Google SecOps Configuring the 'HTTPS' (Dataplane API) protocol for details.

Migrating from the Deprecated Google Chronicle Forwarder

Google SecOps is officially deprecating the Chronicle (SecOps) legacy forwarder in January 2027. All data ingestion will transition to OpenTelemetry (OTel) collectors using Bindplane as the official ingestion platform. See Migrating from the Deprecated Google Chronicle Forwarder for details.

Connect the Google SecOps Integration with WIF Auth

Configure Google SecOps for secure communication with Bindplane using Workload Identity Federation (WIF), without sharing long-lived service account keys. See Connect the Google SecOps Integration with WIF Auth for details.