<?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: Profiler Feed in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021419#M454224</link>
    <description>&lt;P&gt;Hi Donald,&lt;/P&gt;
&lt;P&gt;There is always a bit of risk in using the automated feed service updates on a production system. Ideally, you would want to test the feed service updates in a non-prod environment before updating them in production.&lt;/P&gt;
&lt;P&gt;Typically, there are two ways this is done by customers:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Disable the Online Subscription Update for the Feed Service in the Prod system. Allow a Non-Prod system to auto-update via the Feed Service and use the option to notify an Administrator via email when the update occurs. After testing in the Non-Prod environment, enable the Online Update in Prod and perform a manual update during a change window. Perform endpoint testing and back out (Undo Latest) the update if any issues are found.&lt;/LI&gt;
&lt;LI&gt;Disable the Online Subscription Update in the Prod system and use Offline updates. Register for the Offline Feed Service Management via &lt;A href="https://ise.cisco.com/partner/" target="_self"&gt;https://ise.cisco.com/partner&lt;/A&gt; and sign up for update notifications via email. When new updates are available, download and evaluate the XML file for any overlapping or conflicting profiler updates and test in Non-Prod (if possible). Perform the offline update during a change window, perform endpoint testing, and back out the update if any issues are found.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Greg&lt;/P&gt;</description>
    <pubDate>Fri, 31 Jan 2020 01:58:03 GMT</pubDate>
    <dc:creator>Greg Gibbs</dc:creator>
    <dc:date>2020-01-31T01:58:03Z</dc:date>
    <item>
      <title>Profiler Feed</title>
      <link>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021293#M454222</link>
      <description>&lt;P&gt;Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a way to identify what will be in the profile feed? I had a customer that due to new GE profiles, their author policy stop working. We turned off the feed, and modify the profile, but wanted to see if there is anyway that we can give customer before new profile are sent thought the feed.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 20:39:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021293#M454222</guid>
      <dc:creator>Donald Fisher</dc:creator>
      <dc:date>2020-01-30T20:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: Profiler Feed</title>
      <link>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021413#M454223</link>
      <description>&lt;P&gt;The customer can do manual offline updates and verify any changes to profiling policies that they currently use before uploading to ISE.&amp;nbsp; It really isn't that often that you need to update profiling policies, especially in corporate environments that are relatively static.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 01:49:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021413#M454223</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2020-01-31T01:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: Profiler Feed</title>
      <link>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021419#M454224</link>
      <description>&lt;P&gt;Hi Donald,&lt;/P&gt;
&lt;P&gt;There is always a bit of risk in using the automated feed service updates on a production system. Ideally, you would want to test the feed service updates in a non-prod environment before updating them in production.&lt;/P&gt;
&lt;P&gt;Typically, there are two ways this is done by customers:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Disable the Online Subscription Update for the Feed Service in the Prod system. Allow a Non-Prod system to auto-update via the Feed Service and use the option to notify an Administrator via email when the update occurs. After testing in the Non-Prod environment, enable the Online Update in Prod and perform a manual update during a change window. Perform endpoint testing and back out (Undo Latest) the update if any issues are found.&lt;/LI&gt;
&lt;LI&gt;Disable the Online Subscription Update in the Prod system and use Offline updates. Register for the Offline Feed Service Management via &lt;A href="https://ise.cisco.com/partner/" target="_self"&gt;https://ise.cisco.com/partner&lt;/A&gt; and sign up for update notifications via email. When new updates are available, download and evaluate the XML file for any overlapping or conflicting profiler updates and test in Non-Prod (if possible). Perform the offline update during a change window, perform endpoint testing, and back out the update if any issues are found.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Greg&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 01:58:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021419#M454224</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2020-01-31T01:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: Profiler Feed</title>
      <link>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021432#M454225</link>
      <description>&lt;P&gt;My general recommendation for customers is that for any profiling policy that you are using to provide network access, leverage a custom made copy and following a naming standard indicating that it is self made.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;There have been a few issues in the past where the automated profiler feed update has burnt me in the same way you experienced.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 02:42:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiler-feed/m-p/4021432#M454225</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2020-01-31T02:42:02Z</dc:date>
    </item>
  </channel>
</rss>

