<?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: ISE Policy to Protect vCenter in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135462#M590245</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/218119"&gt;@jeaston&lt;/a&gt;&amp;nbsp;well ISE can push down a Downloadable ACL (DACL) or TrustSec SGACL these would be enforced somewhere on the network such as router, switch or firewall to permit/deny traffic.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Jun 2024 21:02:45 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2024-06-24T21:02:45Z</dc:date>
    <item>
      <title>ISE Policy to Protect vCenter</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135459#M590243</link>
      <description>&lt;P&gt;New to ISE and looking for some direction here.&lt;/P&gt;&lt;P&gt;I'd like to limit access to certain assets to a few jump servers. Not all traffic is going through a firewall&lt;/P&gt;&lt;P&gt;How can i control what devices can access things like vCenter, backup devices, IPMI interfaces?&lt;/P&gt;&lt;P&gt;Thanks in advan&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2024 20:38:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135459#M590243</guid>
      <dc:creator>jeaston</dc:creator>
      <dc:date>2024-06-24T20:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Policy to Protect vCenter</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135461#M590244</link>
      <description>&lt;P&gt;You should look in each of these applications to see if there is an option to restrict the access based on host (e.g. jumphost IPs) or network ranges (e.g. network management subnets). ISE supports this, and I have seen it on various other applications. Failing that, you'd have to put all those "assets" behind a firewall and make the access rules on the FW.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2024 20:46:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135461#M590244</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-06-24T20:46:10Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Policy to Protect vCenter</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135462#M590245</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/218119"&gt;@jeaston&lt;/a&gt;&amp;nbsp;well ISE can push down a Downloadable ACL (DACL) or TrustSec SGACL these would be enforced somewhere on the network such as router, switch or firewall to permit/deny traffic.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2024 21:02:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-protect-vcenter/m-p/5135462#M590245</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-06-24T21:02:45Z</dc:date>
    </item>
  </channel>
</rss>

