Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm looking for an informed opinion on the advantages of ossec in comparison to snort/tripwire/nessus

Therefore anyone shed any light on what features ossec brings that cant be replicated via tripwire (or iwatch) and snort, perhaps with nessus used also ? Particually in regards to PCI compliance sections 10 and 11.

Moreover, would the snort etc hybrid setup bring any features which are not present in ossec ?

share|improve this question

3 Answers 3

up vote 4 down vote accepted

This isn't a fair comparison as not all these products are doing the same thing.

Snort is a Network Intrusion Detection System.

ossec is a host-based network intrusion system as is tripwire and iwatch as they monitor file/filesystem/system integrity for changes and anomalies.

Nessus is Tenable's vulnerability scanner, which scans over the network, authenticating where it can (and has been provided credentials), looking for known vulnerabilities and potential misconfigurations against a large "feed".

share|improve this answer
    
ok, i guess really you are correct in it not being a like for like comparison. Ive used snort and tripwire in the past, but Im unaware of the advantages, if any, of ossec by comparison as i've not used it. From what i can tell it should be possible to replicate all of ossec's functionality in relation to PCI compliance with either tripwire or iwatch, and if so this would be my preffered option (and then layer nessus and snort on top). I just wonder if ossec has something which the others lack. –  Sirex Jul 30 '10 at 15:38
1  
Nessus is great for seeing how well Snort is working, but as with all intrusion detection system (host or network-based), you need to have a really quiet network and a rock-solid change management policy in practice (not just written down in a binder somewhere) or you'll spend your time chasing down false positives and eventually tune it out (or turn it off) if it's "crying wolf" too often. –  gravyface Jul 30 '10 at 15:48

I agree with the others that have posted, they have different goals in mind. Since your primary question seems to be about OSSEC I assume you are mostly looking for a centralized manager of sorts. OSSIM and Prelude are other options in that area, although I think OSSIM is a little nicer.

OSSIM ~ Prelude

Snorby is worth looking at in regards to Snort management and reporting.

Snorby

I found this page to be a (although slightly biased) good read as for as file system ID's are concerned.

A comparison of several host/file integrity monitoring programs

share|improve this answer

As far as I can tell, tripwire watches filesystem changes which OSSEC does as well. But OSSEC watches logs as well and has a long list of rules to identify and notify of abnormal activity. This rules are easy to define, so you can have your own local rules as well.

OSSEC has a central manager where you can control configuration and activity of agents.

OSSEC has rules for snort, so you can chain them together and use OSSEC to filter through snort alerts.

Regarding PCI monitoring, OSSEC can help analyze logs in a automated way.

share|improve this answer

Your Answer

 
discard

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.