LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Advisory Watch: August 15th, 2014
Linux Advisory Watch: August 8th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
Creating Snort Rules with EnGarde Print E-mail
User Rating:      How can I rate this item?
Source: www.linuxsecurity.com - Posted by Administrator   
Features There are already tons of written Snort rules, but there just might be a time where you need to write one yourself. You can think of writing Snort rules as writing a program. They can include variables, keywords and functions. Why do we need to write rules? The reason is, without rules Snort will never detect someone trying to hack your machine. This HOWTO will give you confidence to write your own rules.


Prerequisites:


Bill Keys
What you will need:
  • 1. A machine to do your development on. These rules should NOT be run on a production server because the rules are only meant to be examples, which you can learn from.
  • 2. Also you will need a client machine to connect to the machine which Snort is running on.
  • 3. EnGarde Secure Community 3.0.18 or above with Snort installed.


Syntax: The Guts of Rules

The syntax may look a little strange at first but this section will explain it so you can start writing your own rules. Snort rules are divided into two sections: the rule header and the rule options. First, the rule header contains rules, actions, protocol, source and destination IP address, and source and destination ports. The second part is rule options, which contains an alert message and information on the parts of the packet that should be looked at to see if the rule action should be taken.

Example:
alert tcp any any -> 192.168.1.0/24 111 (content:"|00 01 86 a5|"; msg: "mountd access";)
The text up to the first parenthesis is the rule header and the section inside the parenthesis is the ( rule options ).

Rule Actions:
This is where you describe the “who, where, and what” of a packet and what to do in the event that the rule is triggered. You can choose from the below keywords when writing the rule action.

  • alert - generate an alert using the selected alert method, and then log the packet
  • log - log the packet
  • pass - ignore the packet

Protocol:
Next part of the rule is the protocol. The more popular ones are: TCP, UDP and ICMP but Snort supports many other and continues to add new ones.

Source IP Address:
Following the protocol is the source IP address. This defines where the packet is coming from. You can use the keyword any to define all IP addresses. You can even write a rule to match any address except the one that you defined. This is done by using “!” the negation operator.

Source Port:
This is the port number where the packet is coming from. Port numbers also have the keyword any. You can also define a range of ports. This is done by using “:”. For example 1:1000 defines all ports ranging from 1 to 1000.

Direction Operator: The direction operator “->” is used to define the “direction” of the traffic in which the rule applies to. In other words, where the traffic is coming in or out of your machine.

Destination IP Address:
Next is the destination IP address. Which defines where the packet is going too. Similar to the source IP address you can use the keyword any or define a address which will not cause the rule to be triggered.

Destination Port:
Following the destination IP address is the destination port number. This is the port number where the packet is trying to connect to. The options here are the same as the source port.

Rule Options:
Everything in the parenthesis is called the rule options. One of the more popular keywords is called the content but there are many more you can use. The keyword content allows the user to set rules that search for specific content in the packet payload and trigger a response.

Example:
alert tcp any any -> 192.168.1.0/24 143 (content: "|90C8 C0FF FFFF|/bin/sh"; msg: "IMAP buffer overflow!";)
As you can see we are checking if the packet contains some Binary Byte code and text.

Basic format:

action protocol src_ip src_port direction dst_ip dst_port ( rule options)

Adding a New Rule:
Since we now have a basic understanding of the syntax of Snort rules, we can add a new rule to our system.

First log in as root and transition over to sysadm_r.

[test_server]# newrole -r sysadm_r
Authenticating root.
Password:
[test_server]# setenforce 0

Next you will need to edit the snort.conf, use your favorite editor to modify the /var/chroot/snort/etc/snort.conf. We need to include the line below:

include local.rules

This will tell Snort to use our new rules which will be stored in local.rules.

Now we can create the local.rules file.

[test_server]# cd /var/chroot/snort/etc
[test_server]# touch local.rules



Next is the fun part because its time to write the rule. Open local.rules in a editor and add the below line. Note this rule is only an example and sure not be used on a production environment.

alert tcp any any -> any 80 (msg: "Sample alert";classtype:misc-attack; sid: 2002973; rev:1;)


Last restart Snort to have your new rule take affect.

[test_server]# /etc/init.d/snortd restart

Simple Example:
Since now we have added a new rule it's time to explain what the rule does and see the rule in action.

