Mailing List Archive: How to start exporting Nessus results to a DB

How to start exporting Nessus results to a DB

brian_anon at hotmail

Feb 19, 2003, 5:54 PM

Post #1 of 16 (3820 views)

William and Javier,

I have been following your message threads on exporting Nessus scan results
to MySQL. I see that you both are very active in this initiative.

I am about to setup a Nessus server to begin scanning some systems on a
regular basis. What do I need to do to start getting the scan results into
a MySQL DB server?

Once the results are available in the DB I expect to begin creating report
templates using Crystal.

By the way, I happen to use VMWare for all my testing so I can make these
basic systems available for anyone interested. I'm currently creating a
test environment with the following virtual machines (all based on RH 7.3):
1. Snort IDS Sensor
2. MySQL DB Server, Apache Web Server, ACID, SnortCenter
3. Nessus Server

For #1 and #2 I am following the build docs from www.snort.org. For #3 I
will build the OS similar to #1.

Other plans I have are to create some PHP scripts that will parse the
results of other scans (nmap and HFNETCHK) and application log files (McAfee
NetShield and WebShield) to store in a MySQL DB for reporting with Crystal.

If this is successful. I'd like to expand by creating a portal to all this
information using a content management system like Postnuke.

Any tips or suggestions would be greatly appreciated.

Regards,
Brian

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail

Re: How to start exporting Nessus results to a DB [ In reply to ]

jfernandez at germinus

Feb 20, 2003, 4:40 AM

Post #2 of 16 (3780 views)

Brian Anon wrote:
> William and Javier,
>
> I have been following your message threads on exporting Nessus scan
> results to MySQL. I see that you both are very active in this initiative.

Yep. The schema is not finished yet and there's still things that could
be improved in it.

>
> I am about to setup a Nessus server to begin scanning some systems on a
> regular basis. What do I need to do to start getting the scan results
> into a MySQL DB server?
>

For the moment, I have not tested the code in the CVS, William? In any
case you would need to:

- checkout the CVS branch NESSUS_SQL
- compile the code using -DUSE_DATABASE
- probably tweak the Makefiles to include the proper libraries (Code is
currently only available for MySQL but there should be Postgresql code soon)

I still have to apply a patch William sent me yesterday to update the
structure but there's still a lot to do in order to make it
autoconfigure & compile the code properly.

You can, however, use some of the tools in the CVS (NESSUS_SQL branch)
to process nbe reports and put them in the database. I'm working on
those while William is polishing the code (and updating to reflect the
schema changes).

> Once the results are available in the DB I expect to begin creating
> report templates using Crystal.
>
> By the way, I happen to use VMWare for all my testing so I can make
> these basic systems available for anyone interested. I'm currently
> creating a test environment with the following virtual machines (all
> based on RH 7.3):
> 1. Snort IDS Sensor
> 2. MySQL DB Server, Apache Web Server, ACID, SnortCenter
> 3. Nessus Server

¿Three different virtual machines?

>
> For #1 and #2 I am following the build docs from www.snort.org. For #3

I've found it very easy to setup 1+2 in a single system using Debian,
all the software is already available, save for SnortCenter.

> I will build the OS similar to #1.
>
> Other plans I have are to create some PHP scripts that will parse the
> results of other scans (nmap and HFNETCHK) and application log files
> (McAfee NetShield and WebShield) to store in a MySQL DB for reporting
> with Crystal.

It would be nice to see those (once available).

>
> If this is successful. I'd like to expand by creating a portal to all
> this information using a content management system like Postnuke.
>
> Any tips or suggestions would be greatly appreciated.
>

Check out inprotect.com they have a portal to do automated vulnerability
assessment with Nessus. IIRC plugin information and scans are introduced
in the MySQL database.

Regards

Javi

Re: How to start exporting Nessus results to a DB [ In reply to ]

wjh3710 at osfmail

Feb 20, 2003, 7:22 AM

Post #3 of 16 (3790 views)

On Thu, 20 Feb 2003, Javier Fernandez-Sanguino wrote:

