From: Don Parker (dparker@rigelksecurity.com)
Date: Thu Mar 11 2004 - 16:29:31 EST
You should be using all the openly available exploit code out there in addition to some
funky changes to them. You still need a baseline to work with, and the publicly available
stuff provides just that. Not only will this help you verify your IDS, it will also help
you to tweak the signatures as required for your environment. There are quite a few
factors beyond the normal stuff as well to test on.
One of the key areas as well is to make sure that your IDS is properly detecting
shellcode, and not smothering you with an avalanche of false positives. Properly
verifying your IDS or IPS for that matter is not an easy task, nor is it a quick one. If
you want to do it properly you need the requisite skills also. You don't want someone who
does not even understand the exploits he/she is running to test the signatures. There is
far more to this then simply throwing exploits at it.
Cheers!
Don
-------------------------------------------
Don Parker, GCIA
Intrusion Detection Specialist
Rigel Kent Security & Advisory Services Inc
www.rigelksecurity.com
ph :613.249.8340
fax:613.249.8319
--------------------------------------------
On Mar 11, Frederic Charpentier <fcharpentier@xmcopartners.com> wrote:
hi.
Some tools are ok to test an IDS, but this is not the best way to do that.
A tool will generate stupids triggers to wake up your IDS, like old CGIs
attacks et low-level tcp/ip tricks.
The best way is to be understand the patterns you set up in your IDS.
No matters that some stupid guys performs ping-attacks or silly cgis
attacks !!
* Try bufferoverflow/shellcodes patterns, and do simple test like :
copy/paste a shellcode into a telnet session.
* For http intrusion detection, detecting IIS nimda attacks is not
efficient, try to trigger your IDS with XSS/SQL-Injection techniques is
much more efficient:
sample :
<a href='http://website/script?req=