<?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: Pix 506 E in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-506-e/m-p/732250#M1001630</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apply an access-list to the inside interface. Say you only want to allow http, ftp and https outbound you would do something like the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp any any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp any any eq 443&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp any any eq 21&lt;/P&gt;&lt;P&gt;access-group acl_inside in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would review what traffic you want allowed outbound then apply the access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you want to make additions to your ACL down the road, say you forgot to allow DNS from your internal network, you then just add the new ACL. (You want to allow DNS in your initial access-list)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_inside permit udp any any eq 53&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 22 Jul 2007 13:35:52 GMT</pubDate>
    <dc:creator>JBDanford2002</dc:creator>
    <dc:date>2007-07-22T13:35:52Z</dc:date>
    <item>
      <title>Pix 506 E</title>
      <link>https://community.cisco.com/t5/network-security/pix-506-e/m-p/732249#M1001629</link>
      <description>&lt;P&gt;How do I block outbound traffic?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:47:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506-e/m-p/732249#M1001629</guid>
      <dc:creator>wazzaclarke</dc:creator>
      <dc:date>2019-03-11T10:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: Pix 506 E</title>
      <link>https://community.cisco.com/t5/network-security/pix-506-e/m-p/732250#M1001630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apply an access-list to the inside interface. Say you only want to allow http, ftp and https outbound you would do something like the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp any any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp any any eq 443&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp any any eq 21&lt;/P&gt;&lt;P&gt;access-group acl_inside in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would review what traffic you want allowed outbound then apply the access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you want to make additions to your ACL down the road, say you forgot to allow DNS from your internal network, you then just add the new ACL. (You want to allow DNS in your initial access-list)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_inside permit udp any any eq 53&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Jul 2007 13:35:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506-e/m-p/732250#M1001630</guid>
      <dc:creator>JBDanford2002</dc:creator>
      <dc:date>2007-07-22T13:35:52Z</dc:date>
    </item>
  </channel>
</rss>

