<?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 ASA Content Security in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630637#M422755</link>
    <description>&lt;P&gt;Hay there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I setup a ASA FW with Trend Micro Content Security. When I add an URL to the block list I can still open it from the PCs which use the ASA as the gateway?! What did I forget?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 09:17:45 GMT</pubDate>
    <dc:creator>larsdominic</dc:creator>
    <dc:date>2020-02-21T09:17:45Z</dc:date>
    <item>
      <title>ASA Content Security</title>
      <link>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630637#M422755</link>
      <description>&lt;P&gt;Hay there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I setup a ASA FW with Trend Micro Content Security. When I add an URL to the block list I can still open it from the PCs which use the ASA as the gateway?! What did I forget?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:17:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630637#M422755</guid>
      <dc:creator>larsdominic</dc:creator>
      <dc:date>2020-02-21T09:17:45Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Content Security</title>
      <link>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630638#M422756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The access list configured for URL coookies is not working.&lt;/P&gt;&lt;P&gt;The URL filtering features presented in this chapter allow the Content Engine to control client access to websites in any of the following ways:&lt;/P&gt;&lt;P&gt;    Deny access to URLs specified in a list.&lt;/P&gt;&lt;P&gt;    Permit access only to URLs specified in a list.&lt;/P&gt;&lt;P&gt;    Direct traffic to a N2H2 server for filtering.&lt;/P&gt;&lt;P&gt;    Direct traffic to a Websense enterprise server for filtering&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/conntsw/ps491/products_configuration_guide_chapter09186a008008123b.html#98891" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/conntsw/ps491/products_configuration_guide_chapter09186a008008123b.html#98891&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2006 22:08:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630638#M422756</guid>
      <dc:creator>s.jankowski</dc:creator>
      <dc:date>2006-11-14T22:08:58Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Content Security</title>
      <link>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630639#M422757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CSC-SSM modules use service policies to redirect traffic to the module for processing.    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is an example of what I do...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The inside_mpc is matching only inside traffic destined for web, ftp, pop3 and smtp.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The outside_mpc is matching traffic going to the internal servers (using the outside public addresses) matching  pop3 and smtp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then, I build inside and outside classes matching traffic off of the ACL and sending it to the CSC module with the csc fail-open or csc fail-close command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--Gavin Budd&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_mpc extended permit tcp 10.0.0.0 255.0.0.0 any eq pop3 &lt;/P&gt;&lt;P&gt;access-list inside_mpc extended permit tcp 10.0.0.0 255.0.0.0 any eq www &lt;/P&gt;&lt;P&gt;access-list inside_mpc extended permit tcp 10.0.0.0 255.0.0.0 any eq ftp &lt;/P&gt;&lt;P&gt;access-list inside_mpc extended permit tcp 10.0.0.0 255.0.0.0 any eq https &lt;/P&gt;&lt;P&gt;access-list inside_mpc extended permit tcp 10.0.0.0 255.0.0.0 any eq smtp &lt;/P&gt;&lt;P&gt;access-list outside_mpc extended permit tcp any x.x.25.0 255.255.255.0 eq pop3 &lt;/P&gt;&lt;P&gt;access-list outside_mpc extended permit tcp any x.x.25.0 255.255.255.0 eq smtp &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map inside-class&lt;/P&gt;&lt;P&gt; match access-list inside_mpc&lt;/P&gt;&lt;P&gt;class-map outside-class&lt;/P&gt;&lt;P&gt; match access-list outside_mpc&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;policy-map outside-policy&lt;/P&gt;&lt;P&gt; class outside-class&lt;/P&gt;&lt;P&gt;  csc fail-open&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map inside-policy&lt;/P&gt;&lt;P&gt; class inside-class&lt;/P&gt;&lt;P&gt;  csc fail-open&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;service-policy outside-policy interface outside&lt;/P&gt;&lt;P&gt;service-policy inside-policy interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2006 23:24:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-content-security/m-p/630639#M422757</guid>
      <dc:creator>gbudd12345</dc:creator>
      <dc:date>2006-11-14T23:24:45Z</dc:date>
    </item>
  </channel>
</rss>

