If you were talking to someone whose organization is considering Tenable.io Vulnerability Management, what would you say?
How would you rate it and why? Any other tips or advice?
We're a partner for Tenable Nessus. The Tenable.io is what we're using currently. It suits our needs best due to the fact that it's in the cloud. The API is okay. It's not wonderful. Seems to serve a purpose. The biggest problem with the solution is that if you're a small company, you're not going to be able to afford it, nor are you going to be able to manage it. I would recommend other organizations use the product. People probably don't consider the amount of, let's say, understanding or comprehension that they need of their own network to truly be able to deploy and manage and get the results they're looking for, however. Many often underestimate all their skillsets. Tenable has a number of features and functionalities and it can be a little confusing for, let's say, a non-security savvy person. It could be a little bit of a challenge, to be honest. I'd suggest any company that considers it also does their homework first. I'd rate the solution at a seven out of ten. It gets the job done. It really is smooth to operate once it's set up. It is for the most part pretty easy to set and forget.
We are a reseller. We work with a lot of different Tenable.io products. My only recommendation to other companies would be to put up a plan and follow the plan, point by point. Keep tracking of the result and make adjustments, if necessary. It's important to go in with a bit of a roadmap to follow. It will help ensure results. In general, I would rate the solution at an eight out of ten. We've been pretty happy with the solution overall.
My advice for anybody who is implementing this product is to have all of the requirements documented and ready in advance. You match the solution to your requirements. Out of the box, we found that Tenable.io matched almost all of our requirements. The only clarification that we needed had to do with the Tenable.io Web App license. We have a good understanding of how Tenable.io works with containers and infrastructure, but when it comes to deep driving into applications, databases, APIs, and toolkits that you have in your environment, you need a separate license for that. This is what the Web Application license is. In order to enjoy the maximum value, you need to have the appropriate licensing. Overall, I am quite happy with Tenable.io. I would rate this solution a nine out of ten.
We use the cloud deployment model. I'd recommend the solution. I'd rate it eight out of ten.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.
Let the community know what you think. Share your opinions now!