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
- Cloud logs are written: audit, network, identity.
- A stream picks them up: Firehose, Event Hub, Pub/Sub, or Connector Hub.
- The collector: Splunk, Sentinel, or your own.
- Searchable in one place: next to endpoint and identity data.
| Platform | Uses | The part that catches people |
|---|---|---|
| AWS | Kinesis Firehose to a Splunk HTTP event collector | Firehose will not deliver to a token without indexer acknowledgement. |
| Azure | Event Hubs, read by your SIEM's Azure input or a Sentinel workspace | A diagnostic setting streams only to a hub in the resource's own region. |
| Google Cloud | Pub/Sub to your collector | A subscription nobody reads for 31 days is deleted by default, and the feed ends with no error. |
| Oracle Cloud | Connector Hub copying audit events to a stream the SIEM reads | Audit events are regional. |
Run the quick start
| Download providers | terraform init |
| Preview | terraform plan |
| Apply | terraform 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.