Tip

Snort IDS upgrade and tips on the Snort.conf file

Since the last edition of Snort Report, Snort IDS has been updated from version 2.6.1 to 2.6.1.2. So I'll begin this edition by addressing the issue of upgrading from one version

    Requires Free Membership to View

to the next. Then I'll move on to discuss the contents of the snort.conf configuration file.

In my last Snort Report, I recommended creating a directory specifically for Snort 2.6.1, namely /usr/local/snort-2.6.1. That directory contained the Snort binary, in the bin/ directory. To "upgrade," create a new directory for Snort 2.6.1.2, e.g.:

freebsd61-generic:/root# mkdir /usr/local/snort-2.6.1.2

Now proceed with the steps to retrieve, extract and compile Snort described in the previous article. Be sure to replace instances of "snort-2.6.1" with "snort-2.6.1.2". To run the new version instead of the old, invoke it from the /usr/local/snort-2.6.1.2/bin/ directory.

I recommend creating new directories for extraction and installation every time you encounter a new version of Snort. At the very least, you will have a chance to keep the old version running while creating a new version for testing. Of course, you should deploy a separate testing infrastructure independent of production systems. Keeping several versions of Snort handy on production systems, however, is a good way to roll back to an older version should a newer version seem to encounter difficulties in the field.


Snort: Understanding the configuration file

 Introduction: Upgrade to Snort 2.6.1.2
 The snort.conf file
 Defining IP ranges of interest
 Defining ports of interest
 Core preprocessors
 Non-dynamic preprocessors
 Conclusion

About the author
Richard Bejtlich is founder of TaoSecurity, author of several books on network security monitoring, including Extrusion Detection: Security Monitoring for Internal Intrusions, and operator of the TaoSecurity blog.


This was first published in April 2007

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.