<?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 ISE 2.2 Posture Bypass in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3843486#M473621</link>
    <description>&lt;P&gt;My ISE environment is doing posture.&amp;nbsp; One of the posture requirements is that the computer must be on the domain.&amp;nbsp; We are checking for a certain registry entry to confirm that the machines are on the domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a use case where we have a handful of laptops that are not on our domain but we want them to be able to use the corporate network just like any other user.&amp;nbsp; Is there a way I can put a bypass in based on MAC address so these laptops don't have to be on the domain?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Apr 2019 20:10:00 GMT</pubDate>
    <dc:creator>Andy Guley</dc:creator>
    <dc:date>2019-04-23T20:10:00Z</dc:date>
    <item>
      <title>ISE 2.2 Posture Bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3843486#M473621</link>
      <description>&lt;P&gt;My ISE environment is doing posture.&amp;nbsp; One of the posture requirements is that the computer must be on the domain.&amp;nbsp; We are checking for a certain registry entry to confirm that the machines are on the domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a use case where we have a handful of laptops that are not on our domain but we want them to be able to use the corporate network just like any other user.&amp;nbsp; Is there a way I can put a bypass in based on MAC address so these laptops don't have to be on the domain?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2019 20:10:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3843486#M473621</guid>
      <dc:creator>Andy Guley</dc:creator>
      <dc:date>2019-04-23T20:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Posture Bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3844085#M473624</link>
      <description>There are several ways you can approach this. One way you can accomplish this is by setting up your Client Provisioning Policy 'other conditions' to match on an external source (AD) or internal endpoint groups. This would force posture assessment on your known assets and other assets would bypass the policy therefore not need to be scanned. HTH!</description>
      <pubDate>Wed, 24 Apr 2019 12:14:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3844085#M473624</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-04-24T12:14:31Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Posture Bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3844258#M473627</link>
      <description>&lt;P&gt;I suggest you refer the prescriptive deployment guide here -&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-documents/ise-posture-prescriptive-deployment-guide/ta-p/3680273" target="_self"&gt;Posture Prescriptive Deployment Guide&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 15:34:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-posture-bypass/m-p/3844258#M473627</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2019-04-24T15:34:18Z</dc:date>
    </item>
  </channel>
</rss>

