<?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: False positive High-Risk classification for legitimate healthcare SaaS (gmedic.co) in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254133#M6929</link>
    <description>&lt;P class=""&gt;I have a similar situation - my domain berksfhs.org was incorrectly classified as Malware, and submitting a dispute via urlfiltering.paloaltonetworks.com resulted in the category being corrected (from Malware to Reference-and-Research) but the Risk Level remained High-Risk.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I submitted a second dispute specifically asking for the Risk Level to be reviewed, with supporting evidence including the fact that my domain is now clean at every other major reputation database (Google, VirusTotal, BrightCloud, Symantec, Trellix, IBM X-Force, Kaspersky). The dispute form does not have a Risk Level field - only a category field - and the automated reply confirmed that only the category was reviewed. Risk Level was not addressed. My second submission produced exactly the same outcome as the first: a category response with no comment on the Risk Level despite the explanatory note in the comment field.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I am also a non-customer (volunteer webmaster for a UK registered charity) so the customer support channel is not available to me.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;It would be very useful if a Palo Alto staff member could confirm what the actual process is for requesting Risk Level review when (a) the urlfiltering portal handles only category disputes in practice and (b) the affected domain owner does not have a customer support contract. Without that, it appears there is no functioning route to resolution,a nd we are stuck with a risk factor that was created based on erroneous info from a warning sent by Netcraft in December and which they retracted as an error in under 24 hours.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;Paul Barrett&lt;/P&gt;&lt;P class=""&gt;Volunteer Webmaster,&lt;/P&gt;&lt;P class=""&gt;Berkshire Family History Society&lt;/P&gt;</description>
    <pubDate>Sat, 16 May 2026 16:56:06 GMT</pubDate>
    <dc:creator>paul.barrett</dc:creator>
    <dc:date>2026-05-16T16:56:06Z</dc:date>
    <item>
      <title>False positive High-Risk classification for legitimate healthcare SaaS (gmedic.co)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1253975#M6924</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;A href="https://gmedic.co" target="_blank" rel="noopener"&gt;https://gmedic.co&lt;/A&gt; is a legitimate healthcare SaaS platform used by healthcare professionals in Colombia.&lt;/P&gt;
&lt;P&gt;The domain is correctly categorized as Health-and-Medicine, however it is currently flagged as High-Risk.&lt;/P&gt;
&lt;P&gt;We already verified:&lt;BR /&gt;- no malicious content&lt;BR /&gt;- no phishing&lt;BR /&gt;- no malware&lt;BR /&gt;- clean reverse IP&lt;BR /&gt;- dedicated legitimate hosting&lt;/P&gt;
&lt;P&gt;The issue seems related to ASN/IP reputation or an automated false positive.&lt;/P&gt;
&lt;P&gt;Could someone from PAN-DB / URL Filtering team review this domain manually?&lt;/P&gt;
&lt;P&gt;Thank you.&lt;BR /&gt;Gerson Samaniego&lt;BR /&gt;CEO &amp;amp; Lead Developer&lt;BR /&gt;&lt;A href="https://www.linkedin.com/in/gerson-samaniego/" target="_blank" rel="noopener"&gt;https://www.linkedin.com/in/gerson-samaniego/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2026 00:21:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1253975#M6924</guid>
      <dc:creator>gersonjohan</dc:creator>
      <dc:date>2026-05-14T00:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: False positive High-Risk classification for legitimate healthcare SaaS (gmedic.co)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254096#M6927</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1566120575"&gt;@gersonjohan&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="4"&gt;Thank you for reaching out.&lt;/P&gt;
