<?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 Behaviour identifying SSL after dynamic updates installation in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176274#M55134</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last night the scheduled&amp;nbsp;dynamic installation was done, the new version 734-4212 (apps) was installed. When this installation happened a lot of traffic before detected like ssl in previous version, it was being detected like "not-applicable" and jumping all rule until default deny. We did a revert updated packet to solve it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why PA suddenly stop identifying ssl app with this new update package??? what should we do in order to prevent this fail identifying apps in new apps package??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How should we procced_&amp;nbsp;Do we re-apply the current version? we should wait for a new one (junmping 734-4241 which is not identifying properly SSL?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 13 Sep 2017 08:53:54 GMT</pubDate>
    <dc:creator>soporteseguridad</dc:creator>
    <dc:date>2017-09-13T08:53:54Z</dc:date>
    <item>
      <title>Behaviour identifying SSL after dynamic updates installation</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176274#M55134</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last night the scheduled&amp;nbsp;dynamic installation was done, the new version 734-4212 (apps) was installed. When this installation happened a lot of traffic before detected like ssl in previous version, it was being detected like "not-applicable" and jumping all rule until default deny. We did a revert updated packet to solve it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why PA suddenly stop identifying ssl app with this new update package??? what should we do in order to prevent this fail identifying apps in new apps package??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How should we procced_&amp;nbsp;Do we re-apply the current version? we should wait for a new one (junmping 734-4241 which is not identifying properly SSL?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 08:53:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176274#M55134</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2017-09-13T08:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour identifying SSL after dynamic updates installation</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176284#M55138</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/9102"&gt;@soporteseguridad&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I haven't heard of any issues yet.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The application column shows&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;not-applicable&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;if the traffic matches an allowing/blocking security rule via a service filter rather than an application filter :&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/quot-Not-applicable-quot-in-Traffic-Logs/ta-p/65745" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/quot-Not-applicable-quot-in-Traffic-Logs/ta-p/65745&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To prevent any unwanted things from happening you could configure a threshold in your update schedule.&lt;/P&gt;
&lt;P&gt;If you decide to configure this threshold then please consider this DOC :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/Dynamic-updates-scheduled-with-a-threshold-set-but-are-never-or/ta-p/65952" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/Dynamic-updates-scheduled-with-a-threshold-set-but-are-never-or/ta-p/65952&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 09:38:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176284#M55138</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2017-09-13T09:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour identifying SSL after dynamic updates installation</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176291#M55141</link>
      <description>&lt;P&gt;An example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before apps package was identifying properly the apps SSL. Traffic SSL and rule defined.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="new.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/11243i7255E86994DD7C2E/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="new.png" alt="new.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After installing last package (last night), we detect problem idetifying SSL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="old.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/11245i5534F49BD600F3C9/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="old.png" alt="old.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why its not identifying SSL with the new apps package??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 10:01:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176291#M55141</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2017-09-13T10:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour identifying SSL after dynamic updates installation</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176304#M55149</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/9102"&gt;@soporteseguridad&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;While I can't speak to this being a widespread issue as I don't have the current update installed on even my test enviroment at the moment, I would highly recommmend you put some type of delay on your production equipment so that the update needs to be x number of hours old before it gets applied. This usually gives those of us with test envioroments or those that don't have a delay set to notice any potential issues so PA has a chance to pull the update if it trully causes any issues.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 12:47:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176304#M55149</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-09-13T12:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour identifying SSL after dynamic updates installation</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176346#M55158</link>
      <description>&lt;P&gt;I cant find the cause why PA is not detecting this SSL traffic. I think it could be a widespead issue. If anyone has any PA confirmation just let me know.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 14:29:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176346#M55158</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2017-09-13T14:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour identifying SSL after dynamic updates installation</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176354#M55161</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/9102"&gt;@soporteseguridad&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you reached out to TAC about this ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this was a widespread issue,&amp;nbsp;I would have expected&amp;nbsp;more similar reactions&amp;nbsp;(as with content 729 about 2 weeks ago).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-Kiwi.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 14:41:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-identifying-ssl-after-dynamic-updates-installation/m-p/176354#M55161</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2017-09-13T14:41:32Z</dc:date>
    </item>
  </channel>
</rss>

