<?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: Compromised host FMC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762225#M984154</link>
    <description>sfr acl. but I still see it on the fmc logs.</description>
    <pubDate>Wed, 12 Dec 2018 18:01:18 GMT</pubDate>
    <dc:creator>Steven Williams</dc:creator>
    <dc:date>2018-12-12T18:01:18Z</dc:date>
    <item>
      <title>Compromised host FMC</title>
      <link>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762158#M983803</link>
      <description>&lt;P&gt;I have users trying to access a host that is showing up in FMC events with "red" computer icon which means compromised. The action is allowed in the event log. I have also added this host to bypass the sfr and i still the client getting tcp resets to this host from splunk. How do I fix this?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:34:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762158#M983803</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2020-02-21T16:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: Compromised host FMC</title>
      <link>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762210#M983814</link>
      <description>How you bypass the client....&lt;BR /&gt;Did you whitelist the IP or excluded the IP from the sfr acl.</description>
      <pubDate>Wed, 12 Dec 2018 17:47:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762210#M983814</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2018-12-12T17:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: Compromised host FMC</title>
      <link>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762225#M984154</link>
      <description>sfr acl. but I still see it on the fmc logs.</description>
      <pubDate>Wed, 12 Dec 2018 18:01:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/compromised-host-fmc/m-p/3762225#M984154</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2018-12-12T18:01:18Z</dc:date>
    </item>
  </channel>
</rss>

