<?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: Prevent clients bypassing proxy in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435190#M633591</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;Access list on the inside interface is the easiest and best way to do it. In&lt;/P&gt;&lt;P&gt;addition, you can also control it via NAT. Here is a sample config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-list inside_access_out permit tcp host  any eq 443&lt;/P&gt;&lt;P&gt;Access-list inside_access_out deny tcp any any eq 80&lt;/P&gt;&lt;P&gt;Access-list inside_access_out deny tcp any any eq 443&lt;/P&gt;&lt;P&gt;Access-list inside_access_out permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-group inside_access_out in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Global (outside) 1 interface&lt;/P&gt;&lt;P&gt;Nat (inside) 1 &lt;PROXY servers="" ip=""&gt;&lt;/PROXY&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure that except for the servers that need direct internet access, no&lt;/P&gt;&lt;P&gt;other host has a NAT rule on the firewall. In that way, even if the hosts&lt;/P&gt;&lt;P&gt;try to bypass the access-list rule, they will not be able to go out without&lt;/P&gt;&lt;P&gt;the NAT rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&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;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Jul 2010 14:35:58 GMT</pubDate>
    <dc:creator>Nagaraja Thanthry</dc:creator>
    <dc:date>2010-07-13T14:35:58Z</dc:date>
    <item>
      <title>Prevent clients bypassing proxy</title>
      <link>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435189#M633576</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if someone could help me out with a issue I have.&amp;nbsp; At present our corporation has all internet traffic routed via our HQ, through a Cisco ASA 5510 arrangement.&amp;nbsp; I need to prevent client machines (subnet / range) going directly out onto the internet, I need them to go via a proxy server.&amp;nbsp; My thought was to put a deny ACL on the outbound internal interface.&amp;nbsp; This would be something like deny ip [ip address] [subnet] interface outside with a permit rule for the proxy address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any suggestions, or ideas as to how I could do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:10:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435189#M633576</guid>
      <dc:creator>chriwall01</dc:creator>
      <dc:date>2019-03-11T18:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent clients bypassing proxy</title>
      <link>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435190#M633591</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;Access list on the inside interface is the easiest and best way to do it. In&lt;/P&gt;&lt;P&gt;addition, you can also control it via NAT. Here is a sample config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-list inside_access_out permit tcp host  any eq 443&lt;/P&gt;&lt;P&gt;Access-list inside_access_out deny tcp any any eq 80&lt;/P&gt;&lt;P&gt;Access-list inside_access_out deny tcp any any eq 443&lt;/P&gt;&lt;P&gt;Access-list inside_access_out permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-group inside_access_out in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Global (outside) 1 interface&lt;/P&gt;&lt;P&gt;Nat (inside) 1 &lt;PROXY servers="" ip=""&gt;&lt;/PROXY&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure that except for the servers that need direct internet access, no&lt;/P&gt;&lt;P&gt;other host has a NAT rule on the firewall. In that way, even if the hosts&lt;/P&gt;&lt;P&gt;try to bypass the access-list rule, they will not be able to go out without&lt;/P&gt;&lt;P&gt;the NAT rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&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;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Jul 2010 14:35:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435190#M633591</guid>
      <dc:creator>Nagaraja Thanthry</dc:creator>
      <dc:date>2010-07-13T14:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent clients bypassing proxy</title>
      <link>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435191#M633617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi NT,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the quick reply.&amp;nbsp; I'll give it ago and let you know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One afterthought though, would i need to specifically need to allow the internal IP's access to the DMZ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once again, thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Jul 2010 14:45:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/prevent-clients-bypassing-proxy/m-p/1435191#M633617</guid>
      <dc:creator>chriwall01</dc:creator>
      <dc:date>2010-07-13T14:45:54Z</dc:date>
    </item>
  </channel>
</rss>

