<?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: Envoy integration with ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/5011987#M587035</link>
    <description>&lt;P&gt;You can limit the risk by only allowing the IPs provided in the Envoy documentation to access the ISE node externally.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Feb 2024 14:37:45 GMT</pubDate>
    <dc:creator>gho21</dc:creator>
    <dc:date>2024-02-02T14:37:45Z</dc:date>
    <item>
      <title>Envoy integration with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/4981504#M585804</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are planning to integrate the Envoy tool to integrate with ISE to automate the guest authentication.&lt;/P&gt;&lt;P&gt;For this, in the Envoy guide it require a public IP for the ISE admin node.&lt;/P&gt;&lt;P&gt;Our setup is behind a firewall and we would need to allow the specific rule in the firewall for the Envoy to communicate.&lt;/P&gt;&lt;P&gt;Is there any risk associated with this setup and any impact to be expected if anyone is having experience with integrating the Envoy tool.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Prathap&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2023 15:19:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/4981504#M585804</guid>
      <dc:creator>prathapss</dc:creator>
      <dc:date>2023-12-19T15:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: Envoy integration with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/4981776#M585806</link>
      <description>&lt;P&gt;I've integrated Envoy with other NAC providers but not with ISE specifically.&amp;nbsp; There is always risk associated to opening anything up directly to the internet.&amp;nbsp; That being said proper firewall policy, inspection, etc should mitigate that risk to some degree.&amp;nbsp; Also be sure to keep your ISE deployment upgraded and patched.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2023 20:14:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/4981776#M585806</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-12-19T20:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: Envoy integration with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/5011987#M587035</link>
      <description>&lt;P&gt;You can limit the risk by only allowing the IPs provided in the Envoy documentation to access the ISE node externally.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 14:37:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/envoy-integration-with-ise/m-p/5011987#M587035</guid>
      <dc:creator>gho21</dc:creator>
      <dc:date>2024-02-02T14:37:45Z</dc:date>
    </item>
  </channel>
</rss>

