]> git.pld-linux.org Git - packages/snort.git/blame - README.snort-stuff
- finished update to 2.4.3
[packages/snort.git] / README.snort-stuff
CommitLineData
3914b6b8
MP
1$Header$
2
3The following scripts were developed from ideas gleaned from the snort
4mailing list, with some stuff I came up with on my own. It makes
5for a fairly easy to manage and simple snort configuration on a Red
6Hat Linux system.
7
8The basic files are included in the snort-stuff.tar file (which unpacks the
9files into the right places for each file, if untarred in the / directory.)
10This README file then resides in /usr/doc/snort-stuff (to go along with Red
11Hat's documentation directory structure.) This is the net effect of
12what an RPM file would do, but I don't have time right now to go that
13far. You can find the original at:
14
15 http://staff.washington.edu/dittrich/misc/snort-stuff.tar
16
17Right now, the basic files are:
18
19/usr/doc/snort-stuff/README.snort-stuff
20 This file.
21/etc/rc.d/init.d/snort Red Hat Linux startup script for snort
22/usr/local/etc/check-snort Daily checkup script (run by cron)
23/usr/local/etc/rules.base Base rules file (needs to be modified
24 to suit your network.)
25
26INSTALLATION
27
281). Unpack the files.
29
30You can just unpack this tar file into /, like this:
31
32 # cd /
33 # tar -xvf /path/to/snort-stuff.tar
34 etc/rc.d/init.d/snort
35 usr/local/etc/check-snort
36 usr/local/etc/rules.base
37 usr/doc/snort-stuff/README
38
392). Create snort log and archive directories.
40
41The "snort" rc startup script and "check-snort" log file processor
42assume you are using the rules.base as defined here, and that you store
43snort log files in /var/log/snort and archive prior days' logs in
44/var/log/snort/archive. Create these now if they don't already exist:
45
46 # mkdir -p /var/log/snort/archive
47 # chown -R root.wheel /var/log/snort
48 # chmod -R 640 /var/log/snort
49
503). Set up snort rules files.
51
52You now must edit /usr/local/etc/rules.base to set your own network
53addresses and list of DNS servers you want to ignore for portscan
54reports (if you want to do this).
55
56You next need to set up your rules, which in this case are just the rules
57set up as part of ArachNIDS by Max Vision. You can get these with
58"wget" (if you don't have it, you might as well install it now from your
59favorite Red Hat archive site, as it is needed by the "check-snort" script.)
60
61 # wget --output-document=/usr/local/etc/vision.rules \
62 http://dev.whitehats.com/ids/vision.rules
63
644). Set up daily checkup script.
65
66From the root account, edit your crontab (with "crontab -e") and add
67the following line (or one adjusted to fit the time of day you wish
68to process snort logs):
69
70 0 0 * * * sh /usr/local/etc/check-snort
71
725). Configure snort startup script and start snort running.
73
74You now must install the snort startup script in order for snort to
75be run at boot and stopped/started by check-snort.
76
77 # chkconfig --add snort
78
79You can now start snort using this rc file.
80
81 # /etc/rc.d/init.d/snort start
82
83Lastly, check to see that it started correctly.
84
85 # /etc/rc.d/init.d/snort status
86 snort (pid 10739) is running...
87
88You will now be mailed copies of alert and portscan files, and
89notified of changes to the vision.rules file when necessary. (You
90will also get email from cron with the snort stop/start messages to
91confirm that things are working as expected.)
92
93If you have any suggestions for changes, send them to me at
94<dittrich@cac.washington.edu>.
This page took 0.070174 seconds and 4 git commands to generate.