<?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: Using ISE to block TOR IP’s from connecting to VPN concentrators in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133832#M562271</link>
    <description>&lt;P&gt;ISE is the wrong solution for that requirement. Ideally have an upstream NGFW/IPS with geoblocking. Or use MFA (like Duo) with geofencing requirements enforced on the MFA client.&lt;/P&gt;</description>
    <pubDate>Tue, 11 Aug 2020 14:09:22 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2020-08-11T14:09:22Z</dc:date>
    <item>
      <title>Using ISE to block TOR IP’s from connecting to VPN concentrators</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133445#M562255</link>
      <description>&lt;P&gt;Is it possible to have ISE block TOR IP's from connecting to an ASA RAVPN?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2020 00:05:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133445#M562255</guid>
      <dc:creator>tgallawa</dc:creator>
      <dc:date>2020-08-11T00:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: Using ISE to block TOR IP’s from connecting to VPN concentrators</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133779#M562267</link>
      <description>&lt;P&gt;Best option would be to use the firewall itself to block certain IP's from connecting.&amp;nbsp; Ideally, you would have a "filtering" router at your Internet edge that blocks known bad IP's, RFC 1918 IP's, and your own internal subnet IP's (RFC 2827/BCP 38).&amp;nbsp; That prevents your firewall from having to process a lot of junk, which uses up resources.&lt;/P&gt;&lt;P&gt;If you cannot block on your edge router or firewall, then you could try to look for the "Framed-IP-Address" attribute in your authentication requests and use a Regex to match against your bad list.&amp;nbsp; But that is not ideal or efficient.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2020 13:13:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133779#M562267</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2020-08-11T13:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: Using ISE to block TOR IP’s from connecting to VPN concentrators</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133832#M562271</link>
      <description>&lt;P&gt;ISE is the wrong solution for that requirement. Ideally have an upstream NGFW/IPS with geoblocking. Or use MFA (like Duo) with geofencing requirements enforced on the MFA client.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2020 14:09:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-to-block-tor-ip-s-from-connecting-to-vpn-concentrators/m-p/4133832#M562271</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-08-11T14:09:22Z</dc:date>
    </item>
  </channel>
</rss>

