<?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: Block access to Remote Access VPN by IP Address in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4920522#M1104124</link>
    <description>&lt;P&gt;Good to know. I'll give this a shot.&amp;nbsp; Thank you.&lt;/P&gt;</description>
    <pubDate>Fri, 08 Sep 2023 17:45:45 GMT</pubDate>
    <dc:creator>Jordan1212</dc:creator>
    <dc:date>2023-09-08T17:45:45Z</dc:date>
    <item>
      <title>Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406832#M1080956</link>
      <description>&lt;P&gt;I am running a couple of Cisco FTD 2110 managed with FMC and am looking for the best way to block access to our remote access VPN by IP. From doing some reading it looks like the best (and only?) way to do this is via a control plane ACL deployed via Flex Config. I saw another post that showed how this could be accomplished via geo but I am unsure on that syntax. I'm hoping someone could provide what syntax is used or point me towards some documentation for this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2021 19:37:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406832#M1080956</guid>
      <dc:creator>PerryGuy621</dc:creator>
      <dc:date>2021-05-21T19:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406840#M1080957</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1198016"&gt;@PerryGuy621&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;No you cannot currently use Geolocation to block traffic "to" the FTD to filter VPN connections. Still an unresolved and open feature request...&lt;/P&gt;
&lt;P&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs65322/?rfs=iqvred" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs65322/?rfs=iqvred&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Use flexconfig to apply a control plane ACL, or filter on the upstream router or place another FTD in front of the RAVPN FTD.&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2021 19:46:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406840#M1080957</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2021-05-21T19:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406845#M1080958</link>
      <description>&lt;P&gt;Is there any documentation on what the control plane ACL would need to look like? Are we able to use a network object group along with it?&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2021 19:52:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406845#M1080958</guid>
      <dc:creator>PerryGuy621</dc:creator>
      <dc:date>2021-05-21T19:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406980#M1080965</link>
      <description>&lt;P&gt;here it will give you high level control plan ACL information : (HTH)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/212321-clarify-the-firepower-threat-defense-acc.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/212321-clarify-the-firepower-threat-defense-acc.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 22 May 2021 09:24:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4406980#M1080965</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2021-05-22T09:24:42Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4407137#M1080988</link>
      <description>&lt;P&gt;You should be able to use a normal extended ACL object (including network object group). Just add the parameter "control-plane" at the end of the access-group command which applies the ACL to the interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 23 May 2021 04:38:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4407137#M1080988</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-05-23T04:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4410903#M1081178</link>
      <description>&lt;P&gt;And how do I do this in FMC?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is ridiculous, how do I block IP address from trying to establish a VPN connection? It is such a basic, fundamnetal request, for god sake.&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 10:13:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4410903#M1081178</guid>
      <dc:creator>GSAInfra</dc:creator>
      <dc:date>2021-05-31T10:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4411280#M1081194</link>
      <description>&lt;P&gt;For what it`s worth you could utilize an MFA solution (which you should have anyway) which allows GEO blocks (like DUO MFA).&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2021 08:16:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4411280#M1081194</guid>
      <dc:creator>rschlayer</dc:creator>
      <dc:date>2021-06-01T08:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4412133#M1081243</link>
      <description>&lt;P&gt;I just tested and confirmed this can be done in FMC.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/network-security/ftd-remote-access-vpn-restriction/m-p/4411914#M1081231" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/network-security/ftd-remote-access-vpn-restriction/m-p/4411914#M1081231&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Short steps:&lt;/P&gt;
&lt;P&gt;1. Create an extended ACL object that denies the sources you want to block and allows all others.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Extended ACL object" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/121715iD7EDEE0E00857830/image-size/large?v=v2&amp;amp;px=999" role="button" title="flexconfig-extended ACL.PNG" alt="Extended ACL object" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Extended ACL object&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;2.Create a Flexconfig object that defines a variable linked to the ACL you just created.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Flexconfig variable" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/121716i26E5CF1747686D6D/image-size/large?v=v2&amp;amp;px=999" role="button" title="flexconfig-variable.PNG" alt="Flexconfig variable" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Flexconfig variable&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;3. Create a second Flexconfig object that references the ACL variable and applies it to the desired interface including the "control-plane" keyword.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Flexconfig object" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/121713iEAD0D6CADEDD5EDD/image-size/large?v=v2&amp;amp;px=999" role="button" title="flexconfig-object.PNG" alt="Flexconfig object" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Flexconfig object&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;4. Create and deploy a Flexconfig policy to the target FTD device(s).&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Flexconfig policy" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/121714i617C07500C544321/image-size/large?v=v2&amp;amp;px=999" role="button" title="flexconfig-policy.PNG" alt="Flexconfig policy" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Flexconfig policy&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 17:52:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4412133#M1081243</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-06-02T17:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4536717#M1086683</link>
      <description>&lt;P&gt;Will applying the extended ACL to the Outside interface not override the Access Control Policy defined within the FMC (under Policies&amp;gt;Access Control)?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jan 2022 04:01:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4536717#M1086683</guid>
      <dc:creator>jasond</dc:creator>
      <dc:date>2022-01-24T04:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4536810#M1086685</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/285375"&gt;@jasond&lt;/a&gt; no, a control-plane ACL applied inbound on the outside interface will filter traffic "to" the FTD. The ACP controls traffic "through" the FTD.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The control-plane would permit or deny the VPN connection from being established, the ACP would control the communication if the VPN is established.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jan 2022 08:18:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4536810#M1086685</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-01-24T08:18:27Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4754410#M1096741</link>
      <description>&lt;P&gt;Sorry to bring something up from the dead, but I was curious why the multiple steps (which I plan to use) in the Marvin version (Thank you, Marvin!!) vs the steps in this link -&amp;nbsp;&lt;A href="https://integratingit.wordpress.com/2021/06/26/ftd-control-plane-acl/" target="_blank"&gt;https://integratingit.wordpress.com/2021/06/26/ftd-control-plane-acl/&lt;/A&gt;&lt;BR /&gt;More control of the different parts?&lt;BR /&gt;Thank you!!&lt;/P&gt;&lt;P&gt;Darren&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 17:29:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4754410#M1096741</guid>
      <dc:creator>darrendanko12</dc:creator>
      <dc:date>2023-01-13T17:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4754656#M1096754</link>
      <description>&lt;P&gt;The two are basically the same, just that the one&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;has shown creates it using GUI and reusable objects, while the one in the link you posted creates this using ASA commands directly into the FlexConfig, but will not be available for re-use in any other configuration.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Jan 2023 09:56:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4754656#M1096754</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-01-14T09:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4779993#M1098076</link>
      <description>&lt;P&gt;Another thread necro:&lt;BR /&gt;&lt;BR /&gt;Why are there 2 flex-config objects? It looks like the first one creates a variable, but it isn't referenced in the 2nd flexconfig object. I'm wondering if this is a typo, or do you not need the first object.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2023 01:02:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4779993#M1098076</guid>
      <dc:creator>rtrefz</dc:creator>
      <dc:date>2023-02-22T01:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4780551#M1098081</link>
      <description>&lt;P&gt;It's a typo. I should have shown the creation of contolplaneacl object in the first step.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2023 14:00:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4780551#M1098081</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2023-02-22T14:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4780590#M1098082</link>
      <description>&lt;P&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;What sort of object is controlplaneacl? What information does it contain?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2023 14:17:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4780590#M1098082</guid>
      <dc:creator>rtrefz</dc:creator>
      <dc:date>2023-02-22T14:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4780617#M1098084</link>
      <description>&lt;P&gt;It's an extended ACL. Looks the same as the object ACL-Control_Plane-Test that I showed, but with a name that was more acceptable for parsing by Flexconfig.&lt;/P&gt;
&lt;P&gt;Basically you block the IPs/objects you want to prevent from RA VPN access and allow everything else.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2023 14:43:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4780617#M1098084</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2023-02-22T14:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4791587#M1098573</link>
      <description>&lt;P&gt;Is this still the only way to accomplish this? Can we not do geo-ip based restrictions for control plane traffic even now?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 17:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4791587#M1098573</guid>
      <dc:creator>thegreatone</dc:creator>
      <dc:date>2023-03-10T17:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4791594#M1098574</link>
      <description>&lt;P&gt;Not yet - but it is in the roadmap for an upcoming release.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 17:18:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4791594#M1098574</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2023-03-10T17:18:52Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4804364#M1099104</link>
      <description>&lt;P&gt;Unbelievable. A basic function of a firewall. No wonder my colleges are switching to Checkpoint.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2023 02:03:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4804364#M1099104</guid>
      <dc:creator>scottyd</dc:creator>
      <dc:date>2023-03-30T02:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: Block access to Remote Access VPN by IP Address</title>
      <link>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4852394#M1101477</link>
      <description>&lt;P&gt;Do you know if this will this work with an ASA SFR?&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jun 2023 00:13:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-access-to-remote-access-vpn-by-ip-address/m-p/4852394#M1101477</guid>
      <dc:creator>ChadH63728</dc:creator>
      <dc:date>2023-06-11T00:13:38Z</dc:date>
    </item>
  </channel>
</rss>

