<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Suricata on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/suricata/</link>
    <description>Recent content in Suricata on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Wed, 18 Feb 2015 10:44:41 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/suricata/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Slides of my talks at Lecce</title>
      <link>https://home.regit.org/2015/02/slides-of-my-talks-at-lecce/</link>
      <pubDate>Wed, 18 Feb 2015 10:44:41 +0000</pubDate>
      <guid>https://home.regit.org/2015/02/slides-of-my-talks-at-lecce/</guid>
      <description>&lt;p&gt;I’ve been invited by &lt;a href=&#34;http://salug.it/Eric_Leblond/&#34;&gt;SaLUG&lt;/a&gt; to Lecce to give some talks during their Geek Evening. I’ve done a talk on nftables and one of suricata.&lt;figure id=&#34;attachment_2188&#34; aria-describedby=&#34;caption-attachment-2188&#34; style=&#34;width: 695px&#34; class=&#34;wp-caption aligncenter&#34;&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2015/02/DSC_5136_01.jpg&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2015/02/DSC_5136_01-1024x679.jpg&#34; alt=&#34;Lecce by night&#34; width=&#34;695&#34; height=&#34;460&#34; class=&#34;size-large wp-image-2188&#34; srcset=&#34;https://home.regit.org/uploads/2015/02/DSC_5136_01-1024x679.jpg 1024w, https://home.regit.org/uploads/2015/02/DSC_5136_01-300x199.jpg 300w, https://home.regit.org/uploads/2015/02/DSC_5136_01.jpg 2000w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;figcaption id=&#34;caption-attachment-2188&#34; class=&#34;wp-caption-text&#34;&gt;Lecce by night&lt;/figcaption&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;The nftables talk was about the motivation behind the change from iptables.&lt;/p&gt;
&lt;p&gt;Here are the slides: &lt;a href=&#34;https://home.regit.org/uploads/2015/02/nftables.pdf&#34;&gt;Nftables&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The talk on Suricata was explaining the different feature of Suricata and was showing how I’ve used it to make a study of SSH bruteforce.&lt;/p&gt;</description>
    </item>
    <item>
      <title>pshitt: collect passwords used in SSH bruteforce</title>
      <link>https://home.regit.org/2014/06/pshitt-collect-passwords-used-in-ssh-bruteforce/</link>
      <pubDate>Thu, 26 Jun 2014 08:41:02 +0000</pubDate>
      <guid>https://home.regit.org/2014/06/pshitt-collect-passwords-used-in-ssh-bruteforce/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;I’ve been playing lately on &lt;a href=&#34;https://home.regit.org/2014/02/chinese-scanner/&#34;&gt;analysis SSH bruteforce caracterization&lt;/a&gt;. I was a bit frustrated of just getting partial information:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ulogd can give information about scanner settings&lt;/li&gt;
&lt;li&gt;suricata can give me information about software version&lt;/li&gt;
&lt;li&gt;sshd server logs shows username&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But having username without having the password is really frustrating.&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;So I decided to try to get them. Looking for a SSH server honeypot, I did find &lt;a href=&#34;https://github.com/desaster/kippo&#34;&gt;kippo&lt;/a&gt; but it was going too far for me&lt;br&gt;
by providing a fake shell access. So I’ve decided to build my own based on &lt;a href=&#34;https://github.com/paramiko/paramiko&#34;&gt;paramiko&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata and Ulogd meet Logstash and Splunk</title>
      <link>https://home.regit.org/2014/03/suricata-ulogd-splunk-logstash/</link>
      <pubDate>Fri, 07 Mar 2014 23:19:37 +0000</pubDate>
      <guid>https://home.regit.org/2014/03/suricata-ulogd-splunk-logstash/</guid>
      <description>&lt;h4 id=&#34;some-progress-on-the-json-side&#34;&gt;Some progress on the JSON side&lt;/h4&gt;
&lt;p&gt;Suricata 2.0-rc2 is out and it brings some progress on the JSON side. The logging of SSH protocol has been added:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021.png&#34; alt=&#34;Screenshot from 2014-03-07 18:50:21&#34; width=&#34;629&#34; height=&#34;357&#34; class=&#34;aligncenter size-large wp-image-2051&#34; srcset=&#34;https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021.png 629w, https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021-300x170.png 300w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;and the &lt;a href=&#34;https://github.com/inliniac/suricata/commit/6c3c234ca5583f420371bc706716e8ae1b0c5a61&#34;&gt;format of timestamp has been updated&lt;/a&gt; to be ISO 8601 compliant and it is now named &lt;code&gt;timestamp&lt;/code&gt; instead of &lt;code&gt;time&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata and Nftables</title>
      <link>https://home.regit.org/2014/02/suricata-and-nftables/</link>
      <pubDate>Wed, 05 Feb 2014 09:03:28 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/suricata-and-nftables/</guid>
      <description>&lt;h4 id=&#34;iptables-and-suricata-as-ips&#34;&gt;Iptables and suricata as IPS&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/2011/01/building-a-suricata-compliant-ruleset/&#34;&gt;Building a Suricata ruleset&lt;/a&gt; with iptables has always been a complicated task when trying to combined the rules that are necessary for the IPS with the firewall rules. Suricata has always used &lt;a href=&#34;https://home.regit.org/2011/04/some-new-features-of-ips-mode-in-suricata-1-1beta2/&#34;&gt;Netfilter advanced features&lt;/a&gt; allowing some more or less tricky methods to be used.&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;For the one not familiar with IPS using Netfilter, here’s a few starting points:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;IPS receives the packet coming from kernel via rules using the NFQUEUE target&lt;/li&gt;
