Updating nessus plugins
One of its main advantages is its extensive and continually evolving plugin database of vulnerability checks.Nessus comes with a shell script to retrieve the latest set of plugins from a central repository -- -- and I would imagine most Nessus users run this fairly often to keep their plugins up-to-date.Microsoft's MSXML 4.0 SP2 has been out of support since 2010 but is still widely installed (some estimates are around 39.5 of home PCs in the USA).Yet it hasn't mirrored the perpetual exploits that are expected to occur when patches are no longer released for XP.If you have always-on connection to the Internet, automatic Nessus database update is the preferred method. For the manual method, here is the command to update your Nessus plugins : After several time, depending on your Internet connection speed, the update process is done.Next, you might want to check your Nessus Plugin Feed version, to make sure that you have update it correctly.While the script does at fine job, it does have a couple of limitations in my opinion: it does not backup existing plugins, it doesn't attempt to validate new or changed plugins, and it doesn't provide much information about changes.
All other products or services are trademarks of their respective owners.It is written in NASL (Nessus Attack Scripting Language).There are currently 25638 different plugins used by Nessus, covering local and remote flaws.It should work on any unix-like system with Perl 5 or better (Perl 5.005 if you choose to generate summary reports). This script is free software; you can redistribute it and/or modify it under the same terms as Perl itself.It also requires the following Perl modules: to your commandline) and examine the resulting output before contacting me.