<?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 Using Firepower's Geolocation DB in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503100#M1085110</link>
    <description>&lt;P&gt;We are thinking of using Firepower's Geolocation database to block all incoming IP traffic from both China and Russia. My organization has no business dealing with any of those countries. That is not to say we do not see any traffic already blocked from both of those countries. We get lots of "dropped traffic from both in our logs. Has anyone else tried using this as a basis for a rule in their access policies? Are there any drawbacks to doing this?&lt;/P&gt;</description>
    <pubDate>Mon, 15 Nov 2021 18:11:07 GMT</pubDate>
    <dc:creator>ethutchinson</dc:creator>
    <dc:date>2021-11-15T18:11:07Z</dc:date>
    <item>
      <title>Using Firepower's Geolocation DB</title>
      <link>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503100#M1085110</link>
      <description>&lt;P&gt;We are thinking of using Firepower's Geolocation database to block all incoming IP traffic from both China and Russia. My organization has no business dealing with any of those countries. That is not to say we do not see any traffic already blocked from both of those countries. We get lots of "dropped traffic from both in our logs. Has anyone else tried using this as a basis for a rule in their access policies? Are there any drawbacks to doing this?&lt;/P&gt;</description>
      <pubDate>Mon, 15 Nov 2021 18:11:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503100#M1085110</guid>
      <dc:creator>ethutchinson</dc:creator>
      <dc:date>2021-11-15T18:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Using Firepower's Geolocation DB</title>
      <link>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503155#M1085114</link>
      <description>&lt;P&gt;I do not see any issue here, that is the purpose of the FW it should be the job as mentioned.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Nov 2021 19:36:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503155#M1085114</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2021-11-15T19:36:53Z</dc:date>
    </item>
    <item>
      <title>Re: Using Firepower's Geolocation DB</title>
      <link>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503368#M1085126</link>
      <description>&lt;P&gt;It's a common use case and I've used it successfully for multiple customers for both outgoing and incoming rules.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Nov 2021 07:47:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-firepower-s-geolocation-db/m-p/4503368#M1085126</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-11-16T07:47:40Z</dc:date>
    </item>
  </channel>
</rss>

