<?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 Access Control Policy is the in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583104#M1028384</link>
    <description>&lt;P&gt;Access Control Policy is the way to do it. &amp;nbsp;What you described should work, there is likely some issue with the rules &amp;nbsp;- either the rule criteria or the rule order - that is causing this.&lt;/P&gt;</description>
    <pubDate>Fri, 12 Dec 2014 21:45:40 GMT</pubDate>
    <dc:creator>atatistc</dc:creator>
    <dc:date>2014-12-12T21:45:40Z</dc:date>
    <item>
      <title>Sourcefire File Malware Lookup Bypass</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583103#M1028380</link>
      <description>&lt;P&gt;I am currently looking for a way to exlude IP's from the Malware File lookup on a perimeter 3D sensor but am not having much luck.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, there are Windows patches and other trusted file deployment events that go through the sensor to multiple systems and it is causing a large number of file lookup events (from the malware protection license functionality). I have tried adding a rule in the Access Control policy that is src the patch server and dst any allow with either a blank file lookup policy defined in the rule, or it set to "none". However the systems are still generating large numbers of file lookup events.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone had any luck with this?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 12:36:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583103#M1028380</guid>
      <dc:creator>mvollersf</dc:creator>
      <dc:date>2019-03-12T12:36:05Z</dc:date>
    </item>
    <item>
      <title>Access Control Policy is the</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583104#M1028384</link>
      <description>&lt;P&gt;Access Control Policy is the way to do it. &amp;nbsp;What you described should work, there is likely some issue with the rules &amp;nbsp;- either the rule criteria or the rule order - that is causing this.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Dec 2014 21:45:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583104#M1028384</guid>
      <dc:creator>atatistc</dc:creator>
      <dc:date>2014-12-12T21:45:40Z</dc:date>
    </item>
    <item>
      <title>Thanks atatistc, I was silly</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583105#M1028389</link>
      <description>&lt;P&gt;Thanks atatistc, I was silly and put the location being downloaded from as src in the AC rule, but connection events showed its a pull function initiated from the clients, after correcting that it seems to be working as expected.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jan 2015 21:46:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-file-malware-lookup-bypass/m-p/2583105#M1028389</guid>
      <dc:creator>mvollersf</dc:creator>
      <dc:date>2015-01-08T21:46:44Z</dc:date>
    </item>
  </channel>
</rss>

