<?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 bluekeep in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-posture-bluekeep/m-p/3958388#M455771</link>
    <description>You should be able to approach this a couple ways. You could check for the presence of a file if you know what the fix includes.  An alternative would be to build a simple check for the existence of a registry key assuming the KB4499175 that fixes bluekeep generates one.  &lt;BR /&gt;&lt;BR /&gt;The challenge that might exist is if the fix for Bluekeep is found in multiple KB's.  KB4499175 is specifically the security only KB.</description>
    <pubDate>Thu, 14 Nov 2019 06:04:27 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2019-11-14T06:04:27Z</dc:date>
    <item>
      <title>ISE - Posture bluekeep</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-posture-bluekeep/m-p/3958228#M455669</link>
      <description>&lt;P&gt;Is there any way that through the ISE postures to verify if the windows are fitted with the patches to avoid bluekeep?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2019 20:32:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-posture-bluekeep/m-p/3958228#M455669</guid>
      <dc:creator>carlos.ibarra</dc:creator>
      <dc:date>2019-11-13T20:32:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Posture bluekeep</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-posture-bluekeep/m-p/3958388#M455771</link>
      <description>You should be able to approach this a couple ways. You could check for the presence of a file if you know what the fix includes.  An alternative would be to build a simple check for the existence of a registry key assuming the KB4499175 that fixes bluekeep generates one.  &lt;BR /&gt;&lt;BR /&gt;The challenge that might exist is if the fix for Bluekeep is found in multiple KB's.  KB4499175 is specifically the security only KB.</description>
      <pubDate>Thu, 14 Nov 2019 06:04:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-posture-bluekeep/m-p/3958388#M455771</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-11-14T06:04:27Z</dc:date>
    </item>
  </channel>
</rss>

