I have a home-grown solution for managing constant network scanning that is being rewritten for clarity and stability. It is actually getting close to complete (the first code review is pending). If my employer allows (which is distinctly possible) I'd be happy to make the code available.
The whole scheme relies substantially on certain aspects of our infrastructure, but the database part is fairly independent (we use Oracle, but my background is MySQL so there are only the necessary Oracle-isms such as using sequences). The component that records to the database also does the scanning, parses the nbe result file of a scan of one or more systems and inserts the results into the database. It is a bit bulky for just parsing an nbe file and stuffing the results in a database, but would be easy to trim for that purpose. As the application has been running in house for over a year there have been numerous growing pain fixes. The current scheme to avoid overloading the nessus server with scans is definitely an improvement over my previous efforts. Again, work allowing, I do plan to make it available. I don't have the time to make it independent of our infrastructure, but those dependencies should be relatively easy to either remove or build a replacement function for. It is entirely done in perl with some use of CSS in the web presentation. While the reporting isn't management-purty it is flexible (so far I've been able to generate requested reports without coding new ones) and fits my needs. It primarily focuses on filtering to a host or list of hosts and then providing a host state with filtering of vulnerabilities. There are some other reports that tie in, such as filtering of plugins with report of number of systems affected and link to previously mentioned filtered list to get by-host status. Also scan queue management and a generic status report page. Tim Doty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicole Tutt Sent: Friday, January 04, 2008 8:41 PM To: '[email protected]' Subject: Nessus output to SQL What are the current options for exporting nessus reports (nbe) to SQL or mySQL databases? Is there currently a good openSource solution (other than writing my own export with perl) or is this capability only available in packages commercially - ie Tenable? From my google searches I don't see anyone talking about it very recently. I get hits regarding nessus_sql but they seem pretty old. The old NessusWx exports to mySQL but is limited in scope. Seems to me that a SQL backend would be incredibly useful but perhaps I a missing something. Thanks in advance, Nicole
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