&lt;P data-path-to-node="4"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;Please note that &lt;STRONG data-index-in-node="17" data-path-to-node="5"&gt;LIVEcommunity is a peer-to-peer forum&lt;/STRONG&gt; and we do not have the ability to manually adjust domain risk scores here.&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;To have your domain reviewed and the 'High-Risk' flag reassessed by PANWs URL Filtering researchers, you must submit a formal request through our official portal:&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="6"&gt;&lt;A class="ng-star-inserted" href="https://urlfiltering.paloaltonetworks.com/" target="_blank" rel="noopener"&gt;Palo Alto Networks Test A Site&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL start="1" data-path-to-node="8"&gt;
&lt;LI&gt;
&lt;P data-path-to-node="8,0,0"&gt;Enter your URL (&lt;CODE data-index-in-node="16" data-path-to-node="8,0,0"&gt;&lt;A href="https://gmedic.co" target="_blank"&gt;https://gmedic.co&lt;/A&gt;&lt;/CODE&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="8,1,0"&gt;Once the current category and risk appear, click on &lt;STRONG data-index-in-node="52" data-path-to-node="8,1,0"&gt;"Request Change."&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="8,2,0"&gt;In the comments section, I recommend including the points you mentioned above (specifically that this is a Healthcare SaaS platform and your clean reverse IP/hosting status).&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P data-path-to-node="9"&gt;Once submitted, the PAN-DB team reviews these requests. This is the only way to ensure the automated risk score is updated across the global database.&lt;/P&gt;
&lt;P data-path-to-node="9"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="9"&gt;Kind regards,&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2026 09:34:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254096#M6927</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2026-05-15T09:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: False positive High-Risk classification for legitimate healthcare SaaS (gmedic.co)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254133#M6929</link>
      <description>&lt;P class=""&gt;I have a similar situation - my domain berksfhs.org was incorrectly classified as Malware, and submitting a dispute via urlfiltering.paloaltonetworks.com resulted in the category being corrected (from Malware to Reference-and-Research) but the Risk Level remained High-Risk.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I submitted a second dispute specifically asking for the Risk Level to be reviewed, with supporting evidence including the fact that my domain is now clean at every other major reputation database (Google, VirusTotal, BrightCloud, Symantec, Trellix, IBM X-Force, Kaspersky). The dispute form does not have a Risk Level field - only a category field - and the automated reply confirmed that only the category was reviewed. Risk Level was not addressed. My second submission produced exactly the same outcome as the first: a category response with no comment on the Risk Level despite the explanatory note in the comment field.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I am also a non-customer (volunteer webmaster for a UK registered charity) so the customer support channel is not available to me.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;It would be very useful if a Palo Alto staff member could confirm what the actual process is for requesting Risk Level review when (a) the urlfiltering portal handles only category disputes in practice and (b) the affected domain owner does not have a customer support contract. Without that, it appears there is no functioning route to resolution,a nd we are stuck with a risk factor that was created based on erroneous info from a warning sent by Netcraft in December and which they retracted as an error in under 24 hours.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;Paul Barrett&lt;/P&gt;&lt;P class=""&gt;Volunteer Webmaster,&lt;/P&gt;&lt;P class=""&gt;Berkshire Family History Society&lt;/P&gt;</description>
      <pubDate>Sat, 16 May 2026 16:56:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254133#M6929</guid>
      <dc:creator>paul.barrett</dc:creator>
      <dc:date>2026-05-16T16:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: False positive High-Risk classification for legitimate healthcare SaaS (gmedic.co)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254179#M6930</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1566120575"&gt;@gersonjohan&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="4"&gt;I wanted to follow up and provide an important clarification regarding my previous message.&lt;/P&gt;
&lt;P data-path-to-node="4"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;Upon reviewing our PAN-DB technical documentation, I need to correct a point regarding how risk categories are managed: You cannot manually request a direct change or review for a URL's risk level (High, Medium, or Low Risk).&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;Because risk ratings are determined by dynamic Machine Learning (ML) models that continuously analyze a domain’s behavioral properties, historical data, and ASN/hosting reputation signals, they adapt automatically over time rather than via manual overrides. As noted in your initial message, if the rating is tied to recent ASN or IP reputation shifts, the system must observe a sustained period of benign activity to automatically lower that risk tier.&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;While the risk rating itself cannot be manually adjusted, you &lt;I data-index-in-node="84" data-path-to-node="6"&gt;can&lt;/I&gt; still use the &lt;STRONG data-index-in-node="102" data-path-to-node="6"&gt;&lt;A class="ng-star-inserted" href="https://urlfiltering.paloaltonetworks.com/" rel="noopener" target="_blank"&gt;Palo Alto Networks Test A Site&lt;/A&gt;&lt;/STRONG&gt; portal to verify or request a change to the &lt;STRONG data-index-in-node="177" data-path-to-node="6"&gt;content category&lt;/STRONG&gt; (e.g., ensuring it is strictly categorized under &lt;I data-index-in-node="243" data-path-to-node="6"&gt;Health-and-Medicine&lt;/I&gt;). Keeping the content categorization as accurate as possible helps the ML engine properly contextualize your domain's legitimate traffic patterns.&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;I hope this helps clarify how PAN-DB evaluates dynamic site risk.&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;Sources and additional info:&lt;/P&gt;
&lt;UL&gt;
&lt;LI data-path-to-node="7"&gt;&lt;A href="https://docs.paloaltonetworks.com/advanced-url-filtering/administration/monitoring/request-to-change-the-category-for-a-url" target="_blank"&gt;https://docs.paloaltonetworks.com/advanced-url-filtering/administration/monitoring/request-to-change-the-category-for-a-url&lt;/A&gt;&lt;/LI&gt;
&lt;LI data-path-to-node="7"&gt;&lt;A href="https://docs.paloaltonetworks.com/advanced-url-filtering/administration/url-filtering-basics/url-categories#id82487828-771d-4afb-8582-18eb799e20a7_risk-categories" target="_blank"&gt;https://docs.paloaltonetworks.com/advanced-url-filtering/administration/url-filtering-basics/url-categories#id82487828-771d-4afb-8582-18eb799e20a7_risk-categories&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 08:13:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/false-positive-high-risk-classification-for-legitimate/m-p/1254179#M6930</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2026-05-18T08:13:21Z</dc:date>
    </item>
  </channel>
</rss>

