<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Driver updates and vulnerable_driver_dropped_WinRing0.sys in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/driver-updates-and-vulnerable-driver-dropped-winring0-sys/m-p/513235#M2740</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/204243"&gt;@MartinPfeil&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this rule was brought in with content update 650. This is a behavioural threat event and has nothing to do with wildfire verdict being malware/benign. Rather, it is triggered because the Winring.0.sys is listed as a vulnerable driver software used by multiple vendors. The vendors have brought out new patches into their driver softwares and in cases of endpoints which have the outdated driver, and are dropped, Cortex detects and prevents the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Aug 2022 08:42:28 GMT</pubDate>
    <dc:creator>neelrohit</dc:creator>
    <dc:date>2022-08-29T08:42:28Z</dc:date>
    <item>
      <title>Driver updates and vulnerable_driver_dropped_WinRing0.sys</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/driver-updates-and-vulnerable-driver-dropped-winring0-sys/m-p/513230#M2739</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;over the last couple of days we have seen a lot of behavioural alerts with&amp;nbsp; s&lt;SPAN&gt;vulnerable_driver_dropped_WinRing0.sys&lt;/SPAN&gt;&amp;nbsp;preventing HP and Lenovo signed drivers being updated. Obviously these are false positives, as WF and VT confirms-&lt;/P&gt;
&lt;P&gt;Before I open a ticket, does anybody see similar behaviour?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2022 08:14:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/driver-updates-and-vulnerable-driver-dropped-winring0-sys/m-p/513230#M2739</guid>
      <dc:creator>MartinPfeil</dc:creator>
      <dc:date>2022-08-29T08:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Driver updates and vulnerable_driver_dropped_WinRing0.sys</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/driver-updates-and-vulnerable-driver-dropped-winring0-sys/m-p/513235#M2740</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/204243"&gt;@MartinPfeil&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this rule was brought in with content update 650. This is a behavioural threat event and has nothing to do with wildfire verdict being malware/benign. Rather, it is triggered because the Winring.0.sys is listed as a vulnerable driver software used by multiple vendors. The vendors have brought out new patches into their driver softwares and in cases of endpoints which have the outdated driver, and are dropped, Cortex detects and prevents the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2022 08:42:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/driver-updates-and-vulnerable-driver-dropped-winring0-sys/m-p/513235#M2740</guid>
      <dc:creator>neelrohit</dc:creator>
      <dc:date>2022-08-29T08:42:28Z</dc:date>
    </item>
  </channel>
</rss>

