Re: Using a database as backend for Nessus (current state and volunteering for development)

> While a db back-end is a great idea, keep in mind one
> _very_ important design issue.  If you have a db, and
> you issue a new release of Nessus, you don't have nearly
> the same flexibility changing the db design as you do
> changing nessus functionality.
>
> People will have lots of scans in the db, and if you go
> and change the schema, you're now forced to do a db conversion.
> It's not impossible. Not even terribly difficult. But it
> certainly can be prone to problems.

Having a standard Nessus backend database will bring lots of benefits to
the Nessus users, which in my opinion will overweight concerns about
possible schema or data migration down the road.

Alex Zimin
[email protected]