<?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 Thanks, Thats what I thought. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061994#M145221</link>
    <description>&lt;P&gt;Thanks, Thats what I thought...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Comparing to other vendors, like PAN and Fortinet, their setup is using security profile (such web filter profile) to control the content blocking even the access control which has the profile associated is set to allow.&lt;/P&gt;
&lt;P&gt;The ASA/SFR way is not much more labor effort but just different I guess...&lt;/P&gt;</description>
    <pubDate>Mon, 03 Apr 2017 16:31:44 GMT</pubDate>
    <dc:creator>SIMMN</dc:creator>
    <dc:date>2017-04-03T16:31:44Z</dc:date>
    <item>
      <title>Firepower URL access rule question</title>
      <link>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061992#M145212</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Within FMC, if you setup a access control rule, you define the action to be allowed or deny etc. Then define the matching criteria, like network and/or services. But one question regarding the URL portion: if the action set to Allow for the rule, then what categories of URL to be selected, the permitted categories OR blocked ones?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Say, I want to allow LAN end-user web traffic outbound, but I want to block access to URL categories: Porn and Illegible... So can I do this in one rule OR I have to do two rules: one just to block those URL categories and second rule to allow web traffic?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 09:10:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061992#M145212</guid>
      <dc:creator>SIMMN</dc:creator>
      <dc:date>2019-03-12T09:10:04Z</dc:date>
    </item>
    <item>
      <title>Make a rule with action</title>
      <link>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061993#M145215</link>
      <description>&lt;P&gt;Make a rule with action "block" and the URL categories you wish to block. Follow it with an allow for other traffic. Just like in an ASA, the rules are evaluated from the top down and first match ends the ACP (Access Control Policy) rule processing.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2017 15:31:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061993#M145215</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-04-03T15:31:59Z</dc:date>
    </item>
    <item>
      <title>Thanks, Thats what I thought.</title>
      <link>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061994#M145221</link>
      <description>&lt;P&gt;Thanks, Thats what I thought...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Comparing to other vendors, like PAN and Fortinet, their setup is using security profile (such web filter profile) to control the content blocking even the access control which has the profile associated is set to allow.&lt;/P&gt;
&lt;P&gt;The ASA/SFR way is not much more labor effort but just different I guess...&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2017 16:31:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-url-access-rule-question/m-p/3061994#M145221</guid>
      <dc:creator>SIMMN</dc:creator>
      <dc:date>2017-04-03T16:31:44Z</dc:date>
    </item>
  </channel>
</rss>

