<?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: Palo URL Categorisation process in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330564#M83790</link>
    <description>&lt;P&gt;You have a few options here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;custom URL category for these URLs&lt;/P&gt;&lt;P&gt;block FQDN objects in the destination&lt;/P&gt;&lt;P&gt;Add very clear notes to the URL re-categorization request and hope whoever is working it reads them&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FWIW: I have always had great luck with re-categorization requests, sometimes you have to explain in the notes that there is something behind the login or there is a redirect etc&lt;/P&gt;</description>
    <pubDate>Fri, 29 May 2020 16:51:14 GMT</pubDate>
    <dc:creator>shawnhafen</dc:creator>
    <dc:date>2020-05-29T16:51:14Z</dc:date>
    <item>
      <title>Palo URL Categorisation process</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330204#M83752</link>
      <description>&lt;P&gt;We have been attempting to use URL Filtering to block access to web based email using the Palo Alto URL Category web-based-email.&lt;/P&gt;&lt;P&gt;We have found however that there are many web based email services that are not included in this category, including one of Australia's Largest ISP's telstra.&amp;nbsp; The url for this service is email.telstra.com.&amp;nbsp; I though it would be easy enough to log a re-categorisation request. But unfortunately the Palo Alto Categorisation process appear to be broken and not have any common sense.&lt;/P&gt;&lt;P&gt;When attempting to access email.telstra.com you are redirected to a generic logon page for tesltra with a url of sigon.telstra.com and because of this the url email.telstra.com can not be categorised as webmail sevice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2020 04:54:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330204#M83752</guid>
      <dc:creator>DaMonk</dc:creator>
      <dc:date>2020-05-28T04:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: Palo URL Categorisation process</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330468#M83767</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/50223"&gt;@DaMonk&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Both urls return as category 'Business and Economy'.&lt;/P&gt;
&lt;P&gt;Have you tried making a change request on the PAN url filtering page ?&lt;/P&gt;
&lt;P&gt;&lt;A href="https://urlfiltering.paloaltonetworks.com/" target="_blank" rel="noopener"&gt;https://urlfiltering.paloaltonetworks.com/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If all else fails you can create a custom URL category as a workaround.&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;
&lt;DIV id="ConnectiveDocSignExtentionInstalled" data-extension-version="1.0.4"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Fri, 29 May 2020 07:57:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330468#M83767</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2020-05-29T07:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: Palo URL Categorisation process</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330564#M83790</link>
      <description>&lt;P&gt;You have a few options here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;custom URL category for these URLs&lt;/P&gt;&lt;P&gt;block FQDN objects in the destination&lt;/P&gt;&lt;P&gt;Add very clear notes to the URL re-categorization request and hope whoever is working it reads them&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FWIW: I have always had great luck with re-categorization requests, sometimes you have to explain in the notes that there is something behind the login or there is a redirect etc&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2020 16:51:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-url-categorisation-process/m-p/330564#M83790</guid>
      <dc:creator>shawnhafen</dc:creator>
      <dc:date>2020-05-29T16:51:14Z</dc:date>
    </item>
  </channel>
</rss>

