<?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: Escalate URL categorisation change in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514530#M106801</link>
    <description>&lt;P&gt;the categorization is primarily done by bots but submissions should also be reviewed by human eyes&lt;/P&gt;
&lt;P&gt;if you don't agree with the categorization you could open a support case and request a deeper look&lt;/P&gt;</description>
    <pubDate>Mon, 12 Sep 2022 08:03:51 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2022-09-12T08:03:51Z</dc:date>
    <item>
      <title>Escalate URL categorisation change</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514484#M106794</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I was wondering if there is any process for escalating a URL filter change? I have come across a website today called &lt;STRONG&gt;krudplug.net&lt;/STRONG&gt; that was categorised as streaming media. This website contains video footage of pornography, extreme violence and injury detail including murders and people being killed in accidents. I blocked the website and requested a URL change to Adult and to my surprise this request was rejected and the categorisation kept as streaming media. I requested a URL categorisation change again this time to extremism and it was returned as a categorisation change to questionable, still not really appropriate considering the content and one that I am concerned may revert back if they don't get more categorisation change requests for it.&lt;/P&gt;
&lt;P&gt;I am presuming it is bots doing the categorisation changes rather than people, is there a way&amp;nbsp; anyone knows of to escalate this further so that the site can be further investigated? I have checked online and found no way to do this, I am considering raising this with my point of contact at Palo Alto Networks to see if they could do anything about it.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2022 22:22:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514484#M106794</guid>
      <dc:creator>MichaelWrigh</dc:creator>
      <dc:date>2022-09-09T22:22:57Z</dc:date>
    </item>
    <item>
      <title>Re: Escalate URL categorisation change</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514530#M106801</link>
      <description>&lt;P&gt;the categorization is primarily done by bots but submissions should also be reviewed by human eyes&lt;/P&gt;
&lt;P&gt;if you don't agree with the categorization you could open a support case and request a deeper look&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2022 08:03:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514530#M106801</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2022-09-12T08:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: Escalate URL categorisation change</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514546#M106807</link>
      <description>&lt;P&gt;Thank you for the response, I am raising a support case with our supplier to ask if they can push this forward.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2022 09:54:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/escalate-url-categorisation-change/m-p/514546#M106807</guid>
      <dc:creator>MichaelWrigh</dc:creator>
      <dc:date>2022-09-12T09:54:59Z</dc:date>
    </item>
  </channel>
</rss>

