<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Defender Antivirus on Anything About IT</title><link>https://www.verboon.info/tags/defender-antivirus/</link><description>Recent content in Defender Antivirus on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 25 Aug 2021 15:21:28 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/defender-antivirus/index.xml" rel="self" type="application/rss+xml"/><item><title>Use advanced hunting to Identify Defender clients with outdated definitions</title><link>https://www.verboon.info/2021/08/use-advanced-hunting-to-identify-defender-clients-with-outdated-definitions/</link><pubDate>Wed, 25 Aug 2021 15:21:28 +0000</pubDate><guid>https://www.verboon.info/2021/08/use-advanced-hunting-to-identify-defender-clients-with-outdated-definitions/</guid><description>&lt;p&gt;In an ideal world all of our devices are fully patched and the Microsoft Defender antivirus agent has the latest definition updates installed. Unfortunately reality is often different. When using Microsoft Endpoint Manager we can find devices with outdated definition updates through the Microsoft Endpoint Manager portal as shown in the example below.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/082521_1519_Useadvanced2.png" alt=""&gt;

&lt;/p&gt;
&lt;p&gt;Now in my opinion it must be the IT infrastructure operations team&amp;rsquo;s responsibility to ensure that devices get their patches installed and Defender gets its platform and definition updates. But sometimes the reason for devices not getting updates is because the platform used to manage the deployment of these updates might have an issue, be on the backend or client side.&lt;/p&gt;</description></item></channel></rss>