Re: XML output - should <data> be

> Hi!
>
> I'm parsing the nessus xml output to generate custom reports based on that.
> Though I'm having a bit of a problem parsing the contents of the "data"
> tag because it contains too many different things with no apparent
> determined structure. (E.g. "Solution" info comes arbitrarily before and
> after the "See also" info.)

It is funny that this comes up today, as I've been having the exact
same problem with all of the Nessus reports, but wasn't sure what could
be done.  How much effort would be required in order to get the reports
to have defined fields for all of the data elements, such as "risk factor",
reference sources, etc.  Honestly, reporting on data as either a security
note or warning isn't very flexible... I always use the risk factor, but 
find it difficult to get to.  

I'd be glad to assist in any way that might be handy.  

-Ds

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus