<?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 ISE Lock accounts to machines in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289937#M108090</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah you have to deploy certificate to authenticate devices and user&amp;nbsp; with non-exportable private key. That is the only way by which you can&amp;nbsp; achieve your goal.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Aug 2013 03:10:44 GMT</pubDate>
    <dc:creator>Ravi Singh</dc:creator>
    <dc:date>2013-08-26T03:10:44Z</dc:date>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289935#M108086</link>
      <description>&lt;P&gt;I am trying to determine if there is a way to limit the number of logins. Basically, the requirement is to allow a user X number of concurrent logins, but restrict those logins to the first X machines they log into.&amp;nbsp; The requirement is to prevent users from passing their credentials around to other unauthorized users.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:48:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289935#M108086</guid>
      <dc:creator>MMstre</dc:creator>
      <dc:date>2019-03-11T03:48:33Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289936#M108088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Michael,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can only restrict guests to one concurrent login of 1 or unlimited. However if you have a list of all mac addresses, you can import them into ise and statically assign them to a endpoint group, from there you can combine a policy that only allows users to connect with a device that you assigned to an endpoint group with a valid AD account.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However your best bet is to deploy certificates if you run in an AD environment where all devices are joined to the domain, it is very simple to use group policies to deploy certificates which you can make the private keys not exportable. Then you can switch your authentication policy so that certs are used instead of passwords.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you run all users in AD or if you would like some info on certificate enrollment&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 25 Aug 2013 07:06:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289936#M108088</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-25T07:06:59Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289937#M108090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah you have to deploy certificate to authenticate devices and user&amp;nbsp; with non-exportable private key. That is the only way by which you can&amp;nbsp; achieve your goal.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2013 03:10:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289937#M108090</guid>
      <dc:creator>Ravi Singh</dc:creator>
      <dc:date>2013-08-26T03:10:44Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289938#M108093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ISE-1.1 version does not support the limits on concurrent logins but ISE 1.2 support this function.&lt;/P&gt;&lt;P&gt;Release Notes for Cisco Identity Services Engine, Release 1.2&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/ise/1.2/release_notes/ise12_rn.html"&gt;http://www.cisco.com/en/US/docs/security/ise/1.2/release_notes/ise12_rn.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 17:11:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289938#M108093</guid>
      <dc:creator>aqjaved</dc:creator>
      <dc:date>2013-08-27T17:11:45Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289939#M108111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Aqeel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was my understanding the ISE 1.2 only allows this feature for guests&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 17:17:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289939#M108111</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-27T17:17:59Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289940#M108138</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Please find the attached solution.&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/3/4/9/152943-111.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 19:13:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289940#M108138</guid>
      <dc:creator>blenka</dc:creator>
      <dc:date>2013-08-27T19:13:46Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289941#M108206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The initial question is around dot1x authentication. Please take some time to understand the question above. This has nothing to do with Administrative access nor does it involve guests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 19:33:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289941#M108206</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-27T19:33:14Z</dc:date>
    </item>
    <item>
      <title>ISE Lock accounts to machines</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289942#M108227</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Tarik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the suggestions.&amp;nbsp; However, at this time, the deployment is going to be a live pilot (I know, dangerous move lol), but its what is going to convince the customer of ISE's features.&lt;/P&gt;&lt;P&gt;Cert services isn't an option at this time, due to time constraints and the environment this is being rolled out to.&lt;/P&gt;&lt;P&gt;it's basically a trade show and they are allowing all invitees to use their network, but cant deploy certs, or expect the invitees to be able to install them. Apparently, these guests have been known to pass around credentials and this is what they are trying to prevent.&lt;/P&gt;&lt;P&gt;I have locked them down to 3 concurrent connections, but i am not sure if that will do the trick.&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks again for you reply&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 20:10:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-lock-accounts-to-machines/m-p/2289942#M108227</guid>
      <dc:creator>MMstre</dc:creator>
      <dc:date>2013-08-27T20:10:39Z</dc:date>
    </item>
  </channel>
</rss>

