<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Defender for Identity on Anything About IT</title><link>https://www.verboon.info/tags/defender-for-identity/</link><description>Recent content in Defender for Identity on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 06 Dec 2025 12:27:02 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/defender-for-identity/index.xml" rel="self" type="application/rss+xml"/><item><title>Exploring IdentityAccountInfo - Building a KQL Query to Assess Identity Password Security Posture</title><link>https://www.verboon.info/2025/12/exploring-identityaccountinfo-building-a-kql-query-to-assess-identity-password-security-posture/</link><pubDate>Sat, 06 Dec 2025 12:27:02 +0000</pubDate><guid>https://www.verboon.info/2025/12/exploring-identityaccountinfo-building-a-kql-query-to-assess-identity-password-security-posture/</guid><description>&lt;p&gt;Recently Microsoft Defender XDR introduced a new table called &lt;a href="https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-identityaccountinfo-table"&gt;IdentityAccountInfo&lt;/a&gt;, and this one immediately caught my attention. It brings several interesting attributes into Advanced Hunting, including &lt;code&gt;LastPasswordChangeTime&lt;/code&gt; and even the sensitivity classification of an identity.&lt;/p&gt;
&lt;p&gt;Naturally, my first thought was: this is perfect material for some hunting logic, so let&amp;rsquo;s build a KQL query out of it.&lt;/p&gt;
&lt;p&gt;Why am I excited about this? Because it finally allows us to query identity hygiene data straight from Defender. No external inventory dumps, no AD scripting, just KQL.&lt;/p&gt;</description></item><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><item><title>Shedding Light on Dormant Sensitive Accounts</title><link>https://www.verboon.info/2025/07/shedding-light-on-dormant-sensitive-accounts/</link><pubDate>Tue, 08 Jul 2025 15:34:54 +0000</pubDate><guid>https://www.verboon.info/2025/07/shedding-light-on-dormant-sensitive-accounts/</guid><description>&lt;p&gt;Dormant sensitive accounts are a high-risk identity exposure. In Microsoft Defender XDR, the recommendation &lt;strong&gt;Remove dormant accounts from sensitive groups&lt;/strong&gt; helps surface these accounts, including whether they are inactive, disabled, or have expired credentials.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/shedding-light-on-dormant-sensitive-accounts-01.png" alt=""&gt;

&lt;/p&gt;
&lt;p&gt;You can export the detected entities, but the export often contains limited context. In many cases, you only get entity names or SID values, which makes remediation harder when you need ownership and organizational details.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/shedding-light-on-dormant-sensitive-accounts-02.png" alt=""&gt;

&lt;/p&gt;
&lt;p&gt;A practical approach is to use the SID values to enrich the result set with identity attributes from &lt;code&gt;IdentityInfo&lt;/code&gt;. You can quickly build a SID variable list using KustoVars, then query Defender XDR for additional context.&lt;/p&gt;</description></item></channel></rss>