<?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: Using PA-3220 for URL filtering to replace Barracuda Web Filter in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/using-pa-3220-for-url-filtering-to-replace-barracuda-web-filter/m-p/434035#M95939</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/193646"&gt;@NormGala&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only thing that really changes is that you would want to install the terminal server agent so that the user-id information actually maps correctly for those users. Outside of that, there isn't anything special about the deployment from that aspect.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would recommend that you look into the feature set available on the firewall for url-filtering versus what you are using on the Barracuda web filter. It's been a while since I've actually had to manage one, but if memory serves correctly you could allow time limits for categories, log actual social media posts, and stuff like that. IE: Check to ensure that you don't use any features that aren't available through url-filtering directly on the firewall.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 15 Sep 2021 03:29:16 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2021-09-15T03:29:16Z</dc:date>
    <item>
      <title>Using PA-3220 for URL filtering to replace Barracuda Web Filter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-pa-3220-for-url-filtering-to-replace-barracuda-web-filter/m-p/433829#M95923</link>
      <description>&lt;P&gt;We just got our PA-3220 and hoping to use that for our URL/Web filtering and discontinue our Barracuda Web filter.&amp;nbsp; Has anyone implemented the URL filtering with terminal server users?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2021 15:24:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-pa-3220-for-url-filtering-to-replace-barracuda-web-filter/m-p/433829#M95923</guid>
      <dc:creator>NormGala</dc:creator>
      <dc:date>2021-09-14T15:24:39Z</dc:date>
    </item>
    <item>
      <title>Re: Using PA-3220 for URL filtering to replace Barracuda Web Filter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-pa-3220-for-url-filtering-to-replace-barracuda-web-filter/m-p/434035#M95939</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/193646"&gt;@NormGala&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only thing that really changes is that you would want to install the terminal server agent so that the user-id information actually maps correctly for those users. Outside of that, there isn't anything special about the deployment from that aspect.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would recommend that you look into the feature set available on the firewall for url-filtering versus what you are using on the Barracuda web filter. It's been a while since I've actually had to manage one, but if memory serves correctly you could allow time limits for categories, log actual social media posts, and stuff like that. IE: Check to ensure that you don't use any features that aren't available through url-filtering directly on the firewall.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Sep 2021 03:29:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-pa-3220-for-url-filtering-to-replace-barracuda-web-filter/m-p/434035#M95939</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-09-15T03:29:16Z</dc:date>
    </item>
  </channel>
</rss>