> Brian Anon wrote:
> > William and Javier,
> >
> > I have been following your message threads on exporting Nessus scan
> > results to MySQL. I see that you both are very active in this initiative.
>
> Yep. The schema is not finished yet and there's still things that could
> be improved in it.
>
> >
> > I am about to setup a Nessus server to begin scanning some systems on a
> > regular basis. What do I need to do to start getting the scan results
> > into a MySQL DB server?
> >
>
> For the moment, I have not tested the code in the CVS, William? In any
> case you would need to:
>
> - checkout the CVS branch NESSUS_SQL
> - compile the code using -DUSE_DATABASE
> - probably tweak the Makefiles to include the proper libraries (Code is
> currently only available for MySQL but there should be Postgresql code soon)
>
> I still have to apply a patch William sent me yesterday to update the
> structure but there's still a lot to do in order to make it
> autoconfigure & compile the code properly.
>
> You can, however, use some of the tools in the CVS (NESSUS_SQL branch)
> to process nbe reports and put them in the database. I'm working on
> those while William is polishing the code (and updating to reflect the
> schema changes).
>
No, the code in CVS has not been tested. I've been quite busy and am
waiting for the schema to get stablized. I also need to setup a MySQL
server to test it on ;) I'll probably try to test it tomorrow.

To compile the Nessus code you need to do the following:
Get the newest code from the NESSUS_SQL CVS (after Javi updates it)
Add the following options to the end of nessus-core/nessusd/cflags:
-I/usr/local/include/mysql
-DUSE_DATABASE
-DUSE_MYSQL
Apply the attached diff patch to nessus-core/nessusd/Makefile
% patch nessus-core/nessusd/Makefile < Makefile.diff
Run make

NOTE: The nessus-core/configure script has to be run BEFORE these steps
are done.

> > Once the results are available in the DB I expect to begin creating
> > report templates using Crystal.
> >
> > By the way, I happen to use VMWare for all my testing so I can make
> > these basic systems available for anyone interested. I'm currently
> > creating a test environment with the following virtual machines (all
> > based on RH 7.3):
> > 1. Snort IDS Sensor
> > 2. MySQL DB Server, Apache Web Server, ACID, SnortCenter
> > 3. Nessus Server
>
> ¿Three different virtual machines?
>
> >
> > For #1 and #2 I am following the build docs from www.snort.org. For #3
>
> I've found it very easy to setup 1+2 in a single system using Debian,
> all the software is already available, save for SnortCenter.
>
> > I will build the OS similar to #1.
> >
> > Other plans I have are to create some PHP scripts that will parse the
> > results of other scans (nmap and HFNETCHK) and application log files
> > (McAfee NetShield and WebShield) to store in a MySQL DB for reporting
> > with Crystal.
>
> It would be nice to see those (once available).
>
> >
> > If this is successful. I'd like to expand by creating a portal to all
> > this information using a content management system like Postnuke.
> >
> > Any tips or suggestions would be greatly appreciated.
> >
>
> Check out inprotect.com they have a portal to do automated vulnerability
> assessment with Nessus. IIRC plugin information and scans are introduced
> in the MySQL database.
>
>
> Regards
>
> Javi
>
>

----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: wjh3710@rit.edu

Re: How to start exporting Nessus results to a DB [ In reply to ]

jfernandez at germinus

Feb 20, 2003, 9:21 AM

Post #4 of 16 (3787 views)

William Heinbockel wrote:

> NOTE: The nessus-core/configure script has to be run BEFORE these steps
> are done.
>

Not any longer if you are using CVS sources.

For your information I have just updated the configure.in code so that
it can be used with options: --with-mysql, --with-postgresql,
--with-oracle, --with-odbc (based on snort's autoconfiguration scripts)

Using these options will add the new code into nessusd. It won't be
included unless you explicitly ask for it (i.e. -DUSE_DATABASE will not
be set). I've also changed the Makefile with William's patch so that
save_db gets compiled. It has to be tweaked though so that it is _not_
compiled if -DUSE_DATABASE is not set.

In any case, I'm having issues compiling when enabling --with-mysql
(only code available at the time is -DUSE_MYSQL) however it compiles
fine w/o.

Hopefully, this will help get the database code into the HEAD branch
faster since now people will not have DB issues unless they explicitly
enable the code with the --with-XX options :-)

Regards

Javi

Re: How to start exporting Nessus results to a DB [ In reply to ]

Feb 21, 2003, 7:52 PM

Post #5 of 16 (3783 views)

Gentlemen,
I'm very interested in helping with integrating Nessus results to a
database. Is anyone working on the Postgres code? If not, I'd be more than
happy to do so.

-Tony

Brian Anon wrote:
> William and Javier,
>
> I have been following your message threads on exporting Nessus scan
> results to MySQL. I see that you both are very active in this initiative.

Yep. The schema is not finished yet and there's still things that could
be improved in it.

