<?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: ISE posture condition - emergency security update in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3993213#M455496</link>
    <description>&lt;P&gt;Answer I got from internal community:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Don't have data on the emergency patch. Assume the same schedule as regular Tuesday patches. Also note that we generally recommend WSUS or SMS for patch management instead of ISE so customer do not have to maintain separate patch repositories.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Dec 2019 02:57:45 GMT</pubDate>
    <dc:creator>lul3</dc:creator>
    <dc:date>2019-12-04T02:57:45Z</dc:date>
    <item>
      <title>ISE posture condition - emergency security update</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3987177#M455494</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I went through some tracks and understand that it takes around 3 days for ISE to update the posture condition based on MS KB update: &lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/how-often-does-ise-get-posture-update-for-hotfix-conditions/td-p/3850995" target="_blank"&gt;https://community.cisco.com/t5/identity-services-engine-ise/how-often-does-ise-get-posture-update-for-hotfix-conditions/td-p/3850995&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;May I check if this apply to the MS emergency security update as well? If MS release a&amp;nbsp; emergency update - what is the suggestion for customer to get the updated policy?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 11:43:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3987177#M455494</guid>
      <dc:creator>lul3</dc:creator>
      <dc:date>2019-11-21T11:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE posture condition - emergency security update</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3987967#M455495</link>
      <description>I see you asked this internally. Please update when you find the answer from the product managers</description>
      <pubDate>Fri, 22 Nov 2019 16:16:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3987967#M455495</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-11-22T16:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: ISE posture condition - emergency security update</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3993213#M455496</link>
      <description>&lt;P&gt;Answer I got from internal community:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Don't have data on the emergency patch. Assume the same schedule as regular Tuesday patches. Also note that we generally recommend WSUS or SMS for patch management instead of ISE so customer do not have to maintain separate patch repositories.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 02:57:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-posture-condition-emergency-security-update/m-p/3993213#M455496</guid>
      <dc:creator>lul3</dc:creator>
      <dc:date>2019-12-04T02:57:45Z</dc:date>
    </item>
  </channel>
</rss>

