<?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: Identify Corporate MacOS from VPN,Wired,Wireless using ISE as Radius Server in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3948035#M456587</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;A couple of options to accomplish your goal:&lt;BR /&gt;-You could deploy specific VPN profiles with unique tunnel group names and do a match in your client provisioning policy utilizing Cisco-VPN3000:CVPN3000/ASA/PIX7x-Tunnel-Group-Name EQUALS &amp;lt;your tunnel group name&amp;gt;.&lt;BR /&gt;-Determine a piece of corporate software that you could setup a posture check on to determine that the host is truly a corporate machine&lt;BR /&gt;-Utilize other conditions in client provisioning policy that do a check against your identity source to determine if truly a corporate asset&lt;BR /&gt;I would recommend thinking about how your corporate machines are unique and how you can determine that they are unique &amp;amp; truly your asset. Good luck &amp;amp; HTH!&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Right unlike windows this information is not available as a machine auth or user auth. Perhaps you can deploy JAMF? or EAP-TLS only for corporate machines to use certificate auth? and not corporate only allowed to use user/password?&lt;/P&gt;</description>
    <pubDate>Fri, 25 Oct 2019 10:38:29 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2019-10-25T10:38:29Z</dc:date>
    <item>
      <title>Identify Corporate MacOS from VPN,Wired,Wireless using ISE as Radius Server</title>
      <link>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3937646#M456584</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to identify corporate MacOS vs non-corporate MacOS machine? We are using ISE as radius server for our VPN, Wired and Wireless connection with login using username. We wanted to limit the clients to only use MacOS provided by the company and not allow connection for non-corporate MacOS.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 19:10:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3937646#M456584</guid>
      <dc:creator>misinsuan2229</dc:creator>
      <dc:date>2020-02-21T19:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Corporate MacOS from VPN,Wired,Wireless using ISE as Radius Server</title>
      <link>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3937868#M456585</link>
      <description>A couple of options to accomplish your goal:&lt;BR /&gt;-You could deploy specific VPN profiles with unique tunnel group names and do a match in your client provisioning policy utilizing Cisco-VPN3000:CVPN3000/ASA/PIX7x-Tunnel-Group-Name EQUALS &amp;lt;your tunnel group name&amp;gt;.&lt;BR /&gt;-Determine a piece of corporate software that you could setup a posture check on to determine that the host is truly a corporate machine&lt;BR /&gt;-Utilize other conditions in client provisioning policy that do a check against your identity source to determine if truly a corporate asset&lt;BR /&gt;I would recommend thinking about how your corporate machines are unique and how you can determine that they are unique &amp;amp; truly your asset. Good luck &amp;amp; HTH!</description>
      <pubDate>Wed, 09 Oct 2019 12:39:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3937868#M456585</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-10-09T12:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Corporate MacOS from VPN,Wired,Wireless using ISE as Radius Server</title>
      <link>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3948035#M456587</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;A couple of options to accomplish your goal:&lt;BR /&gt;-You could deploy specific VPN profiles with unique tunnel group names and do a match in your client provisioning policy utilizing Cisco-VPN3000:CVPN3000/ASA/PIX7x-Tunnel-Group-Name EQUALS &amp;lt;your tunnel group name&amp;gt;.&lt;BR /&gt;-Determine a piece of corporate software that you could setup a posture check on to determine that the host is truly a corporate machine&lt;BR /&gt;-Utilize other conditions in client provisioning policy that do a check against your identity source to determine if truly a corporate asset&lt;BR /&gt;I would recommend thinking about how your corporate machines are unique and how you can determine that they are unique &amp;amp; truly your asset. Good luck &amp;amp; HTH!&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Right unlike windows this information is not available as a machine auth or user auth. Perhaps you can deploy JAMF? or EAP-TLS only for corporate machines to use certificate auth? and not corporate only allowed to use user/password?&lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2019 10:38:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/identify-corporate-macos-from-vpn-wired-wireless-using-ise-as/m-p/3948035#M456587</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-10-25T10:38:29Z</dc:date>
    </item>
  </channel>
</rss>

