Community

Please check the appropriate list archives and available documentation before posting.

 Snort Users General discussion about Snort Archives
Snort Sigs Discussion and development of Snort rules Archives
Snort Developers Snort development discussions here. (New features, bug reports and the like) Archives
Snort OpenAppId Snort OpenAppId discussion. The Preprocessor, the detection, all of it Archives

Snort blog

Talos blog

ClamAV blog

Snort has made these virtual backgrounds for your use in Webex!

All images are from the 2023 Snort parody calendar. Snort and the Snort pig are registered trademarks of Cisco. All rights reserved. Alterations are strictly prohibited.

Disclaimer: Snort cannot be held accountable for squeals of joy upon others seeing these backgrounds during a Webex meeting. Also, be conscious of your audience when using these, not all parts of the world appreciate the pig.

January 2023
February 2023
March 2023
April 2023
May 2023
June 2023
July 2023
August 2023
September 2023
October 2023
November 2023
December 2023
The power of Snort is due in large part to the influence and scope of the Snort user community.
The power of Snort is due in large part to the influence and scope of the Snort user community.
The power of Snort is due in large part to the influence and scope of the Snort user community.
The power of Snort is due in large part to the influence and scope of the Snort user community.

Help make Snort better

You can help in the following ways

Snort user webcast series

Check in to view the latest snort webcast. When video is not available powerpoint slides will be provided

Click here to go to view all webcasts
The open source Snort community worldwide can detect security threats more quickly and efficiently than in a 'closed' environment.
The open source Snort community worldwide can detect security threats more quickly and efficiently than in a 'closed' environment.

Submit a Bug

In order for the Snort team to replicate and ultimately solve the problem you're experiencing we need some basic information. When you report a bug please include the following in your report. Without this information there is little we can do to help.

All bug reports should include:

  • The version of Snort you're running
  • Information on the rules you have enabled
  • How Snort was built. Did you build from source (recommended), use a binary from Snort.org, use a third party distribution
  • Your configuration files (snort.conf, *.rules, threshold.conf, etc.)
  • Platform information: OS and hardware (e.g. Ubuntu 8.02, Linux 2.6 kernel, Intel 64bit)
  • Any relevant error messages
  • Any output that may be helpful

For more information on effective bug reporting please review the the doc/BUGS file in the Snort distribution.

Including the above information will help the Snort team to accurately identify the problem and provide you with the guidance you need.

All bug reports should be sent to bugs@snort.org