Snort mailing list archives

Re: Question


From: "Joel Esler \(jesler\) via Snort-sigs" <snort-sigs () lists snort org>
Date: Sun, 10 Mar 2019 13:39:13 +0000

The subscriber/registered ruleset would have them.  The community ruleset is mostly comprised of rules submitted by the 
public, and generally speaking, does not have a lot of IOT rules in it.

Sent from my  iPad

On Mar 10, 2019, at 08:34, Shmuel Gihon <sgihon () allot com> wrote:

Hi All,
 
I have a question about the Sigs.
Which DBs contain IoT Security related signatures?
Community or Enterprise?
 
Thanks.
 
Shmuel Gihon
DPI Researcher
Tel: +97297619138
sgihon () allot com
www.allot.com
 
 
<image001.jpg>
 
This message is intended only for the designated recipient(s). It may contain confidential or proprietary 
information. If you are not the designated recipient, you may not review, copy or distribute this message. If you 
have mistakenly received this message, please notify the sender by a reply e-mail and delete this message. Thank you.
_______________________________________________
Snort-sigs mailing list
Snort-sigs () lists snort org
https://lists.snort.org/mailman/listinfo/snort-sigs

Please visit http://blog.snort.org for the latest news about Snort!

Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette

Visit the Snort.org to subscribe to the official Snort ruleset, make sure to stay up to date to catch the most <a 
href=" https://snort.org/downloads/#rule-downloads";>emerging threats</a>!

Attachment: smime.p7s
Description:

_______________________________________________
Snort-sigs mailing list
Snort-sigs () lists snort org
https://lists.snort.org/mailman/listinfo/snort-sigs

Please visit http://blog.snort.org for the latest news about Snort!

Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette

Visit the Snort.org to subscribe to the official Snort ruleset, make sure to stay up to date to catch the most <a 
href=" https://snort.org/downloads/#rule-downloads";>emerging threats</a>!

Current thread: