<?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 Enterprise Users - How are you using ISE? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/enterprise-users-how-are-you-using-ise/m-p/2784473#M41813</link>
    <description>&lt;P&gt;Wanted to get a feel as to how those of you in the Enterprise space (maybe 1000+ employees) are using ISE.&amp;nbsp; Primarily for guests?&amp;nbsp; Special network needs or have you rolled it out to every port on your network?&lt;/P&gt;
&lt;P&gt;Am evaluating various deployment scenarios and considering the associated pain that might go along with each.&amp;nbsp; Potentially could start with a simple "trusted" device vs. "un-trusted" device where "trusted" means there are valid credentials provided PLUS an org provided certificate installed on the machine and provided during authentication.&amp;nbsp; That might be too cumbersome, however and could look at just checking for the presence of a registry key or equivalent depending on the platform.&amp;nbsp; This would still be messy with mobile devices I assume, but might be a good starting point.&lt;/P&gt;
&lt;P&gt;Interested to hear how those of you are using ISE In the wild, however.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 06:15:00 GMT</pubDate>
    <dc:creator>rvandolson</dc:creator>
    <dc:date>2019-03-11T06:15:00Z</dc:date>
    <item>
      <title>Enterprise Users - How are you using ISE?</title>
      <link>https://community.cisco.com/t5/network-access-control/enterprise-users-how-are-you-using-ise/m-p/2784473#M41813</link>
      <description>&lt;P&gt;Wanted to get a feel as to how those of you in the Enterprise space (maybe 1000+ employees) are using ISE.&amp;nbsp; Primarily for guests?&amp;nbsp; Special network needs or have you rolled it out to every port on your network?&lt;/P&gt;
&lt;P&gt;Am evaluating various deployment scenarios and considering the associated pain that might go along with each.&amp;nbsp; Potentially could start with a simple "trusted" device vs. "un-trusted" device where "trusted" means there are valid credentials provided PLUS an org provided certificate installed on the machine and provided during authentication.&amp;nbsp; That might be too cumbersome, however and could look at just checking for the presence of a registry key or equivalent depending on the platform.&amp;nbsp; This would still be messy with mobile devices I assume, but might be a good starting point.&lt;/P&gt;
&lt;P&gt;Interested to hear how those of you are using ISE In the wild, however.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:15:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/enterprise-users-how-are-you-using-ise/m-p/2784473#M41813</guid>
      <dc:creator>rvandolson</dc:creator>
      <dc:date>2019-03-11T06:15:00Z</dc:date>
    </item>
    <item>
      <title>Guest access and posture</title>
      <link>https://community.cisco.com/t5/network-access-control/enterprise-users-how-are-you-using-ise/m-p/2784474#M41814</link>
      <description>&lt;P&gt;Guest access and posture assessment. We also use it for dynamic switch port configuration after assessment takes place. This is because we have a bunch of VLAN specific devices that dont move around too much but they do move aroudn and it take a lot of work away from the administrators to reconfigure a switch port to account for a new device on a new VLAN.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Please rate useful posts and mark answers as correct if applicable.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2015 14:54:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/enterprise-users-how-are-you-using-ise/m-p/2784474#M41814</guid>
      <dc:creator>zdesignstudio</dc:creator>
      <dc:date>2015-11-18T14:54:31Z</dc:date>
    </item>
  </channel>
</rss>

