<?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 Firepower False Positves in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-false-positves/m-p/2987689#M43240</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We currently have a mix of Linux and Windows servers that are behind our Firepower/ASA devices. &amp;nbsp;We're seeing an uptick in the BASH signatures firing (1:31977 and 1:31978 specifically). &amp;nbsp;The problem is while it is an older rule, we don't want to disable it completely. &amp;nbsp;We would like to be alerted when it fires on a Linux host, but not Windows hosts. &amp;nbsp;Currently it's firing on Windows and Linux and it's creating a bit of a headache.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was hoping to get some suggestions on how to proceed. &amp;nbsp;I know I can setup supression or create a new snort variable without the windows host, but I'd like to have the fix with minimal overhead/configuration. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 13:45:06 GMT</pubDate>
    <dc:creator>croll9898</dc:creator>
    <dc:date>2019-03-10T13:45:06Z</dc:date>
    <item>
      <title>Firepower False Positves</title>
      <link>https://community.cisco.com/t5/network-security/firepower-false-positves/m-p/2987689#M43240</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We currently have a mix of Linux and Windows servers that are behind our Firepower/ASA devices. &amp;nbsp;We're seeing an uptick in the BASH signatures firing (1:31977 and 1:31978 specifically). &amp;nbsp;The problem is while it is an older rule, we don't want to disable it completely. &amp;nbsp;We would like to be alerted when it fires on a Linux host, but not Windows hosts. &amp;nbsp;Currently it's firing on Windows and Linux and it's creating a bit of a headache.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was hoping to get some suggestions on how to proceed. &amp;nbsp;I know I can setup supression or create a new snort variable without the windows host, but I'd like to have the fix with minimal overhead/configuration. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:45:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-false-positves/m-p/2987689#M43240</guid>
      <dc:creator>croll9898</dc:creator>
      <dc:date>2019-03-10T13:45:06Z</dc:date>
    </item>
    <item>
      <title>Can you check the connection</title>
      <link>https://community.cisco.com/t5/network-security/firepower-false-positves/m-p/2987690#M43241</link>
      <description>&lt;P&gt;Can you check the connection events of the intrusion events to see what application id and web application id are identified for those 2 events?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You can create 2 new rules to include a more specific web application identification, if the windows servers are identified different.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Or, you can add the windows servers IP addresses into an object and apply a different IPS policy with the rules disabled only on those IP addresses (with a separate ACP rule that matches the object).&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 09:31:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-false-positves/m-p/2987690#M43241</guid>
      <dc:creator>Claudiu Cismaru</dc:creator>
      <dc:date>2017-01-25T09:31:14Z</dc:date>
    </item>
  </channel>
</rss>

