Home > Articles > Security > Network Security

  • Print
  • + Share This

Configuring Snort

The snort.conf file provided in the distribution normally needs to be modified to work properly. There are several variables that must be defined in order for Snort to identify the traffic. Additionally, the snort.conf file is where you define what plugins to use, what rulesets to use, and how to output log and alert information.

Variable Definition

Individual IP and Network addresses are given in CIDR notation. Most variables and configuration directives accept a list of addresses. The list format is a comma-separated list with no spaces between each IP or Network address. The list itself is enclosed in square brackets, like so:

[10.1.1.0/24,192.168.71.20/32]

The first variables to define are the internal and external networks. The terms internal and external are relative, and can be adjusted to mean many hosts or networks. Internal networks are generally defined as those within your organization. However, for servers on your DMZ, you might configure the internal network as the IP address of the server itself, and external network as everything else. This view allows you to monitor all access, including access from internal hosts.

var HOME_NET 192.168.71.119/32
var INTERNAL $HOME_NET

External networks can then be defined in terms of what is internal.

var EXTERNAL_NET !$HOME_NET
var EXTERNAL $EXTERNAL_NET

It is important to define both HOME_NET/EXTERNAL_NET and INTERNAL/EXTERNAL variable pairs because some rulesets use the former, and others use the latter. Defining both allows you to mix and match rulesets without a significant amount of editing on your part.

Mail servers, Web servers, DNS servers, and database servers are defined in a similar fashion to the internal and external networks. You can provide lists of hosts and networks, or use the $HOME_NET variable.

var SMTP $HOME_NET
var HTTP_SERVERS [192.168.71.2/32,192.168.71.3/32]
var SQL_SERVERS 192.168.71.101/32
var DNS_SERVERS [192.168.71.100/32,192.168.71.1/32]

Again, it is important to define them all, even if you define them as the local server IP address because they are used throughout the available rulesets.

Stealth Sensors

One tip for deploying Snort sensors on either side of the firewall is to not bind an IP address to the listening network interface. This effectively puts the sensor in "stealth mode" because it will not respond to any IP-based traffic.

The sensors are usually configured to have a secondary network interface card installed that is attached to a LAN dedicated to alert logging and administration.

Enabling a network interface without an IP address is not a common practice on network-attached servers. That means there will be precious little (read none) documentation in your administration manuals on how to configure your sensor in this way. Following are some hints about how to configure some of the more common operating systems.

On Solaris systems, you must first initialize the driver and then enable the interface.

ifconfig hme0 plumb
ifconfig hme0 up

On Linux systems, ensure that the driver is loaded and just enable the interface.

modprobe –a tulip
ifconfig eth0 up

On Windows NT and 2000 systems, configure the interface, but do not bind TCP/IP to the interface. If TCP/IP is already bound, just remove TCP/IP from the interface in the Networking Control panel dialog box.

On sensors configured with no IP address, you cannot monitor traffic destined for that particular sensor, but that should not be a problem because that is not the intent of a "stealth sensor."

Enabling Preprocessor Plugins

The next section of the snort.conf configuration file defines which preprocessor plugins are to be used. The definition and configuration options for each plugin are described as comments in the snort.conf file. Some of the more common preprocessors to enable are as follows:

  • IP defragmentation detection, uncomment preprocessor defrag

  • TCP Stream Reassembly, uncomment preprocessor stream

  • HTTP decode normalizes HTTP requests so that all the Snort rules apply in the same fashion, uncomment preprocessor http_decode

  • Portscanning plugin detects UDP packets or TCP packets with the SYN flag set, uncomment preprocessor portscan

  • A complementary plugin to the portscan plugin that identifies your DNS servers so you can reduce the amount of false positives because DNS traffic is so prevalent, uncomment preprocessor portscan-ignorehosts

Defining Output Options

The output options allow you to define how and where alerts and logs get written. You can log to local files in formatted or binary format, syslog, Eventlog on Win32, XML, or any of the supported databases.

You can log to multiple output devices, but the more output you produce, the more overhead is involved with processing those logged packets and incidents. On a highly loaded server, it may be wise to just log to the local filesystem in the tcpdump binary format, which can later be retrieved and reviewed on a central console.

For the purposes of this article, I've chosen to log to a central MySQL database. The snort.conf file has documentation that explains many of the options of each type of output plugin.

The output line looks similar to the following:

output database: log, mysql user=snort_sensor dbname=snort_log host=192.168.71.20 password='pass'
output database: alert, mysql user=snort_sensor dbname=snort_log host=192.168.71.20 password='pass'

The reason for two output lines, nearly the same, is that I want to store both logged packets and alerts to the same database. You can easily separate the two into two databases if you wish.

Selecting Rules and Rulesets

The Snort rule language is fairly easy to learn. A detailed account on specifically writing rules can be found in the Snort rule-writing document: (http://www.snort.org/writing_snort_rules.htm)

Additionally, there are many sources of new rules that can be added to your ruleset. There is a mailing list dedicated to the creation of rules. The Snort Web site has a periodically updated set of rules, split out by functionality. This makes it far easier to enable or disable various classes of rules. The most popular source of Snort rules is the arachNIDS database, maintained by Max Vision. The arachNIDS database is auto-generated whenever new rules are added or changed.

The rules that are provided in the source and binary packages are slightly stale and not really maintained. They are intended primarily for helping you get Snort up and running, and not meant for production deployment. I recommend downloading the updated rules from the Snort Web site, the vision.rules file from the arachNIDS database, or a combination of the two.

The rules can easily be incorporated into your snort.conf file by using the "include" directive. Toward the bottom of the snort.conf file are examples that you can delete or comment out. When including the new rules, use fully qualified pathnames. For example:

include c:\snort\rules\Webserver-iis.rules
include /etc/snort/vision.rules
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020