<?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 Firesight detection engine in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997861#M1019270</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a case that a potential positive&amp;nbsp;injection using API related coding&amp;nbsp;was passing through our IPS, and no&amp;nbsp;intrusion event was seen on Intrusion event. I check the documentation and found out that snort combines signature, protocol and anomaly for inspection methods.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;what would be the possible reason that it happened? was the&amp;nbsp;attempt not matching any Snort rules for injection or 3 of the methods it use?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;any insight would be very helpful, Thanks!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 13:07:27 GMT</pubDate>
    <dc:creator>filterfilter</dc:creator>
    <dc:date>2019-03-12T13:07:27Z</dc:date>
    <item>
      <title>Firesight detection engine</title>
      <link>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997861#M1019270</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a case that a potential positive&amp;nbsp;injection using API related coding&amp;nbsp;was passing through our IPS, and no&amp;nbsp;intrusion event was seen on Intrusion event. I check the documentation and found out that snort combines signature, protocol and anomaly for inspection methods.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;what would be the possible reason that it happened? was the&amp;nbsp;attempt not matching any Snort rules for injection or 3 of the methods it use?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;any insight would be very helpful, Thanks!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:07:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997861#M1019270</guid>
      <dc:creator>filterfilter</dc:creator>
      <dc:date>2019-03-12T13:07:27Z</dc:date>
    </item>
    <item>
      <title>I would have guessed that it</title>
      <link>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997862#M1019271</link>
      <description>&lt;P&gt;I would have guessed that it passed because no rules specifically looking for your applications API exist.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You could write one of your own?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2016 15:17:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997862#M1019271</guid>
      <dc:creator>chris.proudlock</dc:creator>
      <dc:date>2016-09-12T15:17:33Z</dc:date>
    </item>
    <item>
      <title>Hello ,</title>
      <link>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997863#M1019272</link>
      <description>&lt;P&gt;Hello ,&lt;/P&gt;
&lt;P&gt;Its advisable that customers can create custom snort detection rules.&lt;/P&gt;
&lt;P&gt;Here are some helpful links.&lt;/P&gt;
&lt;P&gt;http://manual-snort-org.s3-website-us-east-1.amazonaws.com/node27.html&lt;/P&gt;
&lt;P&gt;Rate and mark correct the helpful posts&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Jetsy&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2016 13:19:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-detection-engine/m-p/2997863#M1019272</guid>
      <dc:creator>Jetsy Mathew</dc:creator>
      <dc:date>2016-09-13T13:19:05Z</dc:date>
    </item>
  </channel>
</rss>

