<?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 Firewall Help! in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-help/m-p/2543619#M237193</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm newbie on the firewall policy configuration. As far as I know, the policy configuration always need to allow both ways. Exm allows services Port1 --&amp;gt; Port2, Port2 --&amp;gt; Port1 in order for both to communication. I've noticed the policy on the internal to wan is always a single policy and it works both way too as from the internal able to reach internet after the nat and flow back to internal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pls advise would be greatly appreciated. Many thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 04:23:00 GMT</pubDate>
    <dc:creator>wayne loh</dc:creator>
    <dc:date>2019-03-12T04:23:00Z</dc:date>
    <item>
      <title>Firewall Help!</title>
      <link>https://community.cisco.com/t5/network-security/firewall-help/m-p/2543619#M237193</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm newbie on the firewall policy configuration. As far as I know, the policy configuration always need to allow both ways. Exm allows services Port1 --&amp;gt; Port2, Port2 --&amp;gt; Port1 in order for both to communication. I've noticed the policy on the internal to wan is always a single policy and it works both way too as from the internal able to reach internet after the nat and flow back to internal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pls advise would be greatly appreciated. Many thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:23:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-help/m-p/2543619#M237193</guid>
      <dc:creator>wayne loh</dc:creator>
      <dc:date>2019-03-12T04:23:00Z</dc:date>
    </item>
    <item>
      <title>For a stateful firewall (such</title>
      <link>https://community.cisco.com/t5/network-security/firewall-help/m-p/2543620#M237194</link>
      <description>&lt;P&gt;For a stateful firewall (such as the Cisco ASA), it keeps track of tcp connections (and udp flows) in its connection table. When traffic is returning in response to an internally-initiated communication, that table finds a connection record and allows the return traffic to transit without requiring matching an access-list.&lt;/P&gt;&lt;P&gt;Only when traffic is initiated from outside does it need an explicit access-list to be allowed into the inside (or other interfaces of higher security level than outside).&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jun 2014 14:43:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-help/m-p/2543620#M237194</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-06-25T14:43:19Z</dc:date>
    </item>
  </channel>
</rss>

