<?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: ACL question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996729#M918101</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modular policy framework allow you to do that.&lt;/P&gt;&lt;P&gt;Please check the document below at the section HTTP inspection policy map&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/asacfg72.pdf" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/asacfg72.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jun 2008 13:22:32 GMT</pubDate>
    <dc:creator>Amadou TOURE</dc:creator>
    <dc:date>2008-06-19T13:22:32Z</dc:date>
    <item>
      <title>ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996726#M918098</link>
      <description>&lt;P&gt;How do I create an ACL that would only allow specific sites to go through if I didn't know the IP and only know the DNS name.  Say I want to allow only these two sites *.cisco.com and *.yahoo.com then block all others.  Can I do that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is on an ASA 5510.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:01:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996726#M918098</guid>
      <dc:creator>ericluoma</dc:creator>
      <dc:date>2019-03-11T13:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996727#M918099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AFAIK this is not supported on the ASA/PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 12:33:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996727#M918099</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-19T12:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996728#M918100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;url filtering possible in ASA using Cisco ASA 5500 Series Content Security Edition.&lt;/P&gt;&lt;P&gt;pls go thru this link.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/prod/collateral/vpndevc/ps6032/ps6094/ps6120/prod_brochure0900aecd80402e88.html" target="_blank"&gt;http://www.cisco.com/en/US/prod/collateral/vpndevc/ps6032/ps6094/ps6120/prod_brochure0900aecd80402e88.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 13:20:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996728#M918100</guid>
      <dc:creator>rangaswamy.gb</dc:creator>
      <dc:date>2008-06-19T13:20:25Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996729#M918101</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modular policy framework allow you to do that.&lt;/P&gt;&lt;P&gt;Please check the document below at the section HTTP inspection policy map&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/asacfg72.pdf" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/asacfg72.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 13:22:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996729#M918101</guid>
      <dc:creator>Amadou TOURE</dc:creator>
      <dc:date>2008-06-19T13:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996730#M918102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;amadoutoure, how does MPF achive that? Can you expand upon your comment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How will MPF keep track of the DNS entry of cisco.com (which say changes frequently).&lt;/P&gt;&lt;P&gt;Ever did a nslookup on google.com (you get multiple IPs)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We do this on one of our Customer's Netscreen ISG tough, it supports this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 15:42:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996730#M918102</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-19T15:42:02Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996731#M918103</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm out of office for now and I'll send a sample config as soon as I go back to office.&lt;/P&gt;&lt;P&gt;It will be done using regex syntax.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 16:04:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996731#M918103</guid>
      <dc:creator>Amadou TOURE</dc:creator>
      <dc:date>2008-06-19T16:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996732#M918104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Oh I get your point now. Thanks for waking me up now. Even tough its not as flexible as a proper filtering solution (because since we are denying based on hostname, the user can simply open the URL by IP, open google's cache etc.):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type inspect http TEST_HTTP&lt;/P&gt;&lt;P&gt; parameters&lt;/P&gt;&lt;P&gt; match request uri regex cisco.com&lt;/P&gt;&lt;P&gt;.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Something like this:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.internetworkpro.org/wiki/ASA_and_PIX_using_http_inspection_to_filter_URLs_and_Hosts_in_HTTP" target="_blank"&gt;http://www.internetworkpro.org/wiki/ASA_and_PIX_using_http_inspection_to_filter_URLs_and_Hosts_in_HTTP&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 16:19:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996732#M918104</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-19T16:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: ACL question</title>
      <link>https://community.cisco.com/t5/network-security/acl-question/m-p/996733#M918105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Right it's something like that... you have a very good point with accessing directly with IP address in URL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But you could filter by content-type and application header and aslo deny accessing with IP address in url.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/asa-8x-regex-config.html" target="_blank"&gt;http://www.cisco.com/warp/public/110/asa-8x-regex-config.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However you're definitely right that it's not the finest way to filter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 16:41:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-question/m-p/996733#M918105</guid>
      <dc:creator>Amadou TOURE</dc:creator>
      <dc:date>2008-06-19T16:41:52Z</dc:date>
    </item>
  </channel>
</rss>

