Project RF
3.6.2013 So Nessus 5 is pretty cool for being able to filter the results to generate reports. I still like my reports though, especially the vulnerability matrix. I also like creating the quick Nmap CSV files as well as loading Kismet into a database to run queries (no reporting yet). I also added an import for Dumpsec and so far have a simple report that tells me password age.
I created Project RF to have a reporting framework that provides consistent reports for various vulnerability scanning tools. The project started with support for Nessus, Eeye Retina, and Nmap expanded with reporting for HP WebInpect, AppScan AppDetective, Kismet, and GFI Languard. This project is still in its alpha stages as I’m not a top notch web program developer. Scan results are exported to XML which is then uploaded, parsed, and imported into a backend MySQL database. I have found this framework very useful in generating reports for my workpapers.
I have created an updated and stripped down version of the framework for the latest Nessus XML. All the work was done redoing the Nessus support for the updated XML with additional reporting features. I’ve created this document (http://www.jedge.com/docs/install%20Project%20RF.pdf) to assist in setting up the framework. As time permits I will include import options for XML reports generated from WebInspect, AppDetective, Nmap, & Kismet. The current parse code I have does not support the latest XML for those tools.
The code can be found here (http://www.jedge.com/docs/projectRF.tar.gz).
Change Log
3.6.2013 – I still work on this shit. Especially since I’m a full time pen tester again and create scripts for reporting.
7.12.2011 – Redid the Nessus compliance parser so it actually works. It was tested on an audit file created by the i2a tool. The report created is still crude but you can dump the info to CSV for analysis.
7.4.2011 – When the Nessus reports are parsed I calculate the scan start and end time and include that in the nessus_results table. Why the Nessus XML files does not have this I don’t know. This is now used to make each scan unique and I hope to include reporting that shows progress on patching vulnerabilities. We shall see.




[...] and workpapers. Just remember to keep the original Nmap results. I’ve developed a LAMP framework to parse and load Nmap results into a database for reporting and analysis. However if you are just [...]
The idea looks cool, would definitely like to try it out for some time and maybe if possible help in development although i am already handful with task’s.
If possible do share the code with me.
I hope my presentation would help you in understanding the dot nessus v2 format.
Also do check tennable official documentation its now updated for v2.
Anant,
Here is the link (http://www.jedge.com/docs/projectRF.zip) to the code. A PDF on how to get the LAMP framework up and running is included in the ZIP file.
Are you still supporting this project? Several attempts to email you at projectRF email address have failed. If so, could you reach out to me at the email address provided?
Thanks!
Ryan
Ryan,
Still coding for the framework. I thought I had created the email account proj...@jedge.com but apparently I did not. Thanks for pointing that out. It has been corrected.
Is this project still active? I have a specific nmap script and results needing to be parsed, output to csv, and input to a mysql database. Wondering if anyone is interested in doing some freelancing.
The short answer is yes it is still “active”. I haven’t had time to see how the new Nessus 5 makes this relevant or how the XML file has changed. Parsing Nmap to create a CSV or import into MySQL is not a problem at all.
Hi,
thank for jour job, projectRF is really userful.
Unfortunately I need to delete some report (and why not merge different ones).
.
Maybe these features will be avaiable in the next releases
In the meanwhile can I have the mysql query to delete all data related to one report uploaded?
Thanks in advance,
Andrea