Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Report Fields Wishlist Items

Subject: Report Fields Wishlist Items
Date: Wed, 26 Sep 2007 10:37:19 -0500
I was looking to create an abridged report using Nessus 3 for Windows.  I 
originally thought that I could make an XSL file to put in the report_styles 
directory, but in the raw xml files in the Vista 
\Users\username\Tenable\Nessus\Reports\*.xml the only fields I see are:
- target (name)
- start_time (time)
- finish_time (time)
- hostname (ip)
- portname (port)
- id (plugin id)
- level (severity)
- desc (up to 20 lines description)

So, a few wishlist items:

1.  Include the NASL fields, for instance script_summary, script_name, and 
script_family in the XML.  This would make an abridged report much easier.  
Yes, I could just group everything by "id" currently, but the report wouldn't 
make sense as I would have no idea what the "id"-numbered plugin does.  It 
would also make it much easier to disable a plugin within Nessus based on the 
report output.

2. Include the plugin file name in the XML.  This would make it easy to figure 
out which plugin to modify while debugging a report.

3. Change NASL to break down the script_description into its typical sections 
(Synopsis, Description, Risk Factor, Fix, Plugin output, etc).  This would make 
it possible to remove a lot of unnecessary white space in a report using XSL, 
and make it possible in a report to list the generic info once separate from 
the per-host specific output, removing a lot of unnecessary repetition.

Thank you,
Chris Covington
--
Chris Covington, ccovington@logis.org<mailto:ccovington@logis.org>

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>