<?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 - Separate database for each site in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5197563#M591929</link>
    <description>&lt;P&gt;No.&amp;nbsp; ISE is not designed for multi-tenancy.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Sep 2024 12:02:01 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2024-09-23T12:02:01Z</dc:date>
    <item>
      <title>ISE - Separate database for each site</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5196978#M591900</link>
      <description>&lt;P&gt;We have to manage 1000s of sites &amp;amp; have a workflow whereby we want one admin per high school to be able to add devices using their mac addresses.&lt;/P&gt;&lt;P&gt;But there is a requirement that each site's admin should keep a &lt;EM&gt;separate&lt;/EM&gt; DB of registered mac addresses, without seeing the other site's registered devices.&lt;/P&gt;&lt;P&gt;These devices should then authenticate on wire with MAC auth.&lt;BR /&gt;&lt;BR /&gt;Is this database separation &amp;amp; invisibility of other sites possible in Cisco ISE? If yes, how?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2024 16:17:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5196978#M591900</guid>
      <dc:creator>NetfastProjectAdmin48133</dc:creator>
      <dc:date>2024-09-20T16:17:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Separate database for each site</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5196999#M591901</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;- Not if your ISE is centralized with overall (centric) polices ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2024 16:52:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5196999#M591901</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-09-20T16:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Separate database for each site</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5197563#M591929</link>
      <description>&lt;P&gt;No.&amp;nbsp; ISE is not designed for multi-tenancy.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2024 12:02:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5197563#M591929</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-09-23T12:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Separate database for each site</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5197570#M591931</link>
      <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/218190-configure-ise-3-2-data-connect-integrati.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/218190-configure-ise-3-2-data-connect-integrati.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Check this contact cisco for more info&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2024 12:06:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-separate-database-for-each-site/m-p/5197570#M591931</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-09-23T12:06:44Z</dc:date>
    </item>
  </channel>
</rss>

