<?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: IAM/NAC: Binding of Certificate and MAC Address in Analytics &amp; Visibility</title>
    <link>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51733#M67</link>
    <description>Some customers fear that their users export their smartphone certificates and install them unto their own devices to get full access to the network. Solution today is to implement non-exportable certificates, so no 802.1X for smartphones (or similar). &lt;BR /&gt;
&lt;BR /&gt;
It would be easier, if it was possible to match the MAC and a certificate attribute for certain device types (of the customers choosing). Especially if there was an alarm/trap/etc, when this match fails. &lt;BR /&gt;</description>
    <pubDate>Thu, 09 Jan 2014 15:31:00 GMT</pubDate>
    <dc:creator>Barbara_Günther</dc:creator>
    <dc:date>2014-01-09T15:31:00Z</dc:date>
    <item>
      <title>IAM/NAC: Binding of Certificate and MAC Address</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51729#M63</link>
      <description>I experience the customer need for a feature where you can bind the Subject of the Certificate to the MAC Address. For example CN=00-11-22-33-44-55 and RADIUS Calling-Station-ID Attribute. &lt;BR /&gt;
&lt;BR /&gt;
Use Case: You want to integrate Mobile Devices into your corporate Wifi secured via certificate (EAP-TLS). The mentioned feature would avoid the user to export the certificate and import it on a own device (as long as the MAC is not spoofed).&lt;BR /&gt;
&lt;BR /&gt;
Are there any other ideas to realize this use case?&lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
Michael&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Nov 2013 03:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51729#M63</guid>
      <dc:creator>Michael_Kirchne</dc:creator>
      <dc:date>2013-11-27T03:03:00Z</dc:date>
    </item>
    <item>
      <title>RE: IAM/NAC: Binding of Certificate and MAC Address</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51730#M64</link>
      <description>Hi Michael, I am going to run this through our product management group and have someone respond shortly.  Thanks for the suggestion!</description>
      <pubDate>Mon, 02 Dec 2013 19:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51730#M64</guid>
      <dc:creator>Tamera_Rousseau</dc:creator>
      <dc:date>2013-12-02T19:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: IAM/NAC: Binding of Certificate and MAC Address</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51731#M65</link>
      <description>We will take this request into consideration but would like to hear from our users on this request.</description>
      <pubDate>Tue, 17 Dec 2013 01:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51731#M65</guid>
      <dc:creator>Kafel__Ali</dc:creator>
      <dc:date>2013-12-17T01:05:00Z</dc:date>
    </item>
    <item>
      <title>RE: IAM/NAC: Binding of Certificate and MAC Address</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51732#M66</link>
      <description>The certificate could be generated with a private key that is not allowed to be exported. But this doesn't help in any circumstance and makes backups of the certificates more complicated for administrators. The suggested solution is a good way to improve this issue.</description>
      <pubDate>Thu, 09 Jan 2014 15:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51732#M66</guid>
      <dc:creator>Max_Zöller</dc:creator>
      <dc:date>2014-01-09T15:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: IAM/NAC: Binding of Certificate and MAC Address</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51733#M67</link>
      <description>Some customers fear that their users export their smartphone certificates and install them unto their own devices to get full access to the network. Solution today is to implement non-exportable certificates, so no 802.1X for smartphones (or similar). &lt;BR /&gt;
&lt;BR /&gt;
It would be easier, if it was possible to match the MAC and a certificate attribute for certain device types (of the customers choosing). Especially if there was an alarm/trap/etc, when this match fails. &lt;BR /&gt;</description>
      <pubDate>Thu, 09 Jan 2014 15:31:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/iam-nac-binding-of-certificate-and-mac-address/m-p/51733#M67</guid>
      <dc:creator>Barbara_Günther</dc:creator>
      <dc:date>2014-01-09T15:31:00Z</dc:date>
    </item>
  </channel>
</rss>

