Hi Tim

On Thursday 23 April 2009 22:11:27 you wrote:
> I'm not planning to take these scripts any further, though I am thinking
> of doing something with MySQL, something a bit more powerful than static
> files!.
>
> Has this been done already?
>
> Perhaps something with 'flash' DashBoards with various summaries,
> historical charts, grouping scan jobs into platforms, services,
> departments etc. In particular, I want to create a realtime chart for
> regular scans. I perform multiple scans some 4-8 times per day and
> create alerts when something is found on my private systems from
> internet scans. I do this with commercial tools already but I would like
> something opensource for sure.
>
> Would be happy for feedback on this also. Please note, I dont want to do
> anything for Nessus, it will be just OpenVas if I do.
I find it looks beautiful and very useful.
Well done, I really enjoyed it.

Some of the ideas you mentioned are discussed from time to time and the 
project will very likely develop in that direction.

In principle there are two approaches: 1) Generate output from the client and 
further process it. 2) Work on the client(s) to make their output better.

I think in general the development will drive in the direction of the latter 
option. That means, e.g. sql 'from the source' and not generated out of the 
xml report; protocol changes (are underway) to query useful information 
directly, etc. We have quite some good ideas, but we sure can need more.

Please (feel free to) join the irc channel 
(http://openvas.org/online-chat.html), most developers hang out there during 
european day time.

Good work.
-- felix

-- 
Felix Wolfsteller |  ++49-541-335 08 3451  |  http://www.intevation.de/
PGP Key: 39DE0100
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to