<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Modsecurity on Inliniac</title>
    <link>https://inliniac.net/blog/tag/modsecurity/</link>
    <description>Recent content in Modsecurity on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2009 18:30:37 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/modsecurity/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OISF engine development update(2)</title>
      <link>https://inliniac.net/blog/2009/09/30/oisf-engine-development-update2/</link>
      <pubDate>Wed, 30 Sep 2009 18:30:37 +0000</pubDate>
      <guid>https://inliniac.net/blog/2009/09/30/oisf-engine-development-update2/</guid>
      <description>&lt;p&gt;Another quick update on the development of the OISF engine. Overall development is going great. Basics like signature keywords, stream reassembly, ip defragmentation are nearing completion. Unified1 + barnyard was already working for quite some time, but now we also have unified2 compatible output. I&amp;rsquo;ve tested this to work with barnyard2 and Sguil which works nicely.&lt;/p&gt;&#xA;&lt;p&gt;We have the first versions of our new YAML based configuration format checked in, a brand new logging API, midstream pickup support in our Stream engine, native PFRING support and many other additions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DC meeting</title>
      <link>https://inliniac.net/blog/2009/07/21/dc-meeting/</link>
      <pubDate>Tue, 21 Jul 2009 16:33:27 +0000</pubDate>
      <guid>https://inliniac.net/blog/2009/07/21/dc-meeting/</guid>
      <description>&lt;p&gt;So I just got back from Washington D.C. where we had our first public meeting for the &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;OISF&lt;/a&gt;. I think it went very well as there were more people than expected. The attendees came from all parts from the industry &amp;amp; government. Overall reception was very positive and we&amp;rsquo;ve gotten many offers for help in development &amp;amp; testing.&lt;/p&gt;&#xA;&lt;p&gt;Around the public meetings we had private meetings with a number of companies and I&amp;rsquo;m very happy that three of them commited to the project already:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Modsec2sguil for HTTP transaction logging revisited</title>
      <link>https://inliniac.net/blog/2007/08/22/using-modsec2sguil-for-http-transaction-logging-revisited/</link>
      <pubDate>Wed, 22 Aug 2007 20:05:34 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/08/22/using-modsec2sguil-for-http-transaction-logging-revisited/</guid>
      <description>&lt;p&gt;Recently I wrote about the idea to log all HTTP transactions into Sguil using my Modsec2sguil agent. I&amp;rsquo;ve implemented this in the current &lt;a href=&#34;http://www.inliniac.net/modsec2sguil/&#34;&gt;0.8-dev5&lt;/a&gt; release and it works very well. All events go into Sguil smoothly and I&amp;rsquo;ve not experienced slowdowns on the webserver. I&amp;rsquo;ve been running it for almost a week now, like to share the first experiences here.&lt;/p&gt;&#xA;&lt;p&gt;I find it to be quite useful. When receiving an alert, it is perhaps more interesting to see what else was done from that ipaddress than to see what was blocked (unless you are suspecting a false positive of course). One area I find to be useful is when I&amp;rsquo;m creating rules against comment spam on this blog. By seeing all properties of a spam message I can create better rules. For example on broken user-agents or weird codes inserted into the comment field of Wordpress.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