&lt;li&gt;The IPS must received all packets of a given flow to be able to handle detection cleanly&lt;/li&gt;
&lt;li&gt;The NFQUEUE target is a terminal target: when the IPS verdicts a packet, it is or accepted (and leave current chain) &lt;/ol&gt; &lt;/p&gt;</description>
    </item>
    <item>
      <title>Investigation on an attack tool used in China</title>
      <link>https://home.regit.org/2014/02/chinese-scanner/</link>
      <pubDate>Sun, 02 Feb 2014 15:28:32 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/chinese-scanner/</guid>
      <description>&lt;h4 id=&#34;log-analysis-experiment&#34;&gt;Log analysis experiment&lt;/h4&gt;
&lt;p&gt;I’ve been playing lately with &lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt; using data from the &lt;a href=&#34;http://git.netfilter.org/ulogd2/commit/?id=e0ae1870e5b15138c12071d9d96522a2720bf44a&#34;&gt;ulogd JSON output plugin&lt;/a&gt; and the &lt;a href=&#34;http://pevma.blogspot.fr/2014/02/suricata-idps-and-common-information.html&#34;&gt;Suricata full JSON output&lt;/a&gt; as well as standard system logs.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png&#34; alt=&#34;Screenshot from 2014-02-02 13:22:34&#34; width=&#34;695&#34; height=&#34;329&#34; class=&#34;aligncenter size-large wp-image-1896&#34; srcset=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png 1024w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-300x142.png 300w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png 1898w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Ulogd is getting Netfilter firewall logs from Linux kernel and is writing them in JSON format. Suricata is doing the same with alert and other traces. Logstash is getting both log as well as sytem log. This allows to create some dashboard with information coming from multiple sources. If you want to know how to configure ulogd for JSON output check &lt;a href=&#34;https://home.regit.org/2014/02/using-ulogd-and-json-output/&#34;&gt;this post&lt;/a&gt;. For suricata, you can have a look at &lt;a href=&#34;https://home.regit.org/2014/01/a-bit-of-logstash-cooking/&#34;&gt;this one&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using linux perf tools for Suricata performance analysis</title>
      <link>https://home.regit.org/2013/11/using-linux-perf-tools-for-suricata-performance-analysis/</link>
      <pubDate>Mon, 18 Nov 2013 12:59:59 +0000</pubDate>
      <guid>https://home.regit.org/2013/11/using-linux-perf-tools-for-suricata-performance-analysis/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://perf.wiki.kernel.org/index.php/Main_Page&#34;&gt;Perf&lt;/a&gt; is a great tool to analyse performances on Linux boxes. For example, &lt;em&gt;perf top&lt;/em&gt; will give you this type of output on a box running &lt;a href=&#34;http://suricata-ids.org/&#34;&gt;Suricata&lt;/a&gt; on a high speed network:&lt;/p&gt;
&lt;pre&gt;Events: 32K cycles                                                                                                                                                                                                                            
 28.41%  suricata            [.] SCACSearch
 19.86%  libc-2.15.so        [.] tolower
 17.83%  suricata            [.] SigMatchSignaturesBuildMatchArray
  6.11%  suricata            [.] SigMatchSignaturesBuildMatchArrayAddSignature
  2.06%  suricata            [.] tolower@plt
  1.70%  libpthread-2.15.so  [.] pthread_mutex_trylock
  1.17%  suricata            [.] StreamTcpGetFlowState
  1.10%  libc-2.15.so        [.] __memcpy_ssse3_back
  0.90%  libpthread-2.15.so  [.] pthread_mutex_lock&lt;/pre&gt;
&lt;p&gt;The functions are sorted by CPU consumption. Using arrow key it is possible to jump into the annotated code to see where most CPU cycles are used.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Logstash and Suricata for the old guys</title>
      <link>https://home.regit.org/2013/10/logstash-and-suricata-for-the-old-guys/</link>
      <pubDate>Mon, 28 Oct 2013 10:47:31 +0000</pubDate>
      <guid>https://home.regit.org/2013/10/logstash-and-suricata-for-the-old-guys/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt; an opensource tool for managing events and logs. It is using &lt;a href=&#34;http://www.elasticsearch.org/&#34;&gt;elasticsearch&lt;/a&gt; for the storage and has a really nice interface named &lt;a href=&#34;http://www.elasticsearch.org/overview/kibana/&#34;&gt;Kibana&lt;/a&gt;. One of the easiest to use entry format is JSON.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.suricata-ids.org&#34;&gt;Suricata&lt;/a&gt; is an IDS/IPS which has some interesting logging features. Version 2.0 will feature a JSON export for all logging subsystem. It will then be possible to output in JSON format:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;HTTP log&lt;/li&gt;
&lt;li&gt;DNS log&lt;/li&gt;
&lt;li&gt;TLS log&lt;/li&gt;
&lt;li&gt;File log&lt;/li&gt;
&lt;li&gt;IDS Alerts&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For now, only File log is available in JSON format. This extract meta data from files transferred over HTTP.&lt;/p&gt;</description>
    </item>
    <item>
      <title>WiFi interface and suricata AF_PACKET IPS mode</title>
      <link>https://home.regit.org/2013/03/wifi-interface-and-suricata-af_packet-ips-mode/</link>
      <pubDate>Tue, 26 Mar 2013 15:24:45 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/wifi-interface-and-suricata-af_packet-ips-mode/</guid>
      <description>&lt;h4 id=&#34;not-usual-setup-can-lead-to-surprise&#34;&gt;Not usual setup can lead to surprise&lt;/h4&gt;
&lt;p&gt;The 5th of December 2012, I’ve setup suricata in AF_PACKET IPS mode between a WiFi interface and an Ethernet interface. The result was surprising as it was leading to a crash after some time:&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2013/03/IMG_20130326_150421.jpg&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2013/03/IMG_20130326_150421-300x225.jpg&#34; alt=&#34;&#34; title=&#34;IMG_20130326_150421&#34; width=&#34;300&#34; height=&#34;225&#34; class=&#34;aligncenter size-medium wp-image-1613&#34; srcset=&#34;https://home.regit.org/uploads/2013/03/IMG_20130326_150421-300x225.jpg 300w, https://home.regit.org/uploads/2013/03/IMG_20130326_150421-1024x768.jpg 1024w&#34; sizes=&#34;auto, (max-width: 300px) 85vw, 300px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The issue was linked with the defrag option of AF_PACKEt fanout. I’ve proposed a &lt;a href=&#34;http://comments.gmane.org/gmane.linux.network/251955&#34;&gt;patch the 7th Dec 2012&lt;/a&gt; and after a discussion with David Miller and Johannes Berg, Johannes has proposed a &lt;a href=&#34;https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1bf3751ec90cc3174e01f0d701e8449ce163d113&#34;&gt;better patch which was included in official tree&lt;/a&gt;. So the problem is fixed for kernel superior or equal to 3.7.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Victor Julien, Suricata and Netfilter</title>
      <link>https://home.regit.org/2013/03/victor-julien-suricata-and-netfilter/</link>
      <pubDate>Mon, 11 Mar 2013 15:04:14 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/victor-julien-suricata-and-netfilter/</guid>
      <description>&lt;p&gt;Suricata and Netfilter can be better friend as they are doing some common work like decoding packet and maintaining flow table.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2013/03/DSC_5419.jpg&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2013/03/DSC_5419.jpg&#34; alt=&#34;&#34; title=&#34;Victor Julien&#34; width=&#34;800&#34; height=&#34;531&#34; class=&#34;aligncenter size-full wp-image-1547&#34; srcset=&#34;https://home.regit.org/uploads/2013/03/DSC_5419.jpg 800w, https://home.regit.org/uploads/2013/03/DSC_5419-300x199.jpg 300w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In IPS mode, Suricata is receiving raw packet from libnetfilter_queue. It has to made the parsing of this packet but this kind of thing has also been done by kernel. So it should be possible to avoid to duplicate the work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some statistics about Suricata 1.4</title>
      <link>https://home.regit.org/2012/12/some-statistics-about-suricata-1-4/</link>
      <pubDate>Thu, 13 Dec 2012 16:11:00 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/some-statistics-about-suricata-1-4/</guid>
      <description>&lt;h4 id=&#34;a-huge-work&#34;&gt;A huge work&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://suricata-ids.org/2012/12/13/suricata-1-4-released/&#34;&gt;Suricata 1.4&lt;/a&gt; has been released December 13th 2012 and it has been a huge work. The number of modifications is just impressing:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;390 files changed, 25299 insertions(+), 11982 deletions(-)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The following video is using &lt;a href=&#34;http://code.google.com/p/gource/&#34;&gt;gource&lt;/a&gt; to display the evolution of Suricata IDS/IPS source code between version 1.3 and version 1.4. It only displays the modified files and do not show the files existing at start.&lt;/p&gt;
&lt;h5 id=&#34;a-collaborative-work&#34;&gt;A collaborative work&lt;/h5&gt;
&lt;p&gt;A total of 11 different authors have participated to this release. The following graph generated by &lt;a href=&#34;http://gitstats.sourceforge.net/&#34;&gt;gitstats&lt;/a&gt; shows the number of lines of code by author:&lt;/p&gt;</description>
    </item>
    <item>
      <title>About Suricata and a kernel oops in AF_PACKET</title>
      <link>https://home.regit.org/2012/12/af-packet-oops/</link>
      <pubDate>Wed, 05 Dec 2012 10:38:19 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/af-packet-oops/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Kernel oops have been reported by some users running Suricata with AF_PACKET multiple thread capture activated. This is due to a bug I’ve introduced in AF_PACKET when fixing an other bug.&lt;/p&gt;
&lt;h4 id=&#34;which-kernel-not-to-use-with-suricata-in-af_packet-mode&#34;&gt;Which kernel not to use with Suricata in AF_PACKET mode&lt;/h4&gt;
&lt;p&gt;The following kernel version will surely crash if Suricata or any other program is used with &lt;strong&gt;AF_PACKET&lt;/strong&gt; capture &lt;strong&gt;with multiple capture threads&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Linux 3.2.30 to 3.2.33&lt;/li&gt;
&lt;li&gt;Linux 3.4.12 to 3.4.18&lt;/li&gt;
&lt;li&gt;Linux 3.5.5 to 3.5.7&lt;/li&gt;
&lt;li&gt;Linux 3.6.0 to 3.6.6&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If only one capture thread is used there is no risk of crash. If you are running a vulnerable kernel, your configuration should looks like:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flow reconstruction and normalization in Suricata</title>
      <link>https://home.regit.org/2012/11/suricata-flow-reconstruction/</link>
      <pubDate>Thu, 15 Nov 2012 17:36:06 +0000</pubDate>
      <guid>https://home.regit.org/2012/11/suricata-flow-reconstruction/</guid>
      <description>&lt;p&gt;The naive approach would consider that an IDS is just taking packet and doing a lot of matching on it. In fact, this is not at all what is happening. An IDS/IPS like Suricata is in fact rebuilding the data stream and in case of known protocols it is even normalizing the data stream and providing keyword which can be used to match on specific field of a protocol.&lt;/p&gt;
&lt;p&gt;Let’s say, we a rule to match on a HTTP request where method is GET and the URL is “/download.php”.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Display suricata signatures in Latex</title>
      <link>https://home.regit.org/2012/10/display-suricata-signatures-in-latex/</link>
      <pubDate>Tue, 23 Oct 2012 18:04:11 +0000</pubDate>
      <guid>https://home.regit.org/2012/10/display-suricata-signatures-in-latex/</guid>
      <description>&lt;p href=&#34;http://en.wikibooks.org/wiki/LaTeX/Packages/Listings&#34;&gt;
  lstlisting&lt;/a&gt; is a convenient way to display code when using latex. It has no definition for suricata rules language and I&amp;#8217;ve cooked one:
