2018-08-29 19:26:00 UTC

What needs improvement with Tenable Nessus?


Please share with the community what you think needs improvement with Tenable Nessus.

What are its weaknesses? What would you like to see changed in a future version?

Guest
1111 Answers

author avatar
Top 10Real User

One area that has room for improvement is the reporting. I'm preparing reports for Windows and Linux machines, etc. Currently, I'm collecting three or four reports and turning them into one report. I don't know if it is possible to combine all of them in one report, but that would be helpful. If the scans which I have already prepared could be used to combine the results into one report, it would save me additional work. Also, when a new machine is brought into the domain, when it's first connected by the system administrator, it would be good to have some kind of automatic, basic vulnerability scan. Of course, I would have to enter my credentials if I wanted something additional, but it would be useful if, the first time, if that basic process happened. Otherwise, it can be problematic for me when, for example, a new Oracle Database is brought on. I may only be notified after 10 days that it has been connected and only then can I do a vulnerability assessment and I may find a lot of vulnerabilities. It would be better to know that before they put it into production. It would be great to have something automatically recognize a new server, a new PC, and do a basic vulnerability assessment.

2019-11-27 05:42:00 UTC
author avatar
Top 20Real User

We use credentialed scans. They need more permissions and more changes or settings on Windows and Linux. Also, Agent scanning is more efficient than credential scanning but Agent scanning is more expensive than credential scanning. I prefer, mainly, the Agent scan over the credential scan, it's better. But we will continue to use the credential scan. I would like to see Tenable make some improvements to the credential scanning; more vulnerabilities, because most of the problems have occurred on Windows Server. We have some scanning issues.

2019-11-18 07:22:00 UTC
author avatar
Top 10Consultant

One area with room for improvement is instead of there just being a PDF format for output, I'd like the option of an Excel spreadsheet, whereby I could better track remediation efforts and provide reporting off of that. Or, if they change the product itself for you to add comments of remediation efforts and allow you to sort on that and report on it, that would be helpful. Most of us would rather not have that information out in the cloud. We'd rather have it in-house. It would be better if you could provide it in an Excel spreadsheet for us to work with.

2019-11-14 06:34:00 UTC
author avatar
Real User

There is room for improvement in finishing the transition to the cloud. We'd like to see them keep on improving the Tenable.io product, so that we can migrate to it entirely, instead of having to keep the Tenable.sc on-prem product. There is also room for improvement in some of the reporting and the role-based access. They have a pretty defined roadmap. They know where the gaps are, but it's a totally different product and so there's a lot of work that they have to do to get it to match.

2019-11-13 05:29:00 UTC
author avatar
Top 20Real User

The Nessus predictive prioritization feature is very nice, the way it displays. The interface could look better, but it has everything it needs. It could do a better grouping of the workstations and run a better schedule. But it was sufficient in what it provided. There is room, overall, for improvement in the way it groups the workstations and the way it detects, when the vulnerability is scanned. Even when we would run a new scan, if it was an already existing vulnerability, it wouldn't put a new date on it.

2019-11-07 10:35:00 UTC
author avatar
Top 20Real User

I would like to see an improvement in the ranking of high, medium and low vulnerability.

2019-09-08 09:50:00 UTC
author avatar
Top 20Real User

* I think that the next versions could improve the graphical interface to make more intuitive the management of the reports. * Additionally, it could include better features in the vulnerability scan at the language level.

2019-01-16 20:28:00 UTC
author avatar
Real User

The reporting functionality needs improvement. I think it would be beneficial to have a high level explanation for a particular user.

2019-01-10 08:22:00 UTC
author avatar
Consultant

This is still a maturing product. Tenable is only a scanner for one ability, while other solutions like Rapid7 have more tools for verification. We still have to manually verify to see if the vulnerability is a false positive or not.

2018-10-28 09:34:00 UTC
author avatar
Consultant

From my point of view, the solution basically is not for large enterprises. I also think there should be built-in plugins for the public cloud vendors.

2018-10-24 14:07:00 UTC
author avatar
User

* They should improve the I/O reporting and the customized spreadsheet export feature. * Multiple steps to create an actionable plan will be a great addition to Nessus.

2018-08-29 19:26:00 UTC
Learn what your peers think about Tenable Nessus. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
425,509 professionals have used our research since 2012.