Original script can be found here: https://github.com/eelsivart/nessus-report-downloader Script was extended for usage with command line options and to automaticly download files from a given number of the last days (now-x). This is needed for the usage of the script with cronjobs. Sample usage, download reports in nessus format from the last 30 days:
========================================
Name: Nessus 6 Report Downloader
Author: Travis Lee
Version: 1.0
Last Updated: 2/28/2016
Description: Interactive script that connects to a specified Nessus 6 server using the Nessus REST API to automate mass report downloads. It has the ability to download multiple or all reports/file types/chapters and save them to a folder of your choosing. This has been tested with Nessus 6.5.5 and should work with Nessus 6+, YMMV.
File types include: NESSUS, HTML, PDF, CSV, and DB.
Chapter types include: Vulnerabilities By Plugin, Vulnerabilities By Host, Hosts Summary (Executive), Suggested Remediations, Compliance Check (Executive), and Compliance Check.
Usage: ruby ./nessus6-report-downloader.rb
========================================
Name: Nessus Report Downloader
Author: Travis Lee
Version: 1.01
Last Updated: 3/14/2014
Description:
Interactive script that connects to a specified Nessus server using the
Nessus REST API to automate mass report downloads. It has the ability to download
multiple or all reports/file types/chapters and save them to a folder of
your choosing. This has been tested with Nessus 5.2.5 and should work with
Nessus 5+, YMMV.
File types include: .nessus v2, HTML, PDF, CSV, and NBE.
Chapter types include: Vulnerabilities By Plugin, Vulnerabilities By Host, Hosts Summary (Executive), Suggested Remediations, Compliance Check (Executive), and Compliance Check.
A windows executable is also available that was created with OCRA.
Requires: nokogiri (gem install nokogiri)
Usage: ruby ./nessus-report-downloader.rb
Windows EXE Usage: .\nessus-report-downloader-1.0.exe
Note 3/14/14: According to Tenable support, the "Status" field reported by the API always shows as "completed" even though the status is in another state as shown in the GUI.