Skip to main content

Looking for some insight on the log source monitoring in Chronicle SIEM?

  • Aug 27, 2023 11:46 AM UTC
  • 11 replies
  • 106 views

Hopefully this is the right place - looking for some insight on what you all are doing for log source monitoring in Chronicle SIEM?

11 replies

  • Aug 27, 2023 11:47 AM UTC

We use silent log alerting from Chronicle. You will get an email if a log type stops sending data to Chronicle.


JaredBloomberg
Forum|alt.badge.img+4

How do you enable log alerting within Chronicle?


  • Aug 27, 2023 11:47 AM UTC

Chronicle support has to do it


JaredBloomberg
Forum|alt.badge.img+4

Thanks!


  • Aug 27, 2023 11:49 AM UTC

I was trying to find the details about it and came across the new way to do it.
https://cloud.google.com/chronicle/docs/ingestion/ingestion-notifications-for-health-metrics


  • Aug 27, 2023 11:49 AM UTC

For the current way, IIRC, the data type has to be silent for several hours before you’re notified.


Forum|alt.badge.img+16

Forum|alt.badge.img+16

if you have integrated your Chronicle SIEM instance with GCP you can use GCP Metrics for Forwarder, and Feed Management notifications, e.g., silent log source, or else abnormal deviation from baseline


Forum|alt.badge.img+16

  • Sep 11, 2023 8:33 AM UTC

I also have some questions about this: log type is nice for single sources on a log source type, but what with sysmon for example? Losing sight of one host may warrant an alert (domain controllers), but will never trigger on logtype alone. Any way to do that?


maxjunker
Forum|alt.badge.img+4
  • Bronze 5
  • Feb 19, 2024 3:24 PM UTC

Is there any other way to detect log source / log source type outages without BigQuery?
We don´t have GCP integration within our Chronicle tentans, but we need to detect if a log source stops sending events. 
I get that because of sliding windows a detection rule with YARAL is not sufficient (https://medium.com/@thatsiemguy/silent-asset-detection-47ad34fdab55)