<?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: Pro/Con IPSEC tunnels through Firewalls in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pro-con-ipsec-tunnels-through-firewalls/m-p/3216076#M1064962</link>
    <description>&lt;P&gt;One benefit is that you have an additional control what traffic reaches your VPN-gateway. If your VPN-device has a vulnerability on an default open port, the filerwall that only lets through the needed VPN-traffic will be an effective countermeasure. But at least for IPSec, a stateless ACL will be enough, a statefull firewall is not really needed.&lt;/P&gt;
&lt;P&gt;Personally, I often accept to have my VPN-gateway directly connected to the internet. But it‘s always important to have some device-hardening in place.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Nov 2017 06:10:15 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2017-11-14T06:10:15Z</dc:date>
    <item>
      <title>Pro/Con IPSEC tunnels through Firewalls</title>
      <link>https://community.cisco.com/t5/network-security/pro-con-ipsec-tunnels-through-firewalls/m-p/3215986#M1064961</link>
      <description>&lt;P&gt;I've found myself in an interesting spot where I preparing to debate with my info security team the merits of continuing to push IPSEC and SSL VPN connections through a stateful firewall. Now my feedback on this design is why? What benefit do you gain by having your IPSEC/SSL traffic inspected by a stateful firewall? Vs. having your VPN device face the public Internet? In my view, passing this traffic through a stateful FW just creates additional and unnecessary overhead (From inspection and NAT processing) which adds delay (Latency). Aside for this, why would you inspect encrypted traffic? Does not compute!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyhow to prepare for this debate I was just search the web and looking for some article, blog, design guide, or any feedback on this topic and did not find any source material on this subject.&lt;/P&gt;
&lt;P&gt;So, in a nutshell, I'm looking for your insights on this subject, should I support this practice or should I stick with what I know works? My gut tells me to swim away from such a design and just place your IPSEC and SSL SSL terminating devices, like an ASA/ISR/ASR&amp;nbsp; device on the edge.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As always, your feedback is appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:44:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pro-con-ipsec-tunnels-through-firewalls/m-p/3215986#M1064961</guid>
      <dc:creator>Professor_Pickles</dc:creator>
      <dc:date>2020-02-21T14:44:34Z</dc:date>
    </item>
    <item>
      <title>Re: Pro/Con IPSEC tunnels through Firewalls</title>
      <link>https://community.cisco.com/t5/network-security/pro-con-ipsec-tunnels-through-firewalls/m-p/3216076#M1064962</link>
      <description>&lt;P&gt;One benefit is that you have an additional control what traffic reaches your VPN-gateway. If your VPN-device has a vulnerability on an default open port, the filerwall that only lets through the needed VPN-traffic will be an effective countermeasure. But at least for IPSec, a stateless ACL will be enough, a statefull firewall is not really needed.&lt;/P&gt;
&lt;P&gt;Personally, I often accept to have my VPN-gateway directly connected to the internet. But it‘s always important to have some device-hardening in place.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Nov 2017 06:10:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pro-con-ipsec-tunnels-through-firewalls/m-p/3216076#M1064962</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2017-11-14T06:10:15Z</dc:date>
    </item>
  </channel>
</rss>

