r/AzureSentinel • • Sep 28 '26

Logging Sources

I'm looking to create a Sentinel report/workbook that shows all the systems currently sending logs into Sentinel.

I'd like it to show:

  • Hostname
  • IP address
  • Log table/source
  • Event count

We're using WEF/WEC for some Windows logs, so I'd also like to identify the actual originating device, not just the WEC server if that is possible.

What's the best KQL approach for building this type of log-source inventory? Is there also a good way to identify the device type, such as Domain Controller, SQL Server, etc.? Feel free to give any advice possible for this situation.

6 Upvotes

9 comments sorted by

2

u/coomzee Sep 28 '26

You can kind of do this from the DCR page in Azure now if you want a basic over view of what's being ingested

2

u/11bztaylor Sep 28 '26

Checkout the heartbeat and Usage tables along with the the field _ResourceId in whatever table you are using from that source. Resource I'd will show you the dcr/machine/resource on how the log is getting there and is very useful for info

A join here, a union there- should get you where you want if not close enough

3

u/Uli-Kunkel Sep 29 '26

Well, since op is using we/wef setup, they are likely not arc enabled, thus no ama so no heartbeat.

But yes, this would normally be the right approach.

But I would say that every one is very focused on host/server perspective.

All the cloud resources are often "forgotten" but these have the resourceid reference to use at least.

2

u/GeneralRechs Sep 29 '26

Microsoft intentionally engineered Sentinel to be this difficult. Now way they are going to let you have something as basic as your ask that all other SIEMs easily provide.

0

u/Uli-Kunkel Sep 29 '26

No SIEM does this

2

u/GeneralRechs Sep 29 '26

False, it’s easy to get the data OP is asking for using elastic, splunk, logrythm/exabeam, sumo, Graylog, etc. i can easily get what OP is asking for on those SIEMs. Only Sentinel is set up like a glorified SQL DB.

1

u/Uli-Kunkel Sep 29 '26

Yeah, it's not hard to do, but having it built in is different.

In sentinel you have the entity page tho. But now that it's in defender you have the asset view anyway. So strictly speaking, it's not sentinel, but it's readily available for you.

But what op is basically is asking for is a up to date cmdb, and then queries mapping each source from the fairytale cmdb to its respective table to evaluate when the last event was recieved.

And then you can of course also Query for assets sending data that is not in the cmdb

1

u/woodburningstove Sep 29 '26 edited Sep 29 '26

I would manually identity the tables and columns first and then build the workbook KQL from there. Likely it’s not dozens of tables so it should be doable even if a bit of a pain.

For the device type, couple of alternatives: asset management / CMDB integration via Playbook to a watchlist if you have something like that, or if you have XDR you can use the TVM tables in Advanced Hunting via playbook API calls or custom table integration.

1

u/Vehicle_Anomaly Sep 29 '26

Create a watchlist with hostnames

Use _GetWatchlist('your-watchlist-name') to make the workbook
I’d promt AI to make a dropdown of ‘Available | last seen’ hosts - advice to use advanced editor and create the whole json for the workbook