<?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: how to block non-computer join domain with cisco ISE ? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549361#M572705</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1267184"&gt;@bunleang&lt;/a&gt; there are several options:&lt;/P&gt;
&lt;P&gt;- You could issue a computer certificate to the domain joined computer, computers without this certificate will fail to authenticate.&lt;/P&gt;
&lt;P&gt;- You could use &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/216510-eap-chaining-with-teap.html" target="_self"&gt;EAP-TEAP&lt;/A&gt; (if your Windows 10 devices support it) which combines computer and user authentication (PEAP/MSCHAPv2 or TLS), if a non-domain joined computers fails both they will not be connected to the network.&lt;/P&gt;
&lt;P&gt;- You could use a custom profile using the AD Probe to determine whether the computer attempting to connect to the network is joined to the domain, this is the least preferred option.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Feb 2022 07:48:40 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2022-02-10T07:48:40Z</dc:date>
    <item>
      <title>how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549337#M572703</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;anyone can share how to&amp;nbsp;block non-computer join to domain with cisco ISE ? Does it possible to block non-computer join to domain or not with cisco ISE ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank in advance for your help&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 06:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549337#M572703</guid>
      <dc:creator>bunleang</dc:creator>
      <dc:date>2022-02-10T06:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549361#M572705</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1267184"&gt;@bunleang&lt;/a&gt; there are several options:&lt;/P&gt;
&lt;P&gt;- You could issue a computer certificate to the domain joined computer, computers without this certificate will fail to authenticate.&lt;/P&gt;
&lt;P&gt;- You could use &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/216510-eap-chaining-with-teap.html" target="_self"&gt;EAP-TEAP&lt;/A&gt; (if your Windows 10 devices support it) which combines computer and user authentication (PEAP/MSCHAPv2 or TLS), if a non-domain joined computers fails both they will not be connected to the network.&lt;/P&gt;
&lt;P&gt;- You could use a custom profile using the AD Probe to determine whether the computer attempting to connect to the network is joined to the domain, this is the least preferred option.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 07:48:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549361#M572705</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-02-10T07:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549363#M572706</link>
      <description>&lt;P&gt;Could you share with me the way to block with option AD probe to block&amp;nbsp; non-computer join domain ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;You could use AD Probe to determine whether the computer attempting to connect to the network is joined to the domain, this is the least preferred option.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 07:50:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549363#M572706</guid>
      <dc:creator>bunleang</dc:creator>
      <dc:date>2022-02-10T07:50:02Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549370#M572707</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1267184"&gt;@bunleang&lt;/a&gt; here is the Cisco guide.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-21/200553-Configure-ISE-2-1-Profiling-Services-bas.pdf" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-21/200553-Configure-ISE-2-1-Profiling-Services-bas.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You essentially create an AD Probe to query the AD domain, a computer that is AD joined MAC address is added to an Identity Group. You use this Identity Group in the ISE AuthZ policy, any device not matching can be denied.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 08:20:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549370#M572707</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-02-10T08:20:46Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549530#M572715</link>
      <description>&lt;P&gt;Totally agree with&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;options.&amp;nbsp; Sharing another option available and that is ISE posturing.&amp;nbsp; You could perform posture assessment against clients to determine if AD joined assets.&amp;nbsp; The posture solution is a bit complex, but really valuable:&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-documents/ise-posture-prescriptive-deployment-guide/ta-p/3680273" target="_blank"&gt;ISE Posture Prescriptive Deployment Guide - Cisco Community&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The example I am thinking of would be a registry check via posture assessment:&lt;/P&gt;
&lt;P&gt;HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History\&lt;BR /&gt;type: STRING - MachineDomain EQUALS &amp;lt;domain value&amp;gt;&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 12:40:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4549530#M572715</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2022-02-10T12:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4553243#M572810</link>
      <description>&lt;P&gt;If the computer is running Windows 10, why not use TEAP and use both machine and user authentication. If the machine is not part of the AD, it will fail authentication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 03:11:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4553243#M572810</guid>
      <dc:creator>Cisco-User500</dc:creator>
      <dc:date>2022-02-16T03:11:31Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4553270#M572812</link>
      <description>&lt;P&gt;I take the chance to launch a provocation.....isn't TLS alone a quite good warranty that the login comes from a domain host?&lt;/P&gt;&lt;P&gt;If I avoid manual certificate installation how can a user certificate be installed on a non domain computer?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 05:24:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4553270#M572812</guid>
      <dc:creator>Massimo Baschieri</dc:creator>
      <dc:date>2022-02-16T05:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: how to block non-computer join domain with cisco ISE ?</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4555970#M572868</link>
      <description>&lt;P&gt;u cant join a domin unless the person is part of doman admin grope&lt;/P&gt;&lt;P&gt;it will ask for domain admin name and password&lt;/P&gt;&lt;P&gt;so it not possable to join&lt;/P&gt;&lt;P&gt;but u can also set gpo to make shure it only apply to domain members&amp;nbsp; and block all others&lt;/P&gt;</description>
      <pubDate>Sat, 19 Feb 2022 18:10:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-block-non-computer-join-domain-with-cisco-ise/m-p/4555970#M572868</guid>
      <dc:creator>jamesbos96602</dc:creator>
      <dc:date>2022-02-19T18:10:32Z</dc:date>
    </item>
  </channel>
</rss>

