<?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 Will ISE support vulnerability Info coming from FMC/FTD and TALOS? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/will-ise-support-vulnerability-info-coming-from-fmc-ftd-and/m-p/3450048#M529031</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As today ISE use 3rd Party to populate vulnerability information in order to create access rules based on endpoint status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firepower Management Center and Firepower Threat Defense sensors also have a similar information collected thru Network Discovery process, so it is logical to think we can use this same info also for ISE to create this vulnerability context without relying on a 3rd-party when the customer already has FTD/FMC deployed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any comments on that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Jun 2017 16:03:42 GMT</pubDate>
    <dc:creator>frbello</dc:creator>
    <dc:date>2017-06-19T16:03:42Z</dc:date>
    <item>
      <title>Will ISE support vulnerability Info coming from FMC/FTD and TALOS?</title>
      <link>https://community.cisco.com/t5/network-access-control/will-ise-support-vulnerability-info-coming-from-fmc-ftd-and/m-p/3450048#M529031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As today ISE use 3rd Party to populate vulnerability information in order to create access rules based on endpoint status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firepower Management Center and Firepower Threat Defense sensors also have a similar information collected thru Network Discovery process, so it is logical to think we can use this same info also for ISE to create this vulnerability context without relying on a 3rd-party when the customer already has FTD/FMC deployed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any comments on that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jun 2017 16:03:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/will-ise-support-vulnerability-info-coming-from-fmc-ftd-and/m-p/3450048#M529031</guid>
      <dc:creator>frbello</dc:creator>
      <dc:date>2017-06-19T16:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: Will ISE support vulnerability Info coming from FMC/FTD and TALOS?</title>
      <link>https://community.cisco.com/t5/network-access-control/will-ise-support-vulnerability-info-coming-from-fmc-ftd-and/m-p/3450049#M529034</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Freddy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately we can't discuss futures in this forum.&amp;nbsp; Today, ISE supports AMP, CTA and Qualys for threat / vulnerability information.&amp;nbsp; The integration between the two systems uses pxGrid for Rapid Threat Containment (RTC).&amp;nbsp; This allows FMC to subscribe to identity information ISE knows about and can also quarantine an endpoint if policy is violated.&amp;nbsp; Ultimately, it is a function of where you want the threat / vulnerability information displayed:&amp;nbsp; ISE or FMC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jun 2017 18:31:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/will-ise-support-vulnerability-info-coming-from-fmc-ftd-and/m-p/3450049#M529034</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2017-06-19T18:31:04Z</dc:date>
    </item>
  </channel>
</rss>

