RE: [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



-----Original Message-----
From: Javier Fernandez-Sanguino [mailto:[email protected]]
Sent: Tuesday, January 13, 2004 11:25 AM
To: [email protected]
Subject: Re: [Nessus-devel] [Database-devel] questions...


Jeff Dell wrote:

> I have been playing with NESSUS_SQL and I have a few questions:
> 
> 1. In he README.txt file it says to use import-nbe.pl to import old nessus
> reports into the database. I can't seem to find it. It is not located where
> it says.

It's available in the nessus-tools CVS directory, branch NESSUS_SQL
http://cvsweb.nessus.org/cgi-bin/cvsweb.cgi/nessus-tools/, more 
precisely in
http://cvsweb.nessus.org/cgi-bin/cvsweb.cgi/nessus-tools/nessus-extract/?only_with_tag=NESSUS_SQL

> 
> 2. How do I start nessus so it utilizes the database?

If you have configured it properly (i.e. 'configure --with-mysql') you 
have to configure nessusd.conf properly with:

db_user = USER_TO_CONNECT_WITH
db_pass = PASSWORD_TO_USE_FOR_CONNECTION
db_host = DATABASE_HOST
db_database = DATABASE_NAME (default name is 'Nessus_Scans')
db_port = REMOTE_DATABASE_PORT (default depends on the DB server)
db_make_tables = yes|no
db_compress = yes|no

This step is not in the readme I will add it there, sorry.
> 
> 3. When extracting the plugins with nessus -qSp it uses a table called
> plugins, when using the script nessus-extract.pl, it uses the table
> nessus-plugindata. Which one is really used by nessus?

Ummm... are you using the nessus_extract.pl from the NESSUS_SQL 
branch? The one from the NESSUS_SQL branch _does_ use the 'PLUGINS' 
table. Since you do not see import_nbe either that might be the reason 
you are seeing those differences.

> 
> 4. Is there any talk about NESSUS_SQL merging in with NESSUS?

As Renaud said, it will probably be added soon (but disabled per 
default since it needs wider testing).

Regards

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



[INFO] -- Access Manager:
This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.  Thank you.   A2


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