<?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: Is it possible in ISE-PIC to block updates for certain type of users with regex or some other mechanism? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552544#M557542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no mechanism on ISE-PIC today. Would love to hear more about the use case. Would also like to know if this exception would be applicable to all ISE-PIC subscribers or just to one subscriber? If this is for a single ISE-PIC subscriber than it perhaps a better request for that subscriber.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Apr 2017 18:26:53 GMT</pubDate>
    <dc:creator>kegagnon</dc:creator>
    <dc:date>2017-04-27T18:26:53Z</dc:date>
    <item>
      <title>Is it possible in ISE-PIC to block updates for certain type of users with regex or some other mechanism?</title>
      <link>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552543#M557540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a mechanism to filter username to IP address mapping for certain users within ISE-PIC?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:32:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552543#M557540</guid>
      <dc:creator>Allen P Chen</dc:creator>
      <dc:date>2020-02-21T18:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible in ISE-PIC to block updates for certain type of users with regex or some other mechanism?</title>
      <link>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552544#M557542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no mechanism on ISE-PIC today. Would love to hear more about the use case. Would also like to know if this exception would be applicable to all ISE-PIC subscribers or just to one subscriber? If this is for a single ISE-PIC subscriber than it perhaps a better request for that subscriber.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Apr 2017 18:26:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552544#M557542</guid>
      <dc:creator>kegagnon</dc:creator>
      <dc:date>2017-04-27T18:26:53Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible in ISE-PIC to block updates for certain type of users with regex or some other mechanism?</title>
      <link>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552545#M557548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, we may define &lt;STRONG&gt;mapping filters&lt;/STRONG&gt; with username and/or IP address/subnet but no regex.&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="106804" alt="Screen Shot 2017-04-27 at 12.09.37 PM.png" class="image-1 jive-image" src="/legacyfs/online/fusion/106804_Screen Shot 2017-04-27 at 12.09.37 PM.png" style="height: 242px; width: 620px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Apr 2017 19:10:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-it-possible-in-ise-pic-to-block-updates-for-certain-type-of/m-p/3552545#M557548</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-04-27T19:10:34Z</dc:date>
    </item>
  </channel>
</rss>

