Scratch that, pytbull was good enough and easy to set-up for a bit of basic testing.
On Wednesday, 25 May 2016 14:03:38 UTC+1, Tahir Hafiz wrote: > > > > On Wednesday, 25 May 2016 12:48:01 UTC+1, dan (ddpbsd) wrote: >> >> On Wed, May 25, 2016 at 4:59 AM, Tahir Hafiz <[email protected]> wrote: >> > Thanks but I think this is not quite what I am after as this seems more >> like >> > a log parser tool. >> > I think what I am looking for is an "automated intruder" tool, like a >> script >> > that can be run which will cause alerts to happen at the various OSSEC >> alert >> > levels from 0 to 16. >> > >> > I will see if a google search or two can find me an automated intruder >> tool. >> > >> >> Like nessus, nmap, or nexpose? >> > > Not really, I am just looking for a script that I can run on a box (could > be the OSSEC server box itself, could be a box where the OSSEC agents are > installed) and the script runs and triggers alerts at various levels, this > is just to demo that OSSEC works basically for the high level alerts. > What I will do is code a python script (I am not a coder but can do a few > basic things) that does that and let you guys know when it's done and if > you want to incorporate it into the OSSEC code repo itself you are more > than welcome to it. > > Every tool I have found is completely over-specced and over-laboured for > the basic task I need to do (Pytbull comes close I think), such as: > > https://www.reddit.com/r/sysadmin/comments/xi13l/what_are_good_ids_testing_tools/ > > > > > > > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
