Microsoft Secure Tech Accelerator
Apr 03 2024, 07:00 AM - 11:00 AM (PDT)
Microsoft Tech Community

Azure ATP, Defender ATP + SysMon/Eventlog?

Copper Contributor

Hi all,

 

I am currently wondering about a project for one of our customers and would be happy to hear about your opinion.

 

We have been monitoring Windows Server with Event log, having them extended by SysMon. Now we are happy to have Azure ATP + Defender ATP available for the DCs / Servers. What do you think - should we still continue collecting event logs with SysMon and Monitoring Agent?

 

Thanks for your input!

 

Ralph

6 Replies

@Ralph Göbel My personal opinion is if the amount of data being ingested does not cost you too much money, and only you or your customer can really determine that,  it is worth ingestion.  I would have rather have the data and not need it than vice versa.

I would leave them running side by side and check what advantages you see with Sysmon/Eventlogs. They might generate alerts that MDATP does not see.

I don't usually do it as there is not much added value for it

@Thijs Lecomte  

 

Good evening.

I have a doubt.

 

The logs of the tables that Defender can send to Sentinel, as if it were a sysmon, is it possible to collect the logs that the Event Viewer generates?

 

That is, a Login Event_id 4624, or password lockout, for example, is it possible to collect via Defender / Sysmon or do I still need the Sentinle MMA agent installed to collect these logs?

Sysmon data is also collected through the MMA agent.

So you need the MMA when you want to retrieve events from the Event Viewer

@Thijs Lecomte 

 

Se recebo os logs via defender, que são semelhantes aos logs do sysmon, ainda preciso receber os logs do Event Viewer?

 

pagar_01.png

 

That is, a login log (4624), for example, does it come via defender or via symon, or does this log come only via installed MMA agent?

 

It really depends. Microsoft doesn't publish what events are ingested through MDE.
You need to check the logs, but I would guess these are in the table 'DeviceLogonEvents'. Have you checked here?