RE: [Database-devel] questions...

Thanks for all the info... With some minor tweaking, I was able to get
almost everything to work. From looking at the source, It looks like the
table DETECTEDVULNERABILITY that was created with the nessus_db_schema.mysql
should be really called vulnerability. I added this table and changed all of
the other table names to lowercase, but DETECTEDVULNERABILITY or
vulnerability are still not getting populated. It looks like most of the
other tables are getting populated though. I checked the nessusd.dump and
nessusd.messages and I am not getting any errors or messages regarding this
problem (I did get messages when I had uppercase tables names). Does anyone
have any hits?

Thanks,
Jeff


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Marsh, Cory
Sent: Tuesday, January 13, 2004 5:47 PM
To: Javier Fernandez-Sanguino
Cc: [email protected]
Subject: RE: [Nessus-devel] [Database-devel] questions...

1. I would not recommend using the import-nbe.pl script.  The NESSUS_SQL
code captures a lot of state information (such as knowledgebase, execution
time, status, etc)  This information is not captured in the nbe output.
Going this route will lead to incomplete data.  I also believe that the
import-nbe.pl scripts do not work with the NESSUS_SQL code as is.

With regard to #2, the db_compress feature is not currently supported.

With regard to #3, I have an updated version of nessus-extract.pl that works
with the code in NESSUS_SQL.  I have also updated some of the regular
expressions to be more robust and case insensitive.

On a more general note, the tables have been renamed to all lowercase (it is
quite a pain to type uppercase column names in the SQL command line)

I also have a Perl script that generates a lot of different reports from the
database.  These include standard reports (similar to nessus html save),
executive summary reports, flat text files and Excel spread sheets (thanks
to Spreadsheet::WriteExcel).  The Perl reporting code also  auto remediates.
This means that if an issue was detected on scan #1 and then checked for but
not found on scan #6, this issue will be included in the report as fixed.
This is a time consuming feature but quite worthwhile.

I also have updated SQL code with speed improvements and support for auto
magically creating inno db tables for MySQL.  Postgre support should be soon
now.

I will try and get the new code to Javier some time in the next week.

-Cory


_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel