<?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: Cortex XDR 7.1.1 reported as OLD defs after update from 7.0.1. in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-7-1-1-reported-as-old-defs-after-update-from-7-0-1/m-p/420904#M880</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/132468"&gt;@ChrisDow1111&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hello all.&amp;nbsp; We are using Global Protect with HIP rules turned on to enforce valid AV, etc. After an update to 7.1.1, HIP was seeing our virus definitions were dated 1/1/1970 for at least a few hours. Had to reboot before GlobalProtect would see current definitions.&amp;nbsp; Didn't have this problem with prior versions of Cortex XDR.&amp;nbsp; Additionally, the HIP rules saw 7.0.1 as Traps, but see the current version as Cortex XDR, which is interesting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen either of these things?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/132468"&gt;@ChrisDow1111&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thank you for contributing to the discussion board.&lt;/P&gt;&lt;P&gt;It would seem that GlobalProtect had some troubles getting accurate data from the Cortex XDR executables and libraries. Is this issue persisting for you on later versions of Cortex XDR? If a Support case was open with GlobalProtect engineers, were they able to guide you through tuning HIP check rules for upgrade scenarios? Or were you advised to disable HIP checks while the upgrades were scheduled?&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jul 2021 23:01:14 GMT</pubDate>
    <dc:creator>gjenkins</dc:creator>
    <dc:date>2021-07-20T23:01:14Z</dc:date>
    <item>
      <title>Cortex XDR 7.1.1 reported as OLD defs after update from 7.0.1.</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-7-1-1-reported-as-old-defs-after-update-from-7-0-1/m-p/333228#M182</link>
      <description>&lt;P&gt;Hello all.&amp;nbsp; We are using Global Protect with HIP rules turned on to enforce valid AV, etc. After an update to 7.1.1, HIP was seeing our virus definitions were dated 1/1/1970 for at least a few hours. Had to reboot before GlobalProtect would see current definitions.&amp;nbsp; Didn't have this problem with prior versions of Cortex XDR.&amp;nbsp; Additionally, the HIP rules saw 7.0.1 as Traps, but see the current version as Cortex XDR, which is interesting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen either of these things?&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2020 19:26:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-7-1-1-reported-as-old-defs-after-update-from-7-0-1/m-p/333228#M182</guid>
      <dc:creator>ChrisDow1111</dc:creator>
      <dc:date>2020-06-12T19:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR 7.1.1 reported as OLD defs after update from 7.0.1.</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-7-1-1-reported-as-old-defs-after-update-from-7-0-1/m-p/420904#M880</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/132468"&gt;@ChrisDow1111&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hello all.&amp;nbsp; We are using Global Protect with HIP rules turned on to enforce valid AV, etc. After an update to 7.1.1, HIP was seeing our virus definitions were dated 1/1/1970 for at least a few hours. Had to reboot before GlobalProtect would see current definitions.&amp;nbsp; Didn't have this problem with prior versions of Cortex XDR.&amp;nbsp; Additionally, the HIP rules saw 7.0.1 as Traps, but see the current version as Cortex XDR, which is interesting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen either of these things?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/132468"&gt;@ChrisDow1111&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thank you for contributing to the discussion board.&lt;/P&gt;&lt;P&gt;It would seem that GlobalProtect had some troubles getting accurate data from the Cortex XDR executables and libraries. Is this issue persisting for you on later versions of Cortex XDR? If a Support case was open with GlobalProtect engineers, were they able to guide you through tuning HIP check rules for upgrade scenarios? Or were you advised to disable HIP checks while the upgrades were scheduled?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jul 2021 23:01:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-7-1-1-reported-as-old-defs-after-update-from-7-0-1/m-p/420904#M880</guid>
      <dc:creator>gjenkins</dc:creator>
      <dc:date>2021-07-20T23:01:14Z</dc:date>
    </item>
  </channel>
</rss>