>
> I am about to setup a Nessus server to begin scanning some systems on a
> regular basis. What do I need to do to start getting the scan results
> into a MySQL DB server?
>

For the moment, I have not tested the code in the CVS, William? In any
case you would need to:

- checkout the CVS branch NESSUS_SQL
- compile the code using -DUSE_DATABASE
- probably tweak the Makefiles to include the proper libraries (Code is
currently only available for MySQL but there should be Postgresql code soon)

I still have to apply a patch William sent me yesterday to update the
structure but there's still a lot to do in order to make it
autoconfigure & compile the code properly.

You can, however, use some of the tools in the CVS (NESSUS_SQL branch)
to process nbe reports and put them in the database. I'm working on
those while William is polishing the code (and updating to reflect the
schema changes).

> Once the results are available in the DB I expect to begin creating
> report templates using Crystal.
>
> By the way, I happen to use VMWare for all my testing so I can make
> these basic systems available for anyone interested. I'm currently
> creating a test environment with the following virtual machines (all
> based on RH 7.3):
> 1. Snort IDS Sensor
> 2. MySQL DB Server, Apache Web Server, ACID, SnortCenter
> 3. Nessus Server

¿Three different virtual machines?

>
> For #1 and #2 I am following the build docs from www.snort.org. For #3

I've found it very easy to setup 1+2 in a single system using Debian,
all the software is already available, save for SnortCenter.

> I will build the OS similar to #1.
>
> Other plans I have are to create some PHP scripts that will parse the
> results of other scans (nmap and HFNETCHK) and application log files
> (McAfee NetShield and WebShield) to store in a MySQL DB for reporting
> with Crystal.

It would be nice to see those (once available).

>
> If this is successful. I'd like to expand by creating a portal to all
> this information using a content management system like Postnuke.
>
> Any tips or suggestions would be greatly appreciated.
>

Check out inprotect.com they have a portal to do automated vulnerability
assessment with Nessus. IIRC plugin information and scans are introduced
in the MySQL database.

Regards

Javi

Re: How to start exporting Nessus results to a DB [ In reply to ]

earnoth at comcast

Feb 21, 2003, 10:37 PM

Post #6 of 16 (3789 views)

On Friday 21 February 2003 21:52, Tony Carter wrote:
> Gentlemen,
> I'm very interested in helping with integrating Nessus results to a
> database. Is anyone working on the Postgres code? If not, I'd be more than
> happy to do so.
>
> -Tony

Tony, I've made a commitment to do so, but I would certainly welcome your help
in the Postgres side of the house (perhaps we could divide up the functions
to be written between each of us). Right now, William Heinbockel is refining
something he's written for MySQL. Javier has expressed to me that he would
rather the Postgres code wait until what William's current effort is done so
the two lines can proceed together and not independently.

