Google SecOps
Leak events are sent to your Google SecOps instance as records.
How it works
The connection uses a service account. The private key is used only to sign the request; it is never placed in one.
Records arrive with the type given during setup; DARK_RADAR is used if it is left empty. The region is also selected during setup.
Delivery is one-way. No search is run on the instance and no rule is read.
Limits
The service account is given ingest permission only.
The leaked value itself is not in the record.
Turning the connection off stops delivery.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.