<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.gmail-hoenzb
{mso-style-name:gmail-hoenzb;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head><body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">So if I understand this correctly. There are Emerging Threats rules for 1.X, 2.X, and 4.X. Are there no 3.X rulesets?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b>Charles DeVoe Jr.</b><o:p></o:p></p>
<p class="MsoNormal">Manager of Engineering<o:p></o:p></p>
<p class="MsoNormal">Multi-State Information Sharing and Analysis Center (MS-ISAC) <o:p></o:p></p>
<p class="MsoNormal">31 Tech Valley Drive<o:p></o:p></p>
<p class="MsoNormal">East Greenbush, NY 12061<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:charles.devoe@cisecurity.org">charles.devoe@cisecurity.org</a><o:p></o:p></p>
<p class="MsoNormal">(518) 266-3494<o:p></o:p></p>
<p class="MsoNormal">7x24 Security Operations Center<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:SOC@cisecurity.org"><span style="color:#0563C1">SOC@cisecurity.org</span></a> - 1-866-787-4722<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img border="0" width="237" height="55" style="width:2.4687in;height:.5729in" id="Picture_x0020_1" src="cid:image001.png@01D36913.80368C70" alt="cid:image001.png@01D2F965.2E3564F0"><o:p></o:p></p>
<p class="MsoNormal"> <a href="https://www.facebook.com/CenterforIntSec"><span style="color:windowtext;text-decoration:none"><img border="0" width="32" height="33" style="width:.3333in;height:.3437in" id="Picture_x0020_2" src="cid:image002.png@01D36913.80368C70" alt="id:image002.png@01D2926D.D9CF2E90"></span></a> <a href="https://twitter.com/CISecurity"><span style="color:windowtext;text-decoration:none"><img border="0" width="32" height="33" style="width:.3333in;height:.3437in" id="Picture_x0020_3" src="cid:image003.png@01D36913.80368C70" alt="id:image003.png@01D2926D.D9CF2E90"></span></a> <a href="https://www.youtube.com/user/TheCISecurity"><span style="color:windowtext;text-decoration:none"><img border="0" width="32" height="33" style="width:.3333in;height:.3437in" id="Picture_x0020_4" src="cid:image004.png@01D36913.80368C70" alt="id:image004.png@01D2926D.D9CF2E90"></span></a> <a href="https://www.linkedin.com/company/the-center-for-internet-security"><span style="color:windowtext;text-decoration:none"><img border="0" width="32" height="33" style="width:.3333in;height:.3437in" id="Picture_x0020_5" src="cid:image005.png@01D36913.80368C70" alt="id:image005.png@01D2926D.D9CF2E90"></span></a><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Oisf-users [mailto:oisf-users-bounces@lists.openinfosecfoundation.org]
<b>On Behalf Of </b>Jason Williams<br>
<b>Sent:</b> Wednesday, November 29, 2017 12:07 PM<br>
<b>To:</b> Alan Amesbury <amesbury@oitsec.umn.edu><br>
<b>Cc:</b> oisf-users@openinfosecfoundation.org<br>
<b>Subject:</b> Re: [Oisf-users] Suricata 4.0 rule fork<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Nov 28, 2017 at 10:29 AM, Alan Amesbury <<a href="mailto:amesbury@oitsec.umn.edu" target="_blank">amesbury@oitsec.umn.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">This message made its way to me via a coworker; my "digest" version apparently isn't due out for another half hour or so, so apologies for any misquoting.<br>
<br>
Francis Trudeau wrote:<br>
<br>
> The new Suricata 4.0 rules have been live on the production servers<br>
> since Thanksgiving. Sorry for the notification delay, we wanted to<br>
> see what happened over the US holiday weekend, and everything looks<br>
> good.<br>
><br>
> Please use the version number of your engine in the URL you use to<br>
> retrieve the set. We changed how it works now, and some paths that<br>
> worked before will no longer work. This was done to ensure people got<br>
> the right set for their engine. Please check your sensors and make<br>
> sure everything is updating correctly.<br>
<br>
Are rulesets backwards compatible? For example, can I run a ruleset intended for a v2.x version of Suricata on a 4.x version? I have a pair of sensors that for ${REASON} haven't been able to upgrade. The bulk are on a v3.x version, but I have some running
2.x.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As suricata has kept compatibility with old versions, and we still have a Suricata 2.0 ruleset, at this time you can run an ET ruleset intended for a v2.x version of Suricata on a 4.x version.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">Also, is there a definitive list of the ruleset version differences somewhere, e.g., which features require which engine version? I looked at<br>
<br>
<a href="http://suricata.readthedocs.io/en/latest/rules/index.html" target="_blank">
http://suricata.readthedocs.io/en/latest/rules/index.html</a><br>
<br>
<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Other than patch notes (<a href="https://suricata-ids.org/2017/07/27/suricata-4-0-released/">https://suricata-ids.org/2017/07/27/suricata-4-0-released/</a>) not to my knowledge. Many rule related improvements, such as http/tls
buffers were introduced in 4 that we (ET) couldn't pass up, hence the fork. Tons of under the hood stuff that makes 4.0 much better. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">but didn't see any v3.x vs v4.x differences highlighted. In contrast, I see notes specific to v1.x and v2.x in section 4.5.2.1.1.1 "Appendix A - Buffers, list_id values, and Registration Order for Suricata 1.3.4" (although the table in
4.5.2.1.1.2 is unreadable due to truncation).<br>
<span style="color:#888888"><br>
<br>
<span class="gmail-hoenzb">--</span><br>
<span class="gmail-hoenzb">Alan Amesbury</span><br>
<span class="gmail-hoenzb">University Information Security</span><br>
<span class="gmail-hoenzb"><a href="http://umn.edu/lookup/amesbury" target="_blank">http://umn.edu/lookup/amesbury</a></span><br>
<br>
<span class="gmail-hoenzb">_______________________________________________</span><br>
<span class="gmail-hoenzb">Suricata IDS Users mailing list: <a href="mailto:oisf-users@openinfosecfoundation.org">
oisf-users@openinfosecfoundation.org</a></span><br>
<span class="gmail-hoenzb">Site: <a href="http://suricata-ids.org" target="_blank">
http://suricata-ids.org</a> | Support: <a href="http://suricata-ids.org/support/" target="_blank">
http://suricata-ids.org/support/</a></span><br>
<span class="gmail-hoenzb">List: <a href="https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users" target="_blank">
https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users</a></span><br>
<br>
<span class="gmail-hoenzb">Conference: <a href="https://suricon.net" target="_blank">
https://suricon.net</a></span><br>
<span class="gmail-hoenzb">Trainings: <a href="https://suricata-ids.org/training/" target="_blank">
https://suricata-ids.org/training/</a></span></span><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><br>
..... <o:p></o:p></p>
</div>
This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender
immediately and permanently delete the message and any attachments.
<br /><br />. . . . .</body></html>