<?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 good Practice in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777128#M494404</link>
    <description>&lt;P&gt;Need good practice advice &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a good practice to control traffic coming from internal to the outside, like allowing only http and https by using access rules on the inside interface ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:44:51 GMT</pubDate>
    <dc:creator>Jean-Francois Gagnon</dc:creator>
    <dc:date>2019-03-11T21:44:51Z</dc:date>
    <item>
      <title>Asa good Practice</title>
      <link>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777128#M494404</link>
      <description>&lt;P&gt;Need good practice advice &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a good practice to control traffic coming from internal to the outside, like allowing only http and https by using access rules on the inside interface ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:44:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777128#M494404</guid>
      <dc:creator>Jean-Francois Gagnon</dc:creator>
      <dc:date>2019-03-11T21:44:51Z</dc:date>
    </item>
    <item>
      <title>Asa good Practice</title>
      <link>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777129#M494406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nope, as far as I know there is no document, but by default, the ASA will permit everything from inside going to outside (and the return traffic for the connection), but nothing from outside going to inside. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since every company have different security policies, there is no way to create an standard of what is allowed and what not. There are some special RFCs that talk about special IP addresses that need to be blocked, but as far as I know, nothing that Cisco have created. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Nov 2011 01:37:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777129#M494406</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-11-01T01:37:20Z</dc:date>
    </item>
    <item>
      <title>Asa good Practice</title>
      <link>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777130#M494407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A more restrictive security posture is 'ALWAYS' good practice! The only thing you have to keep in mind, is if you internet gateway (in this case your ASA) is used for connections from your internal networks need to communicate directly with other hosts in the cloud you will need to poke holes for that traffic as well. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Nov 2011 14:45:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-good-practice/m-p/1777130#M494407</guid>
      <dc:creator>caseth0102</dc:creator>
      <dc:date>2011-11-02T14:45:56Z</dc:date>
    </item>
  </channel>
</rss>

