<?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 Control Internal Network Traffic Based on URL Paths, Subdomains and so on in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Control-Internal-Network-Traffic-Based-on-URL-Paths-Subdomains/m-p/107222#M14358</link>
    <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;Is it possible to control internal! client-to-server network traffic based on URLs, URL Paths, subdomains and similar goodies?&lt;/P&gt;&lt;P&gt;I mean for example &lt;A href="http://mydomain/mysite" target="_blank"&gt;http://mydomain/mysite&lt;/A&gt;&amp;nbsp;vs. &lt;A href="http://mydomain/yoursite" target="_blank"&gt;http://mydomain/yoursite&lt;/A&gt;&amp;nbsp;or &lt;A href="http://mysite.mydomain" target="_blank"&gt;http://mysite.mydomain&lt;/A&gt;&amp;nbsp;vs. &lt;A href="http://yoursite.mydomain" target="_blank"&gt;http://yoursite.mydomain&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I'm not so familiar with firewalls' database access control capabilities in general - does CP have this kind of capability? I mean control network traffic to X instance of a DB and allow the traffic flow there, but deny to the same DB's Y instance.&lt;/P&gt;&lt;P&gt;Thank you in advance for your reply,&lt;/P&gt;&lt;P&gt;BoGa&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jan 2021 14:11:35 GMT</pubDate>
    <dc:creator>BoGa</dc:creator>
    <dc:date>2021-01-07T14:11:35Z</dc:date>
    <item>
      <title>Control Internal Network Traffic Based on URL Paths, Subdomains and so on</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Control-Internal-Network-Traffic-Based-on-URL-Paths-Subdomains/m-p/107222#M14358</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;Is it possible to control internal! client-to-server network traffic based on URLs, URL Paths, subdomains and similar goodies?&lt;/P&gt;&lt;P&gt;I mean for example &lt;A href="http://mydomain/mysite" target="_blank"&gt;http://mydomain/mysite&lt;/A&gt;&amp;nbsp;vs. &lt;A href="http://mydomain/yoursite" target="_blank"&gt;http://mydomain/yoursite&lt;/A&gt;&amp;nbsp;or &lt;A href="http://mysite.mydomain" target="_blank"&gt;http://mysite.mydomain&lt;/A&gt;&amp;nbsp;vs. &lt;A href="http://yoursite.mydomain" target="_blank"&gt;http://yoursite.mydomain&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I'm not so familiar with firewalls' database access control capabilities in general - does CP have this kind of capability? I mean control network traffic to X instance of a DB and allow the traffic flow there, but deny to the same DB's Y instance.&lt;/P&gt;&lt;P&gt;Thank you in advance for your reply,&lt;/P&gt;&lt;P&gt;BoGa&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 14:11:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Control-Internal-Network-Traffic-Based-on-URL-Paths-Subdomains/m-p/107222#M14358</guid>
      <dc:creator>BoGa</dc:creator>
      <dc:date>2021-01-07T14:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: Control Internal Network Traffic Based on URL Paths, Subdomains and so on</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Control-Internal-Network-Traffic-Based-on-URL-Paths-Subdomains/m-p/107330#M14367</link>
      <description>&lt;P&gt;You can do full URLs as custom application/sites, yes.&lt;BR /&gt;For https URLs you will need to enable HTTPS Inspection.&lt;/P&gt;</description>
      <pubDate>Sat, 09 Jan 2021 00:31:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Control-Internal-Network-Traffic-Based-on-URL-Paths-Subdomains/m-p/107330#M14367</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-01-09T00:31:54Z</dc:date>
    </item>
  </channel>
</rss>

