<?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 Policy to differentiate Windows and Apple in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215331#M551625</link>
    <description>&lt;P&gt;Thank you Mohammed&lt;/P&gt;</description>
    <pubDate>Mon, 13 Nov 2017 02:27:50 GMT</pubDate>
    <dc:creator>paul46</dc:creator>
    <dc:date>2017-11-13T02:27:50Z</dc:date>
    <item>
      <title>ISE Policy to differentiate Windows and Apple</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215164#M551365</link>
      <description>&lt;P&gt;Implementing wireless solution on ISE 2.3. Let me provide some details before I ask the question.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Want to authenticate windows machines using EAP-TLS via unique certificate. For all Apple iOS devices, want to authenticate via AirWatch. There will be two SSIDs - WiFiWindows and WiFiApple&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For Windows&lt;/P&gt;
&lt;P&gt;1. A corporate device connects to&amp;nbsp;WiFiWindows and presents certificate&lt;/P&gt;
&lt;P&gt;2. ISE validates certificates and provides corporate access&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for Apple&lt;/P&gt;
&lt;P&gt;1. An iOS device connects to&amp;nbsp;WiFiApple&lt;/P&gt;
&lt;P&gt;2. ISE makes an API call to MDM (AirWatch) and checks device's registration status&lt;/P&gt;
&lt;P&gt;3. If device is registered, corporate certificates is installed on devices to get full corporate access&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;question&lt;/P&gt;
&lt;P&gt;How to prevent Apple iOS devices to join WiFiWindows? In other words, windows and apple have same corporate certificate, but when Apple device joins WiFiWindows, access should be denied.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:38:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215164#M551365</guid>
      <dc:creator>paul46</dc:creator>
      <dc:date>2020-02-21T18:38:43Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Policy to differentiate Windows and Apple</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215176#M551366</link>
      <description>In your authorization rule you can combine Airespace-WLAN-ID with Endpoint&lt;BR /&gt;Identity Group. For example in your WLC if your win-ssid is having id 1 and&lt;BR /&gt;you are profiling your windows endpoints in win-identity-group. In this&lt;BR /&gt;case you authorization rule should match Airespace-WLAN-ID=1 &amp;amp; Endpoint&lt;BR /&gt;Identity Group=win-identity-group&lt;BR /&gt;</description>
      <pubDate>Sun, 12 Nov 2017 11:03:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215176#M551366</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2017-11-12T11:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Policy to differentiate Windows and Apple</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215292#M551474</link>
      <description>&lt;P&gt;Thanks Mohammed&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any solution without profiling?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 Nov 2017 22:34:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215292#M551474</guid>
      <dc:creator>paul46</dc:creator>
      <dc:date>2017-11-12T22:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Policy to differentiate Windows and Apple</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215330#M551624</link>
      <description>I an sure that you can match the oui portion of the radius&lt;BR /&gt;calling-station-id to detect apple device versus dell for example.&lt;BR /&gt;&lt;BR /&gt;But detecting the os require profiling as its detected with snmp traps and&lt;BR /&gt;nmap scans&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Nov 2017 02:25:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215330#M551624</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2017-11-13T02:25:10Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Policy to differentiate Windows and Apple</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215331#M551625</link>
      <description>&lt;P&gt;Thank you Mohammed&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2017 02:27:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-to-differentiate-windows-and-apple/m-p/3215331#M551625</guid>
      <dc:creator>paul46</dc:creator>
      <dc:date>2017-11-13T02:27:50Z</dc:date>
    </item>
  </channel>
</rss>

