<?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: Site-to-Site VPN is blocking SMB traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911605#M1103792</link>
    <description>&lt;P&gt;I believe I have that already set up (I followed the documentation on how to set up a site-to-site VPN, and configuring an Access Control Policy that would allow VPN traffic was part of that). Specifically, under "...-Internet-Outside" the top rule is:&lt;/P&gt;&lt;P&gt;Name: Allow Site-to-Site VPN&lt;BR /&gt;Source Zones: Any&lt;BR /&gt;Dest Zones: Any&lt;BR /&gt;Source Networks: group-inside-networks-vpn,&amp;nbsp;group-[remote]-networks-vpn&lt;BR /&gt;Dest Networks: group-inside-networks-vpn,&amp;nbsp;group-[remote]-networks-vpn&lt;BR /&gt;VLAN Tags: Any&lt;BR /&gt;Users: Any&lt;BR /&gt;Applications: Any&lt;BR /&gt;Source Ports: Any&lt;BR /&gt;Dest Ports: Any&lt;BR /&gt;URLs: Any&lt;BR /&gt;Source SGT: Any&lt;BR /&gt;Dest SGT: Any&lt;BR /&gt;Action: Allow&lt;/P&gt;&lt;P&gt;Since group-[remote]-networks-vpn contains the IP address ranges that are cover the traffic in that VPN tunnel, shouldn't this Access Control Policy be exempting that traffic?&lt;/P&gt;</description>
    <pubDate>Thu, 24 Aug 2023 19:58:44 GMT</pubDate>
    <dc:creator>nnraymond</dc:creator>
    <dc:date>2023-08-24T19:58:44Z</dc:date>
    <item>
      <title>Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911586#M1103790</link>
      <description>&lt;P&gt;I have our Firepower 4110 successfully connected via a site-to-site VPN to our Meraki MX95 appliance in another location, and things are mostly working however some of the SMB traffic is showing as action "Block", reason "File Block", ingress security zone "inside-internet", egress security zone "outside-internet". This is negatively impacting our ability to use PDQ Inventory and PDQ Deploy to manage our PC workstations across the VPN. Our VPN is running over an interface which is in the "outside-internet" group on the Firepower, but I obviously don't want the traffic inside that VPN connection to be scanned and blocked this way by the Firepower. What steps do I need to take to except that VPN traffic from inspection and blocking?&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 19:30:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911586#M1103790</guid>
      <dc:creator>nnraymond</dc:creator>
      <dc:date>2023-08-24T19:30:30Z</dc:date>
    </item>
    <item>
      <title>Re: Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911589#M1103791</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/517073"&gt;@nnraymond&lt;/a&gt; modify your file policy to ensure traffic from your LAN networks to the remote VPN networks is not inspected. &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/70/configuration/guide/fpmc-config-guide-v70/file_policies_and_advanced_malware_protection.html#id_104661" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/70/configuration/guide/fpmc-config-guide-v70/file_policies_and_advanced_malware_protection.html#id_104661&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 19:38:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911589#M1103791</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-08-24T19:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911605#M1103792</link>
      <description>&lt;P&gt;I believe I have that already set up (I followed the documentation on how to set up a site-to-site VPN, and configuring an Access Control Policy that would allow VPN traffic was part of that). Specifically, under "...-Internet-Outside" the top rule is:&lt;/P&gt;&lt;P&gt;Name: Allow Site-to-Site VPN&lt;BR /&gt;Source Zones: Any&lt;BR /&gt;Dest Zones: Any&lt;BR /&gt;Source Networks: group-inside-networks-vpn,&amp;nbsp;group-[remote]-networks-vpn&lt;BR /&gt;Dest Networks: group-inside-networks-vpn,&amp;nbsp;group-[remote]-networks-vpn&lt;BR /&gt;VLAN Tags: Any&lt;BR /&gt;Users: Any&lt;BR /&gt;Applications: Any&lt;BR /&gt;Source Ports: Any&lt;BR /&gt;Dest Ports: Any&lt;BR /&gt;URLs: Any&lt;BR /&gt;Source SGT: Any&lt;BR /&gt;Dest SGT: Any&lt;BR /&gt;Action: Allow&lt;/P&gt;&lt;P&gt;Since group-[remote]-networks-vpn contains the IP address ranges that are cover the traffic in that VPN tunnel, shouldn't this Access Control Policy be exempting that traffic?&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 19:58:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911605#M1103792</guid>
      <dc:creator>nnraymond</dc:creator>
      <dc:date>2023-08-24T19:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911607#M1103793</link>
      <description>&lt;P&gt;Hmm, I believe I chose "Allow" because that's what the guide said, but now that I think about it, should that instead be "Trust", since "Allow" will mean that intrusion protection and file policies will be applied, and that is likely what is causing the SMB traffic to be affected, correct? (And if so, what was the reasoning behind having it set to "Allow" instead of "Trust"?)&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 20:02:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911607#M1103793</guid>
      <dc:creator>nnraymond</dc:creator>
      <dc:date>2023-08-24T20:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911608#M1103794</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/517073"&gt;@nnraymond&lt;/a&gt; I am referring to the File Policy not the Access Control policy. The File Policy is associated to the Access Control Policy.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 20:04:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4911608#M1103794</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-08-24T20:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4913250#M1103852</link>
      <description>&lt;P&gt;FYI,&amp;nbsp;changing "Allow" to "Trust" on the "&lt;SPAN&gt;Allow Site-to-Site VPN" rule made no difference on the blocks that the Firepower is doing to that traffic.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We have one file policy, and is used by our 1 access control policy. I don't see any place in that file policy where I can create an exception for traffic over that site-to-site connection. There are two rules there:&lt;/P&gt;&lt;P&gt;Application Protocol: Any&lt;BR /&gt;Direction of Transfer: Any&lt;BR /&gt;Action: Block Malware&lt;BR /&gt;Enabled: Spero Analysis for MSEXE, Local Malware Analysis, Reset Connection&lt;BR /&gt;Store Files: Malware, Unknown&lt;BR /&gt;Categories: Local Malware Analysis, System Files, Graphics, Encoded, PDF files, Executables, Multimedia, Archive, Office Documents&lt;/P&gt;&lt;P&gt;Application Protocol: Any&lt;BR /&gt;Direction of Transfer: Any&lt;BR /&gt;Action: Block Malware&lt;BR /&gt;Enabled: Spero Analysis for MSEXE, Dynamic Analysis, Capacity Handling, Local Malware Analysis, Reset Connection&lt;BR /&gt;Store Files: Malware, Unknown, Categories: Dynamic Analysis Capable&lt;/P&gt;&lt;P&gt;Why didn't my alteration of the security policy rule from allow to trust bypass these Malware &amp;amp; File Policies? Is there something I'm supposed to do to the malware and file policies themselves to create an exception for the VPN, and if so, where? The page you linked me to doesn't seem to shed any light on that.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 19:50:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4913250#M1103852</guid>
      <dc:creator>nnraymond</dc:creator>
      <dc:date>2023-08-28T19:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: Site-to-Site VPN is blocking SMB traffic</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4913267#M1103854</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/517073"&gt;@nnraymond&lt;/a&gt;&amp;nbsp;thinking about it, create a new access control rule above the existing rule in the Access Control Policy, which permits the VPN traffic. Do NOT reference the file policy in this new rule, therefore VPN traffic will match the new rule without applying the file policy.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 20:18:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-vpn-is-blocking-smb-traffic/m-p/4913267#M1103854</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-08-28T20:18:34Z</dc:date>
    </item>
  </channel>
</rss>

