<?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: URL Filtering - look only at host not URI in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/URL-Filtering-look-only-at-host-not-URI/m-p/140145#M21466</link>
    <description>&lt;P&gt;Without HTTPS Inspection the rest of the URL should be irrelevant.&lt;BR /&gt;With HTTP, it might be worth a TAC case to clarify.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Feb 2022 06:15:25 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2022-02-02T06:15:25Z</dc:date>
    <item>
      <title>URL Filtering - look only at host not URI</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/URL-Filtering-look-only-at-host-not-URI/m-p/139549#M21301</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While doing some logs inspection we found that one of our Custom Application (whitelisting) is in the top trafic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After checking the logs we found that some Web Advertisement are matching this rule to a wrong categorization&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;URL Whitelist contains:&lt;/P&gt;&lt;P&gt;*.example.com&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The logs reported in our report contains this ressource:&lt;/P&gt;&lt;P&gt;&lt;A href="https://c.go-mpulse.net/api/config.json?key=XXXX&amp;amp;d=support.example.com&amp;amp;t=XXXX" target="_self"&gt;https://c.go-mpulse.net/api/config.json?key=XXXX&amp;amp;d=&lt;FONT color="#0000FF"&gt;support.example.com&lt;/FONT&gt;&amp;amp;t=XXXX&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From my understanding this shoul not trigger a hit ??&lt;/P&gt;&lt;P&gt;I decided to follow this SK174194&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;EM&gt;Symptoms&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;EM&gt;The URL partially matches the URL defined in the custom application/Site field&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Example:&lt;BR /&gt;&lt;/STRONG&gt;The custom URL is defined as&amp;nbsp;&lt;STRONG&gt;example.com&amp;nbsp;&lt;/STRONG&gt;and matches URL&amp;nbsp;&lt;STRONG&gt;example.commerce.com&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;EM&gt;Cause&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;EM&gt;When scanning for the URL, the URL must be closed off with a forward slash: "/", otherwise&amp;nbsp;&lt;STRONG&gt;example.com&lt;/STRONG&gt;merce.com will match example.com&lt;/EM&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;EM&gt;Solution&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;EM&gt;Close the URL string with "/" at the end, for the correct match.&amp;nbsp;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Example of the correct definition: "example.com/"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From my understanding this shoul not trigger a hit ??&lt;/P&gt;&lt;P&gt;After implementing the SK a hit to the following URL is still matching&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://c.go-mpulse.net/api/config.json?key=XXXX&amp;amp;d=support.example.com&amp;amp;t=XXXX" target="_self"&gt;https://c.go-mpulse.net/api/config.json?key=XXXX&amp;amp;d=&lt;FONT color="#0000FF"&gt;support.example.com/test&lt;/FONT&gt;&amp;amp;t=XXXX&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the correct implementation to only filter:&lt;/P&gt;&lt;P&gt;http(s)://support.example.com/ or&amp;nbsp;http(s)://example.com/ if possible without Regex as HTTPS inspection is not enabled for all profiles&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 26 Jan 2022 10:08:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/URL-Filtering-look-only-at-host-not-URI/m-p/139549#M21301</guid>
      <dc:creator>CP-NDA</dc:creator>
      <dc:date>2022-01-26T10:08:00Z</dc:date>
    </item>
    <item>
      <title>Re: URL Filtering - look only at host not URI</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/URL-Filtering-look-only-at-host-not-URI/m-p/140145#M21466</link>
      <description>&lt;P&gt;Without HTTPS Inspection the rest of the URL should be irrelevant.&lt;BR /&gt;With HTTP, it might be worth a TAC case to clarify.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Feb 2022 06:15:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/URL-Filtering-look-only-at-host-not-URI/m-p/140145#M21466</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-02-02T06:15:25Z</dc:date>
    </item>
  </channel>
</rss>

