iac.htora.dev · security templates

Home/Refreshers/Get cloud logs into your SIEM: refresher

Get cloud logs into your SIEM

A delivery pipe from cloud logging to the place your detections actually run.

Remember

  1. Cloud logs are written: audit, network, identity.
  2. A stream picks them up: Firehose, Event Hub, Pub/Sub, or Connector Hub.
  3. The collector: Splunk, Sentinel, or your own.
  4. Searchable in one place: next to endpoint and identity data.
PlatformUsesThe part that catches people
AWSKinesis Firehose to a Splunk HTTP event collectorFirehose will not deliver to a token without indexer acknowledgement.
AzureEvent Hubs, read by your SIEM's Azure input or a Sentinel workspaceA diagnostic setting streams only to a hub in the resource's own region.
Google CloudPub/Sub to your collectorA subscription nobody reads for 31 days is deleted by default, and the feed ends with no error.
Oracle CloudConnector Hub copying audit events to a stream the SIEM readsAudit events are regional.

Run the quick start

Download providersterraform init
Previewterraform plan
Applyterraform apply

Watch out

  • Watch the pipe as closely as what flows through it.
  • Each pipe keeps what it could not deliver: refused events in a bucket on AWS, and seven days of messages plus a dead-letter subscription on Google Cloud.
Check it worked

Do one thing you can recognise. Search for it in the SIEM and find it.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.