<?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 Disabling 1330 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/disabling-1330/m-p/659419#M88291</link>
    <description>&lt;P&gt;It seems that 1330 and other normalizer sigs are causing Cicso (and myself) some grief (as evident in CSCsc37875). I am wondering if I can just disable 1330 and all the subs entirely. I am seeing this sig (1330/14 in particular) fire alot. I set the action to either produce an alert or do nothing at all (no packet mod or denying or dropping) so I don't see the point of keeping 1330 enabled.&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 10:19:34 GMT</pubDate>
    <dc:creator>cniblo1975</dc:creator>
    <dc:date>2019-03-10T10:19:34Z</dc:date>
    <item>
      <title>Disabling 1330</title>
      <link>https://community.cisco.com/t5/network-security/disabling-1330/m-p/659419#M88291</link>
      <description>&lt;P&gt;It seems that 1330 and other normalizer sigs are causing Cicso (and myself) some grief (as evident in CSCsc37875). I am wondering if I can just disable 1330 and all the subs entirely. I am seeing this sig (1330/14 in particular) fire alot. I set the action to either produce an alert or do nothing at all (no packet mod or denying or dropping) so I don't see the point of keeping 1330 enabled.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:19:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-1330/m-p/659419#M88291</guid>
      <dc:creator>cniblo1975</dc:creator>
      <dc:date>2019-03-10T10:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling 1330</title>
      <link>https://community.cisco.com/t5/network-security/disabling-1330/m-p/659420#M88292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some of the 1330 signatures have additional internal functions, like queueing fragments for reassembly, so just turning them off is not recommended...in the extreme case you may just render your IPS into a wire.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following tunings were included as part of the S248 signature update and represent our suggested "minimal interference" settings that still let the IPS do its job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normalizer Neutering&lt;/P&gt;&lt;P&gt;SIGID.SUBSIG	ACTION&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1308		Disable&lt;/P&gt;&lt;P&gt;1311	Produce Alert ON, Deny_XXX OFF&lt;/P&gt;&lt;P&gt;1330.3                  "&lt;/P&gt;&lt;P&gt;1330.4                  "&lt;/P&gt;&lt;P&gt;1330.11                 "&lt;/P&gt;&lt;P&gt;1330.14                 "&lt;/P&gt;&lt;P&gt;1330.15		Disable&lt;/P&gt;&lt;P&gt;1330.16	Produce Alert ON, Deny_XXX OFF&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTML sort of killed the formatting...all lines with " are supposed to mean "same as above".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Obviously "Produce Alert" is up to you, but we think that these signatures, if firing, warrant some research into the cause.  Removing the Deny_whatever actions will keep the signature from interferring with the packets, yet still leave its other functionality enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Nov 2006 16:19:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-1330/m-p/659420#M88292</guid>
      <dc:creator>scothrel</dc:creator>
      <dc:date>2006-11-15T16:19:42Z</dc:date>
    </item>
  </channel>
</rss>

