<?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: Locking outbound connection on PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287732#M594537</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Add this to your configuration as dns can use either protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside, outside) &lt;GLOBAL_IP&gt; &lt;LOCAL_IP&gt; netmask 255.255.255.255 0 0 &lt;/LOCAL_IP&gt;&lt;/GLOBAL_IP&gt;&lt;/P&gt;&lt;P&gt;access-list acc-in permit udp host &lt;DNS_LOCAL_IP&gt; any eq domain&lt;/DNS_LOCAL_IP&gt;&lt;/P&gt;&lt;P&gt;access-list acc-out permit udp any host &lt;DNS_GLOBAL_IP&gt; eq domain&lt;/DNS_GLOBAL_IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its advisable locating this dns server in your DMZ. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Feb 2004 21:48:02 GMT</pubDate>
    <dc:creator>laje</dc:creator>
    <dc:date>2004-02-24T21:48:02Z</dc:date>
    <item>
      <title>Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287722#M594481</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please advise on how to limit our Outbound connection only letting network users to access HTTP and servers SMTP, DNS etc...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're currently using PIX515 with the latest sotware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:14:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287722#M594481</guid>
      <dc:creator>support</dc:creator>
      <dc:date>2020-02-21T07:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287723#M594484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you may configure access list and apply that onto the inside interface of the pix. eg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l xxx permit tcp &lt;USER ip=""&gt; any eq http&lt;/USER&gt;&lt;/P&gt;&lt;P&gt;access-l xxx permit tcp &lt;USER ip=""&gt; any eq smtp&lt;/USER&gt;&lt;/P&gt;&lt;P&gt;access-g xxx in inter inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one thing should be noticed is that everything else will be blocked. the way i would suggest is to block user ip range only. in that case you, as an admin, plus servers will still have full access. if you think so,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l xxx permit tcp &lt;USER ip=""&gt; any eq http&lt;/USER&gt;&lt;/P&gt;&lt;P&gt;access-l xxx permit tcp &lt;USER ip=""&gt; any eq smtp&lt;/USER&gt;&lt;/P&gt;&lt;P&gt;access-l xxx deny ip &lt;USER ip=""&gt; any&lt;/USER&gt;&lt;/P&gt;&lt;P&gt;access-l xxx permit ip &lt;LAN ip=""&gt; any&lt;/LAN&gt;&lt;/P&gt;&lt;P&gt;access-g xxx in inter inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Feb 2004 23:55:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287723#M594484</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2004-02-17T23:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287724#M594486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;cheers jackko for the reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but how do i apply this if i have 10.0.0.10 to 20 for the Servers and 10.0.0.20 to 50 Users?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Feb 2004 14:57:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287724#M594486</guid>
      <dc:creator>support</dc:creator>
      <dc:date>2004-02-18T14:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287725#M594487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you can use 'object-group' command. create a network group and add all the user ip into the group. then create access list using the group name rather than ip address. you may also want to re-configure the dhcp pool into proper subnet, as the command doesn't support ip address range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/mr.htm#1038172" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/mr.htm#1038172&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Feb 2004 21:11:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287725#M594487</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2004-02-19T21:11:04Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287726#M594489</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks i've read that on the docs. im considering using object group. definitely!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;btw with all the virus and trojan going around. would it be posible to start blocking all the ports first then open all those are necessary :-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l block deny ip any any &lt;/P&gt;&lt;P&gt;access-l block permit tcp host &lt;MY ip=""&gt; any eq www&lt;/MY&gt;&lt;/P&gt;&lt;P&gt;access-g block in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i tried doing that but my i still cant browse the web. i have a local DNS server on our network i tried adding&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l block permit tcp host &amp;lt;192.168.0.x&amp;gt; any eq 53&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;still no joy. any ideas? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks again!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Feb 2004 18:58:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287726#M594489</guid>
      <dc:creator>support</dc:creator>
      <dc:date>2004-02-20T18:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287727#M594492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Once a match is made the pix does not compare it to the rest of the access-list. It just drops the packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an implicit deny all at the end of each access-list, so simply open the ones you want, and the rest will be blocked.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Feb 2004 06:11:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287727#M594492</guid>
      <dc:creator>jdepies</dc:creator>
      <dc:date>2004-02-21T06:11:04Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287728#M594506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the access list order is important as the pix checks it from the top to the bottom. ie. the first one you put in there is to deny all traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;simply re-order the access list and it should work. btw you don't really need to have 'deny ip any any' as it is the default statement at the end of all access list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l block permit tcp host &lt;MY ip=""&gt; any eq www &lt;/MY&gt;&lt;/P&gt;&lt;P&gt;access-l block deny ip any any &lt;/P&gt;&lt;P&gt;access-g block in interface inside &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Feb 2004 23:34:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287728#M594506</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2004-02-22T23:34:07Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287729#M594513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;great! but how come when i did that, i cant browse the web even though i've allowed my ip for www.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i've also noticed, my internal dns is not resolving anymore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there anything missing or need to do?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Feb 2004 21:07:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287729#M594513</guid>
      <dc:creator>support</dc:creator>
      <dc:date>2004-02-23T21:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287730#M594524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you need to add another access list for the dns. remember to put it above the 'deny any any'&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2004 07:18:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287730#M594524</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2004-02-24T07:18:14Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287731#M594532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;still no joy! i cant browse the web nor resolve any ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acc-out permit tcp any host &lt;EXTERNAL ip=""&gt; eq 53&lt;/EXTERNAL&gt;&lt;/P&gt;&lt;P&gt;access-list acc-in permit tcp host &lt;DNS internal="" ip=""&gt; eq   53&lt;/DNS&gt;&lt;/P&gt;&lt;P&gt;access-list acc-in permit tcp host &lt;MY ip=""&gt; any eq 80&lt;/MY&gt;&lt;/P&gt;&lt;P&gt;access-list acc-in deny ip any any  &lt;/P&gt;&lt;P&gt;static (inside,outside) &lt;EXTERNAL ip=""&gt; &lt;DNS internal="" ip=""&gt; netmask 255.255.255.255 0 0&lt;/DNS&gt;&lt;/EXTERNAL&gt;&lt;/P&gt;&lt;P&gt;access-group acc-out in interface outside&lt;/P&gt;&lt;P&gt;access-group acc-in in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;am i missing anything on my config?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks alot!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2004 20:11:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287731#M594532</guid>
      <dc:creator>support</dc:creator>
      <dc:date>2004-02-24T20:11:17Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287732#M594537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Add this to your configuration as dns can use either protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside, outside) &lt;GLOBAL_IP&gt; &lt;LOCAL_IP&gt; netmask 255.255.255.255 0 0 &lt;/LOCAL_IP&gt;&lt;/GLOBAL_IP&gt;&lt;/P&gt;&lt;P&gt;access-list acc-in permit udp host &lt;DNS_LOCAL_IP&gt; any eq domain&lt;/DNS_LOCAL_IP&gt;&lt;/P&gt;&lt;P&gt;access-list acc-out permit udp any host &lt;DNS_GLOBAL_IP&gt; eq domain&lt;/DNS_GLOBAL_IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its advisable locating this dns server in your DMZ. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2004 21:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287732#M594537</guid>
      <dc:creator>laje</dc:creator>
      <dc:date>2004-02-24T21:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: Locking outbound connection on PIX</title>
      <link>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287733#M594542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey guys! Thanks for all your help! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Everything seems to be locked down. I can sleep at night now!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Mar 2004 17:57:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-outbound-connection-on-pix/m-p/287733#M594542</guid>
      <dc:creator>support</dc:creator>
      <dc:date>2004-03-10T17:57:33Z</dc:date>
    </item>
  </channel>
</rss>

