<?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 Fushar, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964974#M43582</link>
    <description>&lt;P&gt;Tushar,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Cisco ended up confirming for me that there is a bug related to this and they provide me with this link:&lt;/P&gt;
&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva18960&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;They also recommended updating the VDB version in FireSIGHT. As a workaround I did create a Network Access Policy where I disabled the "Challenge-Response Buffer Overflow" pre-processor rule in the Access Control Policy for certain IP addresses. This resolved&amp;nbsp;the issue.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Oct 2016 13:23:44 GMT</pubDate>
    <dc:creator>rweir0001</dc:creator>
    <dc:date>2016-10-06T13:23:44Z</dc:date>
    <item>
      <title>How to change preprocessor rules for specific server IP addresses in FireSIGHT?</title>
      <link>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964972#M43580</link>
      <description>&lt;P&gt;I have a Cisco ASA w/FirePOWER using SourceFire module version 5.4.1. The IPS is seeing SFTP traffic and misidentifying it as an&amp;nbsp; &lt;SPAN&gt;&lt;SPAN&gt;SSH_EVENT_RESPOVERFLOW intrusion event because it thinks the packets are trying to exploit a vulnerability in OpenSSH. The inline action is to drop the packets. I want to set it up so that the IPS will not drop these packets when it sees the traffic going to specific servers, but will function normally otherwise. I tried to change the&amp;nbsp;SSH_EVENT_RESPOVERFLOW rule in the Rule Editor but received this message:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;This preprocessor rule cannot be modified from the rule editor. If you want to modify this rule, you can change the settings in a Network Analysis policy for this preprocessor.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;How can I change the preprocessor rule so that the IPS doesn't drop packets that it misidentifies as&amp;nbsp;&lt;SPAN&gt;SSH_EVENT_RESPOVERFLOW intrusion events for SPECIFIC servers?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:41:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964972#M43580</guid>
      <dc:creator>rweir0001</dc:creator>
      <dc:date>2019-03-10T13:41:02Z</dc:date>
    </item>
    <item>
      <title>I also saw similar issue and</title>
      <link>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964973#M43581</link>
      <description>&lt;P&gt;I also saw similar issue and since NAP is globally applied hence the only way to do this is to whitelist the scanners in NAP.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Refer attached screenshot for same.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Oct 2016 07:04:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964973#M43581</guid>
      <dc:creator>tushar_bangia</dc:creator>
      <dc:date>2016-10-06T07:04:45Z</dc:date>
    </item>
    <item>
      <title>Fushar,</title>
      <link>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964974#M43582</link>
      <description>&lt;P&gt;Tushar,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Cisco ended up confirming for me that there is a bug related to this and they provide me with this link:&lt;/P&gt;
&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva18960&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;They also recommended updating the VDB version in FireSIGHT. As a workaround I did create a Network Access Policy where I disabled the "Challenge-Response Buffer Overflow" pre-processor rule in the Access Control Policy for certain IP addresses. This resolved&amp;nbsp;the issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Oct 2016 13:23:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-change-preprocessor-rules-for-specific-server-ip/m-p/2964974#M43582</guid>
      <dc:creator>rweir0001</dc:creator>
      <dc:date>2016-10-06T13:23:44Z</dc:date>
    </item>
  </channel>
</rss>