Rule we just added:
alert tcp any any -> any 80 (msg: "Sample alert"; classtype:misc-attack; sid: 2002973; rev:1;)


How the rules works:
The above rule is triggered when a user tries to access a website. When the rule is triggered it will do an alert and display a message. The action keyword alert generates an alert using the defined method, and then logs the packet. The protocol of the packet we are detecting is TCP and all source IP addresses and port numbers are defined. The destination is defined on any IP address that is connecting to port 80. Lastly, the rules option keyword msg tells the logger and alerting engine to display the message "Sample alert".

Testing: Now you must be interested in seeing your rule in action. To see the rules firing you will need to tail the Snort alert logs.

[test_server]# cd /var/chroot/snort/var/log/snort
[test_server]# tail -f alert

Now open a web browser and enter your test_server's IP address.

Look at the Snort's alert logs. You will see a message from Snort that was cause by the new rule we just added.
[**] [1:2002973:1] Sample alert [**]
[Classification: Misc Attack] [Priority: 2]
12/12-15:35:22.130162 test_client:35524 -> test_server:80
TCP TTL:64 TOS:0x0 ID:35734 IpLen:20 DgmLen:52 DF
***A**** Seq: 0x5F3B46F0 Ack: 0x85067266 Win: 0xB7 TcpLen: 32
TCP Options (3) => NOP NOP TS: 49925498 1529581

Detecting Payload Example:
Add the below line to /var/chroot/snort/etc/local.rules
alert tcp any any -> any 80 (content:"index.pl";sid:12345678;rev:1;classtype:misc-attack;)

As you can see we wrote a rule to detect any traffic connecting to port 80 with the content of "index.pl".

To test this do the above steps to tail the Snort's alert logs. Then open a web browser and enter http://test_server/index.pl.

Notice in the Snort's alert log you should be able to see a message similar to the one below.
[**] [1:2002973:1] Sample alert [**]
[Classification: Misc Attack] [Priority: 2]
12/13-08:13:20.545431 test_client:32950 -> test_server:80
TCP TTL:64 TOS:0x0 ID:11275 IpLen:20 DgmLen:52 DF
***A**** Seq: 0x188A67A3 Ack: 0xF74B200C Win: 0xD8 TcpLen: 32
TCP Options (3) => NOP NOP TS: 64899598 45624

This is only the start:
With the knowledge you have now you can start digging deeper into the writing your own rules. The official Snort documentation contains every in and out of the syntax. As you journey deeper into writing your own Snort rules you will notice attackers on your network that you have never seen before.

References:

Official Snort website

www.snort.org

Comments
SnortWritten by Joe on 2007-12-19 21:56:57
Nice how-to Snort is cool stuff
AttacksWritten by mike on 2008-01-07 08:58:23
It's interesting to see how many attacks you can see when using Snort
What theWritten by Intruded on 2008-01-25 04:18:57
This is what im looking for. Explain the basics to improve more. Thx, great job dude
Network AdministratorWritten by Matt Hall on 2008-07-11 09:19:00
I don't know if its already in existence but does snort have any rules for ip resolution of attacks and a possible way to whois and trace them?If not I'd love to try and write such a rule I would think it would remove a vast amount of time fro resolving attackers information and staying more alert to if its coming from any specific ip block.
Need Help writing SNORT Rules for the foWritten by HILL on 2008-11-03 14:39:51
1. (1 point) Write a Snort rule that will alert on TCP traffic exiting the 10.0.1.0/24 network with the content "proprietary". I do not care where the traffic is going or what ports it is using. When Snort creates the alert it should read "Proprietary information leaving!" 
 
2. (1 point) Write a Snort rule that will log any TCP traffic entering into the 192.168.100.0/24 and 10.2.2.0/24 networks with destination ports 1 through 1024. I do not care about the source IP addresses or source ports. When Snort logs the traffic it should read "Incoming to low ports". 
 
3. (1 point) Write a Snort rule that will alert on UDP traffic entering the 192.168.10.0/24 network that contains the content "cgi-bin" anywhere between the 5th byte offset to the 25th byte offset. The alert should trigger on both lowercase and uppercase content. I do not care about the source ports or destination ports. When Snort creates the alert it should read "UDP CGI exploit". 

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

 
< Prev   Next >
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Google Fixes 12 Vulnerabilities in Chrome 36
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.