<?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: Firepower: How to block traffic from PCs running Windows XP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3185028#M1066088</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/178747"&gt;@Flavio Miranda&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I don't see how a URL rule can block traffic base on initiator operating system.&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/289964"&gt;@cisco&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I haven't done this and Firepower doesn't&amp;nbsp;make it easy but I believe you can use a Correlation Policy. You have to build a traffic profile and then a rule and finally a correlation policy that uses those building blocks and assign&amp;nbsp;an action (i.e. Blacklist). However, Firepower has to be in a location to see the traffic with enough detail to authoritatively identify the OS. That can be problematic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This sort of thing can be done better and more easily with Cisco ISE as its built-in profiling&amp;nbsp;(a Plus license feature) is much more precise. It can then assign a downloadable&amp;nbsp;ACL (DACL) dynamically to prevent Internet access while allowing all other internal access at the switchport (or Wireless client) level.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 16 Sep 2017 15:10:39 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2017-09-16T15:10:39Z</dc:date>
    <item>
      <title>Firepower: How to block traffic from PCs running Windows XP</title>
      <link>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3184589#M1066086</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a ASA 5525-X with Firepower. We still have some computers in our networks running Windows XP and I would like to block Internet-traffic from these computers. Of course I can maintain the IP-addresses in an access-list and block the traffic that way, but is it possible to do this more dynamic by using Firepower?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Thor-Egil Ekeli&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:18:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3184589#M1066086</guid>
      <dc:creator>cisco</dc:creator>
      <dc:date>2020-02-21T14:18:32Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower: How to block traffic from PCs running Windows XP</title>
      <link>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3184707#M1066087</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Sure it is. Follows the steps:&lt;/P&gt;&lt;P&gt;1-Configure URL objects/group under Object &amp;gt; Object Management&lt;BR /&gt;2-Create rule under Access Control policy calling the URL object created&lt;BR /&gt;3-Deploy the policy on the targe device.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2017 14:20:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3184707#M1066087</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-09-15T14:20:07Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower: How to block traffic from PCs running Windows XP</title>
      <link>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3185028#M1066088</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/178747"&gt;@Flavio Miranda&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I don't see how a URL rule can block traffic base on initiator operating system.&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/289964"&gt;@cisco&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I haven't done this and Firepower doesn't&amp;nbsp;make it easy but I believe you can use a Correlation Policy. You have to build a traffic profile and then a rule and finally a correlation policy that uses those building blocks and assign&amp;nbsp;an action (i.e. Blacklist). However, Firepower has to be in a location to see the traffic with enough detail to authoritatively identify the OS. That can be problematic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This sort of thing can be done better and more easily with Cisco ISE as its built-in profiling&amp;nbsp;(a Plus license feature) is much more precise. It can then assign a downloadable&amp;nbsp;ACL (DACL) dynamically to prevent Internet access while allowing all other internal access at the switchport (or Wireless client) level.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Sep 2017 15:10:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-how-to-block-traffic-from-pcs-running-windows-xp/m-p/3185028#M1066088</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-09-16T15:10:39Z</dc:date>
    </item>
  </channel>
</rss>

