<?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 Recommended protocol for enterprise authentication in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/recommended-protocol-for-enterprise-authentication/m-p/3031022#M25908</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was wondering if anyone has any recommendations for authentication protocols in our scenario.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We need to be able to send user information from our ISE server to our Firepower system. &amp;nbsp;In order to gather user information from Domain joined computers, enterprise owned mobile devices, byod devices, and guest devices I am thinking of using the following for the respective wireless networks&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;SSID: Guest - Captive portal, self registration or pre defined guest accounts&lt;/P&gt;
&lt;P&gt;SSID: BYOD - PEAP-MSCHAPv2 with AD Authentication, Register to endpoint groups. &amp;nbsp;Users will need to be part of the correct AD group in order to login&lt;/P&gt;
&lt;P&gt;SSID: Corporate - PEAP-MSCHAPv2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was thinking of using PEAP-MSCHAPv2 instead of EAP-TLS (which is what we are currently using, but only for machine authentication) for corporate access because we have many shared machines. &amp;nbsp;Shared machines don't have user certificates so user authentication wont work in this scenario because I need the user certificate to do EAP-TLS and user authentication. &amp;nbsp;I cannot put user certificates on the computers because there may be 100's of users that use the machine over time.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The problem with using PEAP-MSCHAPv2 for corporate access is that I am finding it difficult to find a way to keep mobile byod devices from connect to the corporate SSID. &amp;nbsp;Does anyone have any authentication policies that I can try in order to disable non domain joined devices from connecting?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Anyone have any suggestions for a better way? &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Dan.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 07:49:03 GMT</pubDate>
    <dc:creator>dan.letkeman</dc:creator>
    <dc:date>2019-03-11T07:49:03Z</dc:date>
    <item>
      <title>Recommended protocol for enterprise authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/recommended-protocol-for-enterprise-authentication/m-p/3031022#M25908</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was wondering if anyone has any recommendations for authentication protocols in our scenario.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We need to be able to send user information from our ISE server to our Firepower system. &amp;nbsp;In order to gather user information from Domain joined computers, enterprise owned mobile devices, byod devices, and guest devices I am thinking of using the following for the respective wireless networks&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;SSID: Guest - Captive portal, self registration or pre defined guest accounts&lt;/P&gt;
&lt;P&gt;SSID: BYOD - PEAP-MSCHAPv2 with AD Authentication, Register to endpoint groups. &amp;nbsp;Users will need to be part of the correct AD group in order to login&lt;/P&gt;
&lt;P&gt;SSID: Corporate - PEAP-MSCHAPv2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was thinking of using PEAP-MSCHAPv2 instead of EAP-TLS (which is what we are currently using, but only for machine authentication) for corporate access because we have many shared machines. &amp;nbsp;Shared machines don't have user certificates so user authentication wont work in this scenario because I need the user certificate to do EAP-TLS and user authentication. &amp;nbsp;I cannot put user certificates on the computers because there may be 100's of users that use the machine over time.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The problem with using PEAP-MSCHAPv2 for corporate access is that I am finding it difficult to find a way to keep mobile byod devices from connect to the corporate SSID. &amp;nbsp;Does anyone have any authentication policies that I can try in order to disable non domain joined devices from connecting?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Anyone have any suggestions for a better way? &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Dan.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:49:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/recommended-protocol-for-enterprise-authentication/m-p/3031022#M25908</guid>
      <dc:creator>dan.letkeman</dc:creator>
      <dc:date>2019-03-11T07:49:03Z</dc:date>
    </item>
    <item>
      <title>SSID: Corporate - PEAP</title>
      <link>https://community.cisco.com/t5/network-access-control/recommended-protocol-for-enterprise-authentication/m-p/3031023#M25909</link>
      <description>&lt;P&gt;SSID: Corporate - PEAP-MSCHAPv2&lt;/P&gt;
&lt;P&gt;add a condition to ISE policy to check if the machine belongs to the domain, if yes then use desired result, else deny or limited access.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;**rate helpful posts**&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jul 2017 16:19:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/recommended-protocol-for-enterprise-authentication/m-p/3031023#M25909</guid>
      <dc:creator>Ambuj M</dc:creator>
      <dc:date>2017-07-09T16:19:20Z</dc:date>
    </item>
  </channel>
</rss>

