<?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 ACL bypass doubt in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780809#M493545</link>
    <description>&lt;P&gt;Hi, all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a doubt about firewall interface ACL bypass, I understand stand that when traffic is initiated from inside to an outside server, the firewall will create a flow entry and bypass ACL check on outside interface, how about the other way around? if the traffic is initated from outside (traffic explicitly allowed on outside ACL), but inside access-list is not explicitly allowing this traffic, will the connection be established?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:49:21 GMT</pubDate>
    <dc:creator>oldcreek12</dc:creator>
    <dc:date>2019-03-11T21:49:21Z</dc:date>
    <item>
      <title>Firewall ACL bypass doubt</title>
      <link>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780809#M493545</link>
      <description>&lt;P&gt;Hi, all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a doubt about firewall interface ACL bypass, I understand stand that when traffic is initiated from inside to an outside server, the firewall will create a flow entry and bypass ACL check on outside interface, how about the other way around? if the traffic is initated from outside (traffic explicitly allowed on outside ACL), but inside access-list is not explicitly allowing this traffic, will the connection be established?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:49:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780809#M493545</guid>
      <dc:creator>oldcreek12</dc:creator>
      <dc:date>2019-03-11T21:49:21Z</dc:date>
    </item>
    <item>
      <title>Firewall ACL bypass doubt</title>
      <link>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780810#M493546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it would be allowed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Nov 2011 19:57:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780810#M493546</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2011-11-11T19:57:17Z</dc:date>
    </item>
    <item>
      <title>Firewall ACL bypass doubt</title>
      <link>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780811#M493547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, that is what I thought so, I have inside ACL did not explict allow traffic to remote access SSL-VPN address pool, since remote-access VPN traffic is always initiated from client, this worked fine. But we are having strange behavior when Cisco Desktop Agent is running on SSL VPN client laptop, the agent can not see other agents, I suspected that CDA is using some ports that are not recognized to ASA, so I added inside ACL to explictly allow any IP traffic to remote SSL-VPN address pool IPs, that fixed the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Nov 2011 20:09:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-acl-bypass-doubt/m-p/1780811#M493547</guid>
      <dc:creator>oldcreek12</dc:creator>
      <dc:date>2011-11-11T20:09:38Z</dc:date>
    </item>
  </channel>
</rss>