&lt;/p&gt;
&lt;pre&gt;\lstdefinelanguage{suricata}
{morekeywords= {alert, tcp, http, tls, ip, ipv4, ipv4, drop, pass, sid, priority, rev, classtype, threshold, metadata, reference, tag, msg, content, uricontent, pcre, ack, seq, depth, distance, within, offset, replace, nocase, fast\_pattern, rawbytes, byte\_test, byte\_jump, sameip, ip\_proto, flow, window, ftpbounce, isdataat, id, rpc, dsize, flowvar, flowint, pktvar, noalert, flowbits, stream\_size, ttl, itype, icode, tos, icmp\_id, icmp\_seq, detection\_filter, ipopts, flags, fragbits, fragoffset, gid, nfq\_set\_mark, tls.version, tls.subject, tls.issuerdn, tls.fingerprint, tls.store, http\_cookie, http\_method, urilen, http\_client\_body, http\_server\_body, http\_header, http\_raw\_header, http\_uri, http\_raw\_uri, http\_stat\_msg, http\_stat\_code, http\_user\_agent, ssh.protoversion, ssh.softwareversion, ssl\_version, ssl\_state, byte\_extract, file\_data, dce\_iface, dce\_opnum, dce\_stub\_data, asn1, filename, fileext, filestore, filemagic, filemd5, filesize, l3\_proto, luajit},
otherkeywords={ipv4-csum, tcpv4-csum, tcpv6-csum, udpv4-csum, udpv6-csum, icmpv4-csum, icmpv6-csum, decode-event, app-layer-event, engine-event, stream-event},
sensitive=true,
morecomment=[l]{//},
morecomment=[s]{/*}{*/},
morestring=[b]&#34;,
}
&lt;/pre&gt;
&lt;p&gt;To use it, you can simply add this code at start of your tex file and you can then use it:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Defend your network from Microsoft Word upload with Suricata and Netfilter</title>
      <link>https://home.regit.org/2012/10/defend-your-network-from-word/</link>
      <pubDate>Tue, 09 Oct 2012 14:17:13 +0000</pubDate>
      <guid>https://home.regit.org/2012/10/defend-your-network-from-word/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Some times ago, I’ve blogged about &lt;a href=&#34;https://home.regit.org/2011/04/some-new-features-of-ips-mode-in-suricata-1-1beta2/&#34;&gt;new IPS features in Suricata 1.1&lt;/a&gt; and did not find at the time&lt;br&gt;
any killer application of the &lt;em&gt;nfq_set_mark&lt;/em&gt; keyword. When using Suricata in Netfilter IPS mode, this keyword allows you to set the Netfilter mark on the packet when a rule match.&lt;br&gt;
This mark can be used by Netfilter or by other network subsystem to differentiate the treatment to apply to the packet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A new unix command mode in Suricata</title>
      <link>https://home.regit.org/2012/09/a-new-unix-command-mode-in-suricata/</link>
      <pubDate>Tue, 18 Sep 2012 22:21:05 +0000</pubDate>
      <guid>https://home.regit.org/2012/09/a-new-unix-command-mode-in-suricata/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;I’ve been working for the past few days on a new Suricata feature. It is available in &lt;a href=&#34;http://suricata-ids.org/2012/11/29/suricata-1-4rc1-available/&#34;&gt;Suricata 1.4rc1&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Suricata can now listen to a unix socket and accept commands from the user. The exchange protocol is JSON-based and the format of the message has been done to be generic and it is described in this &lt;a href=&#34;https://github.com/regit/suricata/commit/1a58eec318a842834a9252fbf4961a392cbad8a8&#34;&gt;commit message&lt;/a&gt;. An example script called &lt;em&gt;suricatasc&lt;/em&gt; is provided in the source and installed automatically when updating Suricata.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New AF_PACKET IPS mode in Suricata</title>
      <link>https://home.regit.org/2012/09/new-af_packet-ips-mode-in-suricata/</link>
      <pubDate>Tue, 04 Sep 2012 20:53:53 +0000</pubDate>
      <guid>https://home.regit.org/2012/09/new-af_packet-ips-mode-in-suricata/</guid>
      <description>&lt;h4 id=&#34;a-new-suricata-ips-mode&#34;&gt;A new Suricata IPS mode&lt;/h4&gt;
&lt;p&gt;Suricata IPS capabilities are not new. It is possible to use Suricata with Netfilter or ipfw to build a state-of-the-art IPS. On Linux, this system has not the best throughput performance. Patrick McHardy’s work on &lt;a href=&#34;https://lwn.net/Articles/512442/&#34;&gt;netlink: memory mapped I/O&lt;/a&gt; should bring some real improvement but this is not yet available.&lt;/p&gt;
&lt;p&gt;I’ve thus decided to do an implementation of IPS based on AF_PACKET (read raw socket). The idea is based on one of the snort’s running mode. It peers two network interfaces and all packets received from one interface are sent to the other interface (if a signature with drop keyword does not fired on the packet). This requires to dedicate two network interfaces for Suricata but this provide a simple bridge system. As suricata is using latest AF_PACKET features (read load balancing), it was possible to build something really promising.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata new TLS fingerprint and TLS store keywords.</title>
      <link>https://home.regit.org/2012/08/tls-fingerprint-store/</link>
      <pubDate>Mon, 27 Aug 2012 17:10:49 +0000</pubDate>
      <guid>https://home.regit.org/2012/08/tls-fingerprint-store/</guid>
      <description>&lt;h4 id=&#34;suricata-tls-support&#34;&gt;Suricata TLS support&lt;/h4&gt;
&lt;p&gt;Victor Julien has just &lt;a href=&#34;https://github.com/inliniac/suricata/pull/34&#34;&gt;merged to main tree&lt;/a&gt; a branch containing some interesting new TLS related features. They have been contributed by me and Jean-Paul Roliers.&lt;/p&gt;
&lt;p&gt;This patchset introduces TLS logging and brings some new keywords to Suricata engine.&lt;br&gt;
Here’s the list of all TLS related keywords that are available in latest Suricata git:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;tls.version: match on version of protocol&lt;/li&gt;
&lt;li&gt;tls.subject: match on subject of certificate&lt;/li&gt;
&lt;li&gt;tls.issuerdn: match on issuer DN of certificate&lt;/li&gt;
&lt;li&gt;tls.fingerprint: match on SHA1 fingerprint of certificate&lt;/li&gt;
&lt;li&gt;tls.store: store the certificate on disk&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You will find detailed explanation below.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata, to 10Gbps and beyond</title>
      <link>https://home.regit.org/2012/07/suricata-to-10gbps-and-beyond/</link>
      <pubDate>Mon, 30 Jul 2012 21:03:19 +0000</pubDate>
      <guid>https://home.regit.org/2012/07/suricata-to-10gbps-and-beyond/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Since the beginning of July 2012, OISF team is able to access to a server where one interface is receiving&lt;br&gt;
some mirrored real European traffic. When reading &amp;ldquo;some&amp;rdquo;, think between 5Gbps and 9.5Gbps&lt;br&gt;
constant traffic. With that traffic, this is around 1Mpps to 1.5M packet per seconds we have to study.&lt;/p&gt;
&lt;p&gt;The box itself is a standard server with the following characteristics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;CPU: One Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz (16 cores counting Hyperthreading)&lt;/li&gt;
&lt;li&gt;Memory: 32Go&lt;/li&gt;
&lt;li&gt;capture NIC: Intel 82599EB 10-Gigabit SFI/SFP+&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The objective is simple: be able to run Suricata on this box and treat the whole&lt;br&gt;
traffic with a decent number of rules. With the constraint not to use any non&lt;br&gt;
official system code (plain system and kernel if we omit a driver).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building Suricata for OpenBSD 4.9 and over</title>
      <link>https://home.regit.org/2012/04/suricata-for-openbsd-4-9-and-over/</link>
      <pubDate>Fri, 27 Apr 2012 14:57:47 +0000</pubDate>
      <guid>https://home.regit.org/2012/04/suricata-for-openbsd-4-9-and-over/</guid>
      <description>&lt;p&gt;It seems OpenBSD upgrade are done to give maintenance work to the developers of third-party application. In a way, OpenBSD fight against the economic crisis: It gives jobs to developers and if you want some performance you need a powerful thus new computer.&lt;/p&gt;
&lt;p&gt;Let’s stop bashing and be serious: Suricata was building fine on OpenBSD 4.8 but the build was failing on subsequent version. This was link with an include modification around the “socket.h” file. It is now mandatory to include “types.h” before “socket.h” to avoid compilation error. The patch &lt;a href=&#34;https://home.regit.org/uploads/2012/04/0001-Fix-OpenBSD-compilation.patch.gz&#34;&gt;0001-Fix-OpenBSD-compilation.patch.gz&lt;/a&gt; fixes the build.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using AF_PACKET zero copy mode in Suricata</title>
      <link>https://home.regit.org/2012/02/using-af_packet-zero-copy-mode-in-suricata/</link>
      <pubDate>Thu, 23 Feb 2012 18:25:15 +0000</pubDate>
      <guid>https://home.regit.org/2012/02/using-af_packet-zero-copy-mode-in-suricata/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.inliniac.net/blog/&#34;&gt;Victor Julien&lt;/a&gt; has &lt;a href=&#34;http://lists.openinfosecfoundation.org/pipermail/oisf-devel/2012-February/001283.html&#34;&gt;just pushed&lt;/a&gt; a new feature to &lt;a href=&#34;https://redmine.openinfosecfoundation.org/projects/suricata/repository&#34;&gt;suricata’s git tree&lt;/a&gt;. It brings improvements to the AF_PACKET capture mode.&lt;/p&gt;
&lt;p&gt;This capture mode can be used on Linux. It is the native way to capture packet. Suricata is able to use the interesting new multithreading feature provided by AF_PACKET on recent kernels: it is possible to have multiple capture threads receiving the packet of a single interface.&lt;/p&gt;
&lt;p&gt;The commits add mmaped ring buffer support to AF_PACKET capture and also provide a zero copy mode. Mmaped ring buffer is mechanism similar to the one used by PF_RING. The kernel allocates some memory to store the packets and share this memory with the capture process. Instead of sending messages, the kernel just write to the shared memory and the process capture reads it. This is less consuming in term of CPU ressource and helps to increase the capture rate. But the main avantage of this technique is that the capture process can treat the packets without making a copy and this saves a lot of time&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ecosystem of Suricata</title>
      <link>https://home.regit.org/2012/02/ecosystem-of-suricata/</link>
      <pubDate>Mon, 13 Feb 2012 16:46:32 +0000</pubDate>
      <guid>https://home.regit.org/2012/02/ecosystem-of-suricata/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.openinfosecfoundation.org/index.php/downloads&#34;&gt;Suricata&lt;/a&gt; is an IDS/IPS engine. To build a complete solution, you will need to use other tools.&lt;/p&gt;
&lt;p&gt;The following schema is a representation of a possible software setup in the case Suricata is used as IDS or IPS on the network. It only uses opensource components:&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2012/02/suricata-ecosystem1.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2012/02/suricata-ecosystem1.png&#34; alt=&#34;&#34; title=&#34;Suricata&amp;#039;s ecosystem&#34; width=&#34;450&#34; height=&#34;484&#34; class=&#34;aligncenter size-full wp-image-914&#34; srcset=&#34;https://home.regit.org/uploads/2012/02/suricata-ecosystem1.png 450w, https://home.regit.org/uploads/2012/02/suricata-ecosystem1-278x300.png 278w&#34; sizes=&#34;auto, (max-width: 450px) 85vw, 450px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Suricata is used to sniff and analyse the traffic. To detect malicious traffic, it uses signatures (or rules). You can download a set of specialised rules from &lt;a href=&#34;http://www.emergingthreats.net/&#34;&gt;EmergingThreats&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Acquisition systems and running modes evolution of Suricata</title>
      <link>https://home.regit.org/2011/10/suricata-new-feature/</link>
      <pubDate>Thu, 06 Oct 2011 23:06:24 +0000</pubDate>
      <guid>https://home.regit.org/2011/10/suricata-new-feature/</guid>
      <description>&lt;p&gt;Some new features have recently reach &lt;a href=&#34;https://redmine.openinfosecfoundation.org/projects/suricata/repository&#34;&gt;Suricata’s git tree&lt;/a&gt; and will be available in the next development release. I’ve worked on some of them that I will describe here.&lt;/p&gt;
&lt;h2 id=&#34;multi-interfaces-support-and-new-running-modes&#34;&gt;Multi interfaces support and new running modes&lt;/h2&gt;
&lt;h3 id=&#34;configuration-update&#34;&gt;Configuration update&lt;/h3&gt;
&lt;p&gt;IDS live mode in &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;suricata&lt;/a&gt; (pcap, pf_ring, af_packet) now supports the capture on multiple interfaces. The syntax of the YAML configuration file has evolved and it is now possible to set per-interface variables.&lt;/p&gt;
&lt;p&gt;For example, it is possible to define &lt;code&gt;pfring&lt;/code&gt; configuration with the following syntax:&lt;/p&gt;</description>
    </item>
    <item>
      <title>OISF brainstorming: planning phase 3 (take 3)</title>
      <link>https://home.regit.org/2011/09/oisf-brainstorming-planning-phase-3-take-3/</link>
      <pubDate>Mon, 19 Sep 2011 23:42:25 +0000</pubDate>
      <guid>https://home.regit.org/2011/09/oisf-brainstorming-planning-phase-3-take-3/</guid>
      <description>&lt;h2 id=&#34;geo-ip&#34;&gt;GEO IP&lt;/h2&gt;
&lt;p&gt;Idea is to add a keyword that would be used to interact with GEOIP database (free at least) and be able to use it to detect things like control canal. For example, an IRC server in an non common country is certainly a control canal.&lt;/p&gt;
&lt;h2 id=&#34;live-ruleset-swap&#34;&gt;Live ruleset swap&lt;/h2&gt;
&lt;p&gt;A must have! This is vital for critical environnement. This is very costly in memory and this should be an option to avoid exploding low memory boxes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OISF brainstorming: planning phase 3 (take 2)</title>
      <link>https://home.regit.org/2011/09/oisf-brainstorming-planning-phase-3-take-2/</link>
      <pubDate>Mon, 19 Sep 2011 22:49:17 +0000</pubDate>
      <guid>https://home.regit.org/2011/09/oisf-brainstorming-planning-phase-3-take-2/</guid>
      <description>&lt;h2 id=&#34;dns-fast-fluxanomaly-detection&#34;&gt;DNS fast flux/anomaly detection&lt;/h2&gt;
&lt;p&gt;The idea is to detect malware and other things by collecting the DNS request and their answer and detecting anomaly. For example, if an host is making a lot of request to a domain.&lt;/p&gt;
&lt;p&gt;First part of the job on Suricata is to log all requests and their answer. Then analysis can occurs in the database.&lt;/p&gt;
&lt;h2 id=&#34;file-extraction&#34;&gt;File extraction&lt;/h2&gt;
&lt;p&gt;This is a work under progress linked with a third party contract. It permit to store exchanged files on disk for some application level protocol. It is possible to say: “store the file, if the content type is different from the extension”. File extraction works currently on HTTP. It focus on POST request to detect uploaded file.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Oisf brainstorming: planning phase 3 (take 1)</title>
      <link>https://home.regit.org/2011/09/discussing-phase-3/</link>
      <pubDate>Mon, 19 Sep 2011 21:52:28 +0000</pubDate>
      <guid>https://home.regit.org/2011/09/discussing-phase-3/</guid>
      <description>&lt;h2 id=&#34;performance-improvement&#34;&gt;Performance improvement&lt;/h2&gt;
&lt;p&gt;As shown by Victor’s latest work on performance counters, there is a lot of work that can be done to improve performance. They are currently good but there is place for improvement. Proposal to provide off-loading or clustering is done. This is heavily discussed but as pointed out by Victor, it will be more interesting to do this in the next phase. Phase 3 should focus in improvement of current code. This will permit to use the upcoming Suricata killing features like global flow variable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Matt Jonkman: development avancement</title>
      <link>https://home.regit.org/2011/09/matt-jonkman-development-avancement/</link>
      <pubDate>Mon, 19 Sep 2011 21:14:59 +0000</pubDate>
      <guid>https://home.regit.org/2011/09/matt-jonkman-development-avancement/</guid>
      <description>&lt;p&gt;Phase 2 development is almost over now. Among the completed major features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Multithread&lt;/li&gt;
&lt;li&gt;protocol discovery&lt;/li&gt;
&lt;li&gt;smb logging&lt;/li&gt;
&lt;li&gt;HTTP logging&lt;/li&gt;
&lt;li&gt;flowvars&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;One of the advantage of Suricata over Snort is protocol discovery combined to HTTP parsing by libhtp. It provides a huge improvement over Snort as a lot of bad flow are using HTTP on non standard ports.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Victor Julien: Development status</title>
      <link>https://home.regit.org/2011/09/victor-julien-development-status/</link>
      <pubDate>Mon, 19 Sep 2011 20:49:42 +0000</pubDate>
      <guid>https://home.regit.org/2011/09/victor-julien-development-status/</guid>
      <description>&lt;p&gt;Work has started in september 2007. The work depends on some externel library like multithread of input handling library. The main external depedency is libhtp which is initally developped by Ivan Ristic.&lt;/p&gt;
&lt;p&gt;The development is managed in a single git repository. Victor is the only one with commit right. The review are done by Victor and cross review are made by developpers.&lt;/p&gt;
&lt;p&gt;Work unit for developers are tasks which are written by Victor and describe a specific task to do. This task are mainly done by OISF funded developers. Some simpler task are let to the comunity and everyone can help with this.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Slides of my Suricata talk at Libre Software Meeting</title>
      <link>https://home.regit.org/2011/07/slides-of-my-suricata-talk-at-libre-software-meeting/</link>
      <pubDate>Wed, 13 Jul 2011 08:55:15 +0000</pubDate>
      <guid>https://home.regit.org/2011/07/slides-of-my-suricata-talk-at-libre-software-meeting/</guid>
      <description>&lt;p&gt;I gave a talk about Suricata entitled &lt;em&gt;Suricata, rethinking IDS/IPS&lt;/em&gt; at Libre Software Meeting (RMLL in french). &lt;a href=&#34;http://2011.rmll.info/IMG/pdf/2011_rmll_suricata.pdf&#34;&gt;The slides&lt;/a&gt; can be downloaded from the &lt;a href=&#34;http://2011.rmll.info/Suricata-repensez-les-IDS-IPS&#34;&gt;RMLL website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Thanks a lot to &lt;a href=&#34;https://twitter.com/#!/cbrocas&#34;&gt;Christophe Brocas&lt;/a&gt; and Mathieu Blanc for the organisation of the security track of LSM.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About Suricata performance boost between 1.0 and 1.1beta2</title>
      <link>https://home.regit.org/2011/06/about-suricata-performance-boost-between-1-0-and-1-1beta2/</link>
      <pubDate>Thu, 02 Jun 2011 19:45:03 +0000</pubDate>
      <guid>https://home.regit.org/2011/06/about-suricata-performance-boost-between-1-0-and-1-1beta2/</guid>
      <description>&lt;h2 id=&#34;discovering-the-performance-boost&#34;&gt;Discovering the performance boost&lt;/h2&gt;
&lt;p&gt;When doing some coding on both 1.0 and 1.1 branch of &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;suricata&lt;/a&gt;, I’ve remarked that there was a huge performance improvement of the 1.1 branch over the 1.0 branch. The parsing of a given real-life pcap file was taking 200 seconds with 1.0 but only 30 seconds with 1.1. This performance boost was huge and I decide to double check and to study how such a performance boost was possible and how it was obtained:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata conference at Solutions Linux 2011</title>
      <link>https://home.regit.org/2011/05/suricata-sollinux-2011/</link>
      <pubDate>Wed, 11 May 2011 20:18:59 +0000</pubDate>
      <guid>https://home.regit.org/2011/05/suricata-sollinux-2011/</guid>
      <description>&lt;p&gt;I’ve gived today a presentation about &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;Suricata&lt;/a&gt; at the &lt;a href=&#34;http://www.solutionslinux.fr/&#34;&gt;Solutions Linux&lt;/a&gt; event. It was part of the security track presided by &lt;a href=&#34;http://hsc.fr/&#34;&gt;Herve Schauer&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The slides are in french and are available here: &lt;a href=&#34;http://home.regit.org/uploads/2011/05/2011_sollinux_suricata.pdf&#34;&gt;2011_sollinux_suricata&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Joining the OISF coding staff</title>
      <link>https://home.regit.org/2011/04/joining-the-oisf-codinf-staff/</link>
      <pubDate>Wed, 20 Apr 2011 21:19:55 +0000</pubDate>
      <guid>https://home.regit.org/2011/04/joining-the-oisf-codinf-staff/</guid>
      <description>&lt;p&gt;My collaboration with OISF has been &lt;a href=&#34;http://www.openinfosecfoundation.org/index.php/component/content/article/1-latest-news/123-eric-leblond-joins-the-oisf-coding-staff&#34;&gt;announced today&lt;/a&gt;. This is an honor for me to join this excellent team on this wonderful project. I’ve taken a lot of pleasure in the past months contributing to the project and I’m sure the start of an official collaboration will lead to good things. The challenge is high and I will do my best to merit the trust.&lt;/p&gt;
&lt;p&gt;A big thanks to all people who congrat me for this nomination.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building Suricata under OpenBSD</title>
      <link>https://home.regit.org/2011/04/building-suricata-under-openbsd/</link>
      <pubDate>Sun, 17 Apr 2011 08:17:35 +0000</pubDate>
      <guid>https://home.regit.org/2011/04/building-suricata-under-openbsd/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.openinfosecfoundation.org/index.php/component/content/article/1-latest-news/121-suricata-11beta2-available&#34;&gt;Suricata 1.1beta2&lt;/a&gt; has brought &lt;a href=&#34;http://www.openbsd.org/&#34;&gt;OpenBSD&lt;/a&gt; to the list of supported operating system. I’m a total newbie to OpenBSD so excuse me for the lack of respect of OpenBSD standards and usages in this documentation.&lt;/p&gt;
&lt;p&gt;Here’s the different step, I’ve used to finalize the port starting from a fresh install of OpenBSD.&lt;/p&gt;
&lt;p&gt;If you want to use source taken from git, you will need to install building tools:&lt;/p&gt;
&lt;pre&gt;pkg_add git libtool&lt;/pre&gt;
&lt;p&gt;automake and autoconf need to be installed to. For a OpenBSD 4.8, one can run:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some new features of IPS mode in Suricata 1.1beta2</title>
      <link>https://home.regit.org/2011/04/some-new-features-of-ips-mode-in-suricata-1-1beta2/</link>
      <pubDate>Wed, 13 Apr 2011 22:37:12 +0000</pubDate>
      <guid>https://home.regit.org/2011/04/some-new-features-of-ips-mode-in-suricata-1-1beta2/</guid>
      <description>&lt;p&gt;The IDS/IPS suricata has a native support for Netfilter queue. This brings IPS functionnalities to users running Suricata on Linux.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.openinfosecfoundation.org/index.php/component/content/article/1-latest-news/121-suricata-11beta2-available&#34;&gt;Suricata 1.1beta2&lt;/a&gt; introduces a lot of new features related to the NFQ mode.&lt;/p&gt;
&lt;h2 id=&#34;new-stream-inline-mode&#34;&gt;New stream inline mode&lt;/h2&gt;
&lt;p&gt;One of the main improvement of Suricata IPS mode is related with the new stream engine dedicated to inline. Victor Julien has a &lt;a href=&#34;http://www.inliniac.net/blog/2011/01/31/suricata-ips-improvements.html&#34;&gt;great blog post about it&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;multiqueue-support&#34;&gt;Multiqueue support&lt;/h2&gt;
&lt;p&gt;Suricata can now be started on multiple queue by using a comma separated list of queue identifier on the command line. The following syntax:&lt;/p&gt;</description>
    </item>
    <item>
      <title>More about Suricata multithread performance</title>
      <link>https://home.regit.org/2011/02/more-about-suricata-multithread-performance/</link>
      <pubDate>Tue, 15 Feb 2011 23:30:49 +0000</pubDate>
      <guid>https://home.regit.org/2011/02/more-about-suricata-multithread-performance/</guid>
      <description>&lt;p&gt;Following my &lt;a href=&#34;http://home.regit.org/?p=438&#34;&gt;preceding post&lt;/a&gt; on suricata multithread performance I’ve decided to continue to work on the subject.&lt;/p&gt;
&lt;p&gt;By using perf-tool, I found out that when the number of detect threads was increasing, more and more time was used in a spin lock. One of the possible explanation is that the default running mode for pcap file (RunModeFilePcapAuto) is not optimal. The only decode thread take some time to treat the packets and he is not fast enough to send data to the multiple detect threads. This is triggering a lot of wait and a CPU usage increase. Following a discussion with Victor Julien, I decide to give a try to an alternate run mode for working on pcap file, RunModeFilePcapAutoFp.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Optimizing Suricata on multicore CPUs</title>
      <link>https://home.regit.org/2011/01/optimizing-suricata-on-a-multicore-cpu/</link>
      <pubDate>Wed, 26 Jan 2011 00:20:28 +0000</pubDate>
      <guid>https://home.regit.org/2011/01/optimizing-suricata-on-a-multicore-cpu/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;Suricata&lt;/a&gt; IDS/IPS architecture is heavily using multithreading. On almost every runmode (PCAP, PCAP file, NFQ, …) it is possible to setup the number of thread that are used for detection. This is the most CPU intensive task as it does the detection of alert by checking the packet on the signatures. The configuration of the number of threads is done by setting&lt;br&gt;
a ratio which decide of the number of threads to be run by available CPUs (detect_thread_ratio variable).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building a suricata compliant ruleset</title>
      <link>https://home.regit.org/2011/01/building-a-suricata-compliant-ruleset/</link>
      <pubDate>Sun, 16 Jan 2011 16:13:08 +0000</pubDate>
      <guid>https://home.regit.org/2011/01/building-a-suricata-compliant-ruleset/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;During Nefilter Workshop 2008, we had an interesting discussion about the fact that NFQUEUE is a terminal decision. This has some strong implication and in particular when working with an IPS like suricata (or snort-inline at the time of the discussion): the IPS must received all packets routed by the gateway and can only issue a terminal DROP or ACCEPT verdict. It thus take precedence over all subsequent rules in the ruleset: any ACCEPT rules before the IPS rules will remove packets from IPS analysis and in the other way, any decision after the IPS rules will be ignored.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Suricata with CUDA</title>
      <link>https://home.regit.org/2010/05/using-suricata-with-cuda/</link>
      <pubDate>Sun, 23 May 2010 19:10:25 +0000</pubDate>
      <guid>https://home.regit.org/2010/05/using-suricata-with-cuda/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.openinfosecfoundation.org/&#34; target=&#34;_blank&#34;&gt;Suricata&lt;/a&gt; is a next generation IDS/IPS engineÂ developedÂ by the &lt;a href=&#34;http://www.openinfosecfoundation.org/index.php/consortium-members&#34;&gt;Open Information Security Foundation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This article describes the installation, setup and usage of &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34; target=&#34;_blank&#34;&gt;Suricata&lt;/a&gt; with CUDA support on a &lt;a href=&#34;http://www.ubuntu.com&#34; target=&#34;_blank&#34;&gt;Ubuntu&lt;/a&gt; 10.04 64bit. For 32 bit users, simply remove 64 occurances where you find them.&lt;/p&gt;
&lt;h2 id=&#34;preparation&#34;&gt;Preparation&lt;/h2&gt;
&lt;p&gt;You need to download &lt;span style=&#34;text-decoration: underline;&#34;&gt;both&lt;/span&gt; Developper driver and Cuda driver from &lt;a title=&#34;Nvidia Download&#34; href=&#34;http://developer.nvidia.com/object/cuda_3_0_downloads.html#Linux&#34; target=&#34;_blank&#34;&gt;nvidia website&lt;/a&gt;. I really mean both because Ubuntu nvidia drivers are not working with CUDA.&lt;/p&gt;
&lt;p&gt;I’ve first downloaded and installed CUDA toolkit for Ubuntu 9.04. It was straightforward:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
