<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Event Auditing on Anything About IT</title><link>https://www.verboon.info/tags/event-auditing/</link><description>Recent content in Event Auditing on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Nov 2025 14:29:46 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/event-auditing/index.xml" rel="self" type="application/rss+xml"/><item><title>Defender for Identity - Automatic Windows Event Auditing Configuration</title><link>https://www.verboon.info/2025/11/defender-for-identity-automatic-windows-event-auditing-configuration/</link><pubDate>Sat, 22 Nov 2025 14:29:46 +0000</pubDate><guid>https://www.verboon.info/2025/11/defender-for-identity-automatic-windows-event-auditing-configuration/</guid><description>&lt;p&gt;One of the most common issues we encounter during Defender for Identity assessments is misconfiguration. Many organizations assume that installing the sensor is the final step, but proper post-installation configuration is just as important.&lt;/p&gt;
&lt;p&gt;In particular, enabling the required Windows event auditing policies is essential for full detection capabilities. Without these settings, functionality is degraded and health notifications start to appear.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/defender-for-identity-automatic-windows-event-auditing-configuration-01.png" alt=""&gt;

&lt;/p&gt;
&lt;p&gt;Defender for Identity relies on specific Windows audit categories and subcategories to capture critical events.&lt;/p&gt;</description></item></channel></rss>