Re: QUICK NESSUS 3.2 QUESTION
| Newsgroups | gmane.comp.security.nessus.general |
|---|---|
| Message-ID | <OF24D085F5.ED8EB8F4-ON85257466.005A2809-85257466.005ADBE3@srs.gov> |
Being in a similar situation, I had the same questions. No changes were required to my parsing scripts. The *nix scanners output the results in the new .nessus format (b/c of my application design) and then running a conversion to .nbe for input into a database. Mike "John Scherff" <[email protected]> Sent by: [email protected] 06/12/2008 11:26 AM To <[email protected]> cc Subject QUICK NESSUS 3.2 QUESTION Background: We're finally getting around to migrating from 3.06 to 3.2x. Our scanning system is a fairly complex setup comprised of several perl scripts that parse the .nbe output files and load the results into an Oracle database used by a separate, PHP-based web reporting system. Question: will the new nessus client work with the same command-line switches and will it still produce legacy .nbe output, or must we also migrate to the new .nessus report format? We will eventually re-write our code to use the new format, but prefer to upgrade first and do the re-write later. John Scherff Information Security and Storage Manager 24 Hour Fitness [email protected] The code of competence is the only system of morality that’s on a gold standard. –Ayn Rand _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus