-
Website
http://www.matasano.com/log -
Original page
http://www.matasano.com/log/661/pro-forma-06-punditry-results/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Press Controls
3 comments · 2 points
-
ChrisMtso
12 comments · 1 points
-
Eric Monti
11 comments · 1 points
-
StatlerAndWaldorf
12 comments · 3 points
-
Dave G.
7 comments · 1 points
-
-
Popular Threads
NAC was countered with http://kevin.sf.net
CSA was countered by Slipfest at CanSecWest
MARS detected one script kiddie running land.c until they graduated from idiot university and ran snot/sneeze/etc
combine the usefulness of Cisco IPS and it appears we have a winner for "most silicon snake-oil in 2006".
"What’s taking you guys so long?"
Same as what I mentioned in our discussion thread: ongoing maintainance and log source support.
http://www.ossec.net/wiki/index.php/Supported-Logs
Most people think of it as an HIDS only, but its log analysis and correlation options are side by side with most commercial solutions (and even better most of the times).
Link to it: http://www.ossec.net
Thanks,
Daniel Cid
I can't tell you how many really cool ideas I had pitched by VCs for a SIM based on a really neat technical approach. None of them figured in the issue of integrating with all the ticketing systems or building a good GUI with functional workflow (see BASE & SGUIL vs. ACID in terms of workflow clarity), etc...
I don't expect to ever see a complete open source SIM. The correlation engines have existed for a couple years though.
"Expect a mainstream open-source
combination of Argus and Sguil to own the security management
conversation next year."
Sorry to let you down. I'd take half the blame except adding Argus to Sguil doesn't a SIM make (http://infosecpotpourri.blogspot.com/2006/01/sg...).
Also, Sguil has used SANCP (or a similar app) to provide flow/connection/session data since its inception. I've done a bit of research and haven't been able to find a compelling reason to create some type of hook between Sguil and Argus (yet).
OSSEC (http://www.ossec.net) is starting to get more exposure though and as much as I despise the term SIM, it is starting to fill that void (even if it is labeled as a HIDS). Here is a list of log types it supports: http://www.ossec.net/wiki/index.php/Supported-Logs.
On #1 - why didn't the # of M$ vulnerabilities drop? Is it too early (i.e. you'll repeat this prediction for 2007 and declare you were just ahead of the curve) or are their investments in SDL and security audit not working?
I'm sure we're lacking marketing but at least I'd like to know why:
#4 OSSIM
is not an option, after almost five years of development.
You get:
- Correlation engine.
- Simple correlation engine language (xml).
- Lightweight plugins.
- Cross correlation (Snort-Nessus)
- Various anomaly detection engines (OS, Mac, Services, IP/TCP/UDP/...)
- Website provides more information.
I'd be glad to provide more information, samples and documents in case I get the opportunity.
Dominique
you can take a look at http://www.ossim.net to check it.
Hkr.