Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We need to setup an intrusion detection system (IDS) on our linux proxy server. Please suggest intrusion detection systems ? anything else than Snort ?

And ... does snort have a good web interface ?

share|improve this question
"good" is a relative term...what do you mean by "good"? I don't think snort itself has a web interface, but there are third party programs that can interface to the logs and stats and manage the configuration, as I recall. – Bart Silverstrim May 25 '10 at 12:50
up vote 5 down vote accepted

Your question is rather ambiguous. I've answered a similar ambiguous question here:

SNORT is pretty much the defacto standard for Open Source network based IDS. The Wikipedia page lists others as well. There's a variety of front-ends for SNORT. An Open Source one is BASE and Sourcefire, the company who owns SNORT, sells a commercial one.

share|improve this answer

For just network monitoring or intrusion on the system? A file integrity scanner can be beneficial, but it takes work to maintain as it needs updating each time you update the system and needs a bit of initial tuning. See the Open Source Tripwire page for information on that.

Wikipedia has some links to IDS systems as well.

share|improve this answer
Yes, for network monitoring. – nitins May 25 '10 at 12:18

I used OSSEC HIDS. Basically, it checks file integrity (/etc/passwd,...) and parses log files (syslog, auth.log,...). It has usable web interface and email notification. But nothing special, I guess.



share|improve this answer
I use OSSEC quite a bit and I really like it. Fairly easy to setup and you can have your agents report to one central location if you have multiple proxies or do a stand alone install. It has some default rules that detect attacks/errors but also allows you to create as many rules as you want and modify the current rule set. – user22492 May 25 '10 at 14:52

i'd say nothing better than command-level settings for security solutions to control everything implemented... though

for a GUI to Snort, there is : http:// / don't know how good you'll find it, but can have a look at Scrrenshots @ http:// / screenshots.html

other than SNORT, nice IDS is BRO :

read a research article over it... has a nice plug-able architecture... works good

share|improve this answer

IDS is different from IPS (intrusion protection system). Why the requirement for IDS, do you plan on reporting attacks or building firewalls to stop dirty network traffic?

Squid and other proxys can be configured to only transfer clean traffic... There is allot of packets of dirty data floating around on the internet, allot of them can be ignored.

Snort with an interface like BASE or ACID use a lot of CPU cycles, RAM and SQL space (Physical storage). If your dealing with a production level environment IDS must be setup correctly or it becomes pointless very quickly.

If you run snort on your proxy server, databases and logs are not maintained on a weekly basis, sooner rather than later your proxy server is going to hang from lack of resources.

So say you have a genuine interest in IDS, You will require a serious server depending on your traffic though-put to support both the Squid + Snort + Apache + MySQL + PHP WebGUI.

A more desirable option would be to setup a dedicated machine and dedicated monitoring NIC connected to a mirror port on your main switch.

Good luck, IDS is more interesting than useful.

Check out HoneyPot Project and OSSEC

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.