<?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: Does the IPS/Snort checks the VPN traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149170#M1114530</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1704941"&gt;@cmarin&lt;/a&gt; the solution you mentioned would work if you wanted to "force" inspection. Normally the traffic would not go through the DAQ and into Snort due to the sysopt parameter you mentioned.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jul 2024 16:15:32 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2024-07-23T16:15:32Z</dc:date>
    <item>
      <title>Does the IPS/Snort checks the VPN traffic</title>
      <link>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149113#M1114526</link>
      <description>&lt;P&gt;Hi Fellas,&lt;/P&gt;&lt;P&gt;I have a question, regarding how the ASA with IPS module or Firepower with intrusion policy is able to check VPN traffic.&lt;/P&gt;&lt;P&gt;The traffic is coming from a L2L tunnel and does a U turn pointing to a VTI so the traffic never pass through the device.&lt;BR /&gt;So in the config it just hits the NAT and the static route and never is being checked by an ACL or policy.&lt;/P&gt;&lt;P&gt;Is there a way the IPS/Snort inspect that traffic?&lt;/P&gt;&lt;P&gt;The only thing I have in mind is disable the &lt;SPAN&gt;sysopt connection permit-vpn and set a outside ALC or ACP pointing to the outside zone but I am not sure.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'll be waiting for your guidance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2024 14:41:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149113#M1114526</guid>
      <dc:creator>cmarin</dc:creator>
      <dc:date>2024-07-23T14:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: Does the IPS/Snort checks the VPN traffic</title>
      <link>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149118#M1114527</link>
      <description>&lt;P&gt;Use prefilter fastpath it better than use ACL&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2024 14:53:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149118#M1114527</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-07-23T14:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: Does the IPS/Snort checks the VPN traffic</title>
      <link>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149170#M1114530</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1704941"&gt;@cmarin&lt;/a&gt; the solution you mentioned would work if you wanted to "force" inspection. Normally the traffic would not go through the DAQ and into Snort due to the sysopt parameter you mentioned.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2024 16:15:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149170#M1114530</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2024-07-23T16:15:32Z</dc:date>
    </item>
    <item>
      <title>Re: Does the IPS/Snort checks the VPN traffic</title>
      <link>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149194#M1114533</link>
      <description>&lt;P&gt;So just let me confirm, if I disable the&amp;nbsp;&lt;SPAN&gt;sysopt connection permit-vpn I will be force to set ACLs or ACPs to allow the VPN traffic so in that way I could enable the intrusion policy for those specific lines to be checked.&lt;BR /&gt;I will try to test it and let you know.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2024 16:53:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5149194#M1114533</guid>
      <dc:creator>cmarin</dc:creator>
      <dc:date>2024-07-23T16:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Does the IPS/Snort checks the VPN traffic</title>
      <link>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5198076#M1116025</link>
      <description>&lt;P&gt;Correct.&amp;nbsp; The sysopt conn permit is going to bypass any zone/interface for the traffic coming in on a tunnel.&amp;nbsp; Now, you could put a vpn filter on the side of concern to control pre-encrypted/post-decrypted traffic, but in my testing I did not see that run across snort.&amp;nbsp; If you disable the sysopt command, any traffic coming in, tunnel or not, is going to run across that zone/interface ACL.&amp;nbsp; Then just specify the IPS policy on the ACE for the traffic you are wanting inspected.&amp;nbsp; I would be cautious when disabling that option, as it is global.&amp;nbsp; The FMC/FTDs sure make it seem as a per tunnel basis, but it is not.&amp;nbsp; If other tunnels are terminating to this firewall and relying on the sysopt command, and no reverse rules to allow traffic in from the other peers are in place, traffic will begin to be dropped.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 11:25:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/does-the-ips-snort-checks-the-vpn-traffic/m-p/5198076#M1116025</guid>
      <dc:creator>rickbnet</dc:creator>
      <dc:date>2024-09-24T11:25:46Z</dc:date>
    </item>
  </channel>
</rss>