--
Eric I. Arnoth CISSP (http://www.isc2.org)
earnoth@comcast.net
http://mywebpages.comcast.net/earnoth
¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø

Re: How to start exporting Nessus results to a DB [ In reply to ]

wjh3710 at osfmail

Feb 22, 2003, 9:08 AM

Post #7 of 16 (3787 views)

Tony,
Right now Javi and I are working on abstracting the database code
from the Nessus main code and getting the configure file to properly
setup the flags and include the database libraries.

Once that is finished, to add another database, you'll be able to use
my mysql code as a guideline and change the mysql library calls and
queuries to whatever database you want. This will ensure that the
databases are layed out according to the schema and allow someone with
very little C knowledge to add their own database to the mix.

I am sure something will be posted to the nessus-dev list once
Javi and I feel that enough progress has been made detailing how
people can add their own database to Nessus. Until that time,
you may want to follow our development in this list and in the
NESSUS_SQL CVS tree.

----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: wjh3710@rit.edu

On Fri, 21 Feb 2003, Tony Carter wrote:

> Gentlemen,
> I'm very interested in helping with integrating Nessus results to a
> database. Is anyone working on the Postgres code? If not, I'd be more than
> happy to do so.
>
> -Tony
>
>
> Brian Anon wrote:
> > William and Javier,
> >
> > I have been following your message threads on exporting Nessus scan
> > results to MySQL. I see that you both are very active in this initiative.
>
> Yep. The schema is not finished yet and there's still things that could
> be improved in it.
>
> >
> > I am about to setup a Nessus server to begin scanning some systems on a
> > regular basis. What do I need to do to start getting the scan results
> > into a MySQL DB server?
> >
>
> For the moment, I have not tested the code in the CVS, William? In any
> case you would need to:
>
> - checkout the CVS branch NESSUS_SQL
> - compile the code using -DUSE_DATABASE
> - probably tweak the Makefiles to include the proper libraries (Code is
> currently only available for MySQL but there should be Postgresql code soon)
>
> I still have to apply a patch William sent me yesterday to update the
> structure but there's still a lot to do in order to make it
> autoconfigure & compile the code properly.
>
> You can, however, use some of the tools in the CVS (NESSUS_SQL branch)
> to process nbe reports and put them in the database. I'm working on
> those while William is polishing the code (and updating to reflect the
> schema changes).
>
> > Once the results are available in the DB I expect to begin creating
> > report templates using Crystal.
> >
> > By the way, I happen to use VMWare for all my testing so I can make
> > these basic systems available for anyone interested. I'm currently
> > creating a test environment with the following virtual machines (all
> > based on RH 7.3):
> > 1. Snort IDS Sensor
> > 2. MySQL DB Server, Apache Web Server, ACID, SnortCenter
> > 3. Nessus Server
>
> ¿Three different virtual machines?
>
> >
> > For #1 and #2 I am following the build docs from www.snort.org. For #3
>
> I've found it very easy to setup 1+2 in a single system using Debian,
> all the software is already available, save for SnortCenter.
>
> > I will build the OS similar to #1.
> >
> > Other plans I have are to create some PHP scripts that will parse the
> > results of other scans (nmap and HFNETCHK) and application log files
> > (McAfee NetShield and WebShield) to store in a MySQL DB for reporting
> > with Crystal.
>
> It would be nice to see those (once available).
>
> >
> > If this is successful. I'd like to expand by creating a portal to all
> > this information using a content management system like Postnuke.
> >
> > Any tips or suggestions would be greatly appreciated.
> >
>
> Check out inprotect.com they have a portal to do automated vulnerability
> assessment with Nessus. IIRC plugin information and scans are introduced
> in the MySQL database.
>
>
> Regards
>
> Javi
>
>

Re: How to start exporting Nessus results to a DB [ In reply to ]

wjh3710 at osfmail

Feb 22, 2003, 9:14 AM

Post #8 of 16 (3789 views)

On Sat, 22 Feb 2003, Eric Arnoth wrote:

> On Friday 21 February 2003 21:52, Tony Carter wrote:
> > Gentlemen,
> > I'm very interested in helping with integrating Nessus results to a
> > database. Is anyone working on the Postgres code? If not, I'd be more than
> > happy to do so.
> >
> > -Tony
>
> Tony, I've made a commitment to do so, but I would certainly welcome your help
> in the Postgres side of the house (perhaps we could divide up the functions
> to be written between each of us). Right now, William Heinbockel is refining
> something he's written for MySQL. Javier has expressed to me that he would
> rather the Postgres code wait until what William's current effort is done so
> the two lines can proceed together and not independently.
>
>
> --
> Eric I. Arnoth CISSP (http://www.isc2.org)
> earnoth@comcast.net
> http://mywebpages.comcast.net/earnoth
> ¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø
>
>

I just uploaded an update to the NESSUS_SQL CVS tree to Javi yesterday.
The code now compiles, but does not link. I explained this in detail
in a message to Javi and hopefully it will be fixed soon so we can start
testing.

Also, I am feeling pretty confident in the schema that has developed for
this database project. There are several minor issues left to iron
out, but hopefully we can agree to finalize the schema soon. That way
I can finalize my code.

I suggest that any one interested, check out the schema in the
NESSUS_SQL branch -> nessus-core/doc/database/ (if i remember correctly)
and post your feedback.

Thanks.

----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: wjh3710@rit.edu

Re: How to start exporting Nessus results to a DB [ In reply to ]

earnoth at comcast

Feb 22, 2003, 11:04 AM

Post #9 of 16 (3793 views)

On Saturday 22 February 2003 11:08, William Heinbockel wrote:
> Tony,
> Right now Javi and I are working on abstracting the database code
> from the Nessus main code and getting the configure file to properly
> setup the flags and include the database libraries.
William, I hope you and Javi don't mind my asking, but how are
transactions/ACID complaince being considered in the abstraction? I would
expect that by the very act of abstracting, it would be possible to either
use transactions in the underlying DB calls or to not, but at the same time,
I can also envision abstractions that make transactioning difficult if not
impossible.

> Once that is finished, to add another database, you'll be able to use
> my mysql code as a guideline and change the mysql library calls and
> queuries to whatever database you want. This will ensure that the
> databases are layed out according to the schema and allow someone with
> very little C knowledge to add their own database to the mix.
>
> I am sure something will be posted to the nessus-dev list once
> Javi and I feel that enough progress has been made detailing how
> people can add their own database to Nessus. Until that time,
> you may want to follow our development in this list and in the
> NESSUS_SQL CVS tree.

Re: How to start exporting Nessus results to a DB [ In reply to ]

earnoth at comcast

Feb 22, 2003, 11:07 AM

Post #10 of 16 (3790 views)

ACK! I hit send a bit too early on this, I wasn't quite finished...I'm
currently looking at the functions in save_mysql.h, trying to figure out how
well that accomodates transactions...sorry for the premature send!

On Saturday 22 February 2003 13:04, Eric Arnoth wrote:
> On Saturday 22 February 2003 11:08, William Heinbockel wrote:
> > Tony,
> > Right now Javi and I are working on abstracting the database code
> > from the Nessus main code and getting the configure file to properly
> > setup the flags and include the database libraries.
>
> William, I hope you and Javi don't mind my asking, but how are
> transactions/ACID complaince being considered in the abstraction? I would
> expect that by the very act of abstracting, it would be possible to either
> use transactions in the underlying DB calls or to not, but at the same
> time, I can also envision abstractions that make transactioning difficult
> if not impossible.

>
> > Once that is finished, to add another database, you'll be able to use
> > my mysql code as a guideline and change the mysql library calls and
> > queuries to whatever database you want. This will ensure that the
> > databases are layed out according to the schema and allow someone with
> > very little C knowledge to add their own database to the mix.
> >
> > I am sure something will be posted to the nessus-dev list once
> > Javi and I feel that enough progress has been made detailing how
> > people can add their own database to Nessus. Until that time,
> > you may want to follow our development in this list and in the
> > NESSUS_SQL CVS tree.

--
Eric I. Arnoth CISSP (http://www.isc2.org)
earnoth@comcast.net
http://mywebpages.comcast.net/earnoth
¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø

Re: How to start exporting Nessus results to a DB [ In reply to ]

jfernandez at germinus

Feb 24, 2003, 12:46 AM

Post #11 of 16 (3786 views)

Eric Arnoth wrote:
> ACK! I hit send a bit too early on this, I wasn't quite finished...I'm
> currently looking at the functions in save_mysql.h, trying to figure out how
> well that accomodates transactions...sorry for the premature send!

Oh. Please check save_db.{h,c} best. save_mysql has been superceeded by it.

Javi

Re: How to start exporting Nessus results to a DB [ In reply to ]

jfernandez at germinus

Feb 24, 2003, 1:51 AM

Post #12 of 16 (3787 views)

Javier Fernandez-Sanguino wrote:
> Eric Arnoth wrote:
>
>> ACK! I hit send a bit too early on this, I wasn't quite
>> finished...I'm currently looking at the functions in save_mysql.h,
>> trying to figure out how well that accomodates transactions...sorry
>> for the premature send!
>
>
>
> Oh. Please check save_db.{h,c} best. save_mysql has been superceeded by it.
>
> Javi
>

Re-reading my mail I believe it might not be understood properly. I
meant that the code in save_mysql.c which was previously called from
nessusd.c/attack.c directly is now called through an abstraction layer
that is coded in save_db.c so really:

nessusd.c --\ --- save_mysq.{h,c} (only one atm)
---> save_db.{h,c} ---|
attack.c --/ |-- save_pg.{h,c} (planned)
|
|-- save_oracle.{h,c} (expected :-)
|
|.....

So depending on what you ./configure you will enable/disable either one
of the database backends (you will probably be able to even have more
than one backend).

Regards

Javi

Re: How to start exporting Nessus results to a DB [ In reply to ]

deraison at nessus

Feb 24, 2003, 2:46 AM

Post #13 of 16 (3788 views)

On Mon, Feb 24, 2003 at 09:51:00AM +0100, Javier Fernandez-Sanguino wrote:
> Re-reading my mail I believe it might not be understood properly. I
> meant that the code in save_mysql.c which was previously called from
> nessusd.c/attack.c directly is now called through an abstraction layer
> that is coded in save_db.c so really:
>
> nessusd.c --\ --- save_mysq.{h,c} (only one atm)
> ---> save_db.{h,c} ---|
> attack.c --/ |-- save_pg.{h,c} (planned)

[...]

I will start to have a closer look at the code when I'm done with the
release of Nessus 2.0, but I really don't see any reason why the
database hooks should go in attack.c rather than save_kb.c (which
receives basically everything information-wise).

The reason I'd prefer to see the code in save_kb is that attack.c is
very complex already, and I'm in the process of simplifying the code as
much as I can (1113 lines in 1.2.x, 887 in 2.0.x and hopefully even less
than that in 2.2.x), so adding stuff in it makes the future merge of
NESSUS_SQL much harder (there will be conflicts if we merge by 2.2).

OTOH, the save_kb stuff is a set of hooks which probably won't change
much over time, because it's supposed to be modular enough and clean.

Maybe I'm wrong though, give me some time and I'll check if what I say
is completely bogus or not.

-- Renaud

RE: How to start exporting Nessus results to a DB [ In reply to ]

John.Benninghoff at Rbcdain

Feb 24, 2003, 10:00 AM

Post #14 of 16 (3786 views)

The schema documentation in nessus-core/doc/database/ appears to be in the Attic... at least it is on cvs.nessus.org. ?

-----Original Message-----
From: William Heinbockel [mailto:wjh3710@osfmail.isc.rit.edu]
Sent: Saturday, February 22, 2003 10:15 AM
To: Eric Arnoth
Cc: Tony Carter; Nessus-Dev
Subject: Re: How to start exporting Nessus results to a DB

On Sat, 22 Feb 2003, Eric Arnoth wrote:

> On Friday 21 February 2003 21:52, Tony Carter wrote:
> > Gentlemen,
> > I'm very interested in helping with integrating Nessus results to a
> > database. Is anyone working on the Postgres code? If not, I'd be more than
> > happy to do so.
> >
> > -Tony
>
> Tony, I've made a commitment to do so, but I would certainly welcome your help
> in the Postgres side of the house (perhaps we could divide up the functions
> to be written between each of us). Right now, William Heinbockel is refining
> something he's written for MySQL. Javier has expressed to me that he would
> rather the Postgres code wait until what William's current effort is done so
> the two lines can proceed together and not independently.
>
>
> --
> Eric I. Arnoth CISSP (http://www.isc2.org)
> earnoth@comcast.net
> http://mywebpages.comcast.net/earnoth
> ¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø
>
>

I just uploaded an update to the NESSUS_SQL CVS tree to Javi yesterday.
The code now compiles, but does not link. I explained this in detail
in a message to Javi and hopefully it will be fixed soon so we can start
testing.

Also, I am feeling pretty confident in the schema that has developed for
this database project. There are several minor issues left to iron
out, but hopefully we can agree to finalize the schema soon. That way
I can finalize my code.

I suggest that any one interested, check out the schema in the
NESSUS_SQL branch -> nessus-core/doc/database/ (if i remember correctly)
and post your feedback.

Thanks.

----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: wjh3710@rit.edu

Re: How to start exporting Nessus results to a DB [ In reply to ]

jfernandez at germinus

Feb 24, 2003, 10:03 AM

Post #15 of 16 (3787 views)

Benninghoff, John wrote:
> The schema documentation in nessus-core/doc/database/ appears to be in the Attic... at least it is on cvs.nessus.org. ?
>

Yes, probably because it's in a branch (NESSUS_SQL) and it is not
present (at all) in the HEAD branch. It should appear under doc/database
if you do a 'cvs co -rNESSUS_SQL' IIRC.

Regards

Javi

RE: How to start exporting Nessus results to a DB [ In reply to ]

John.Benninghoff at Rbcdain

Feb 24, 2003, 10:16 AM

Post #16 of 16 (3789 views)

Oh yeah, forgot about that. Thanks.

-----Original Message-----
From: Javier Fernandez-Sanguino [mailto:jfernandez@germinus.com]
Sent: Monday, February 24, 2003 11:04 AM
To: Benninghoff, John
Cc: Nessus-Dev
Subject: Re: How to start exporting Nessus results to a DB

Benninghoff, John wrote:
> The schema documentation in nessus-core/doc/database/ appears to be in the Attic... at least it is on cvs.nessus.org. ?
>

Yes, probably because it's in a branch (NESSUS_SQL) and it is not
present (at all) in the HEAD branch. It should appear under doc/database
if you do a 'cvs co -rNESSUS_SQL' IIRC.

Regards

Javi