We performed a comparison between AWS Security Hub and Tenable.sc based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: Tenable.sc provides precise identification of vulnerabilities, compliance and vulnerability scans, and a risk-oriented methodology. On the other hand, AWS Security Hub receives commendation for its integration capabilities, immediate alerts, and thorough notifications regarding potential compliance concerns. Tenable.sc and AWS Security Hub both have areas where they could improve. Tenable.sc needs to work on their penetration testing, pricing, ticketing, GUI, reporting, vendor training, and accuracy of vulnerability assessments. AWS Security Hub requires more integration options, better UI, multi-cloud compatibility, faster updates, and easier configuration.
Service and Support: Tenable.sc's customer service has received mixed feedback, with varying levels of helpfulness. In comparison, AWS Security Hub's support is praised for being prompt and good.
Ease of Deployment: Tenable.sc's initial setup is praised for being simple and quick, with the cloud version taking only one day and the on-prem version taking two to three weeks. Meanwhile, AWS Security Hub's setup is also considered easy, though it does involve policy configuration and some upkeep.
Pricing: Tenable.sc charges based on the number of IP addresses and has mixed opinions on pricing, while AWS Security Hub has reasonable pricing.
ROI: Tenable.sc is cost-effective and offers a guaranteed ROI with a significant reduction in manpower costs. In contrast, AWS Security Hub does not provide the same level of value, despite offering a positive outcome.
Comparison Results: Tenable.sc is seen as the superior choice when compared to AWS Security Hub by users. This is due to its extensive features, including accurate vulnerability detection, compliance and vulnerability scans, and a risk-based approach. Tenable.sc also provides advanced scanning, asset discovery, and scoring, which are not found in AWS Security Hub. Although AWS Security Hub is praised for its integration capabilities and real-time alerts, Tenable.sc's analysis, prioritization, and usability features make it a more valuable tool for vulnerability analysis and remediation progress tracking.
"The vulnerability management modules and the discovery and inventory are the most valuable features. Before using Wiz, it was a very manual process for both. After implementing it, we're able to get all of the analytics into a single platform that gives us visibility across all the systems in our cloud. We're able to correspond and understand what the vulnerability landscape looks like a lot faster."
"Our most important features are those around entitlement, external exposure, vulnerabilities, and container security."
"The security baseline and vulnerability assessments is the valuable feature."
"The first thing that stood out was the ease of installation and the quick value we got out of the solution."
"Out of all the features, the one item that has been most valuable is the fact that Wiz puts into context all the pieces that create an issue, and applies a particular risk evaluation that helps us prioritize when we need to address a misconfiguration, vulnerability, or any issue that would put our environment into risk."
"The CSPM module has been the most effective. It was easy to deploy and covered all our accounts through APIs, requiring no agents. Wiz provides instant visibility into high-level risks that we need to address."
"With Wiz, we get timely alerts for leaked data or any vulnerabilities already existing in our environment."
"The product supports out-of-the-box reporting with context about the asset and allows us to perform complex custom queries on UI."
"Easily integrates with third-party tools"
"Finding out if your infrastructure is secure is a valuable feature."
"The most valuable features of the solution are the scanning of all the cloud environments and most of the compliances available in the cloud."
"It's a security posture management tool from AWS. Basically, it identifies misconfigurations, similar to Trusted Advisor but on a larger scale."
"Cloudposse is a valuable feature as it guarantees my security."
"I really like the seamless integration with the AWS account structure. It can even be made mandatory as part of the landing zone. These are great features. And there's a single pane of glass for the entire account."
"AWS Security Hub has very good integration features. It allows for AWS native services integration, and it helps us to integrate some of the services outside of AWS. They have partners, such as Amazon Preferred Network Partners (APN). If you have different security tools around APN, we can integrate those findings with AWS Security Hub reducing the need to refer to different portals or different UIs. You can have AWS Security Hub act as a single common go-to dashboard."
"Very good at detection and providing real-time alerts."
"I found the dashboard features very useful. It made it easy to track remediation progress. I could publish dashboards to remediation teams and track the progress on the dashboards."
"Tenable.sc is user-friendly."
"Initial setup was pretty straightforward."
"The most important features are the dashboard and reporting. The dashboard provides statistics with graphs and bar charts for our management."
"The most valuable feature of the product is the Assurance Report Card, which gives us an overview of the security poster in just a simple glance."
"The tool provides us insight into the happens of the network and its hosts. It provides me with a list of hosts."
"It is a very good and user-friendly product."
"It basically reviews our threat landscape vulnerability."
"We're looking at some of the data compliance stuff that they've got Jon offer. I know they're looking at container security, which we gonna be looking at next."
"We would like to see improvements to executive-level reporting and data reporting in general, which we understand is being rolled out to the platform."
"We wish there were a way, beyond providing visibility and automated remediation, to wait on a given remediation, due to a critical aspect, such as the cost associated with a particular upgrade... We would like to see preventive controls that can be applied through Wiz to protect against vulnerabilities that we're not going to be able to remediate immediately."
"The solution's container security could be improved."
"The reporting isn't that great. They have executive summaries, but it's only a compliance report that maps all current issues to specific controls. Whether you look at one subscription or project, regardless of the size, you will get a multipage report on how the issues in that account map to that control. Our CSO isn't going to read through that. He won't filter that out or show that to his leadership and say, "Here's what we're doing." It isn't a helpful report. They're working on it, but it's a poor executive summary."
"The only small pain point has been around some of the logging integrations. Some of the complexities of the script integrations aren't supported with some of the more automated infrastructure components. So, it's not as universal. For example, they have great support for cloud formation and other services, but if you're using another type of management utility or governance language for your infrastructure-as-code automation components, it becomes a little bit trickier to navigate that."
"The remediation workflow within the Wiz could be improved."
"Given the level of visibility into all the cloud environments Wiz provides, it would be nice if they could integrate some kind of mechanism to better manage tenants on multiple platforms. For example, let's say that some servers don't have an application they need, such as an antivirus. Wiz could include an API or something to push those applications out to the servers. It would be great if you could remedy these issues directly from the Wiz platform."
"Security needs to be measured based on their own criteria. We can't add custom criteria specific to our organization. For example, having an S3 bucket publicly available might be flagged as a critical alert, but it might not be critical in a sandbox environment. So, it gets flagged as critical, which becomes a false positive. So, customization options and creating custom dashboards would be areas for improvement."
"It's not user-friendly. Too much going on, too many unnecessary findings, not very visual. You can't do much compared to other similar tools that are cheaper and better."
"Adding SIEM features would be beneficial because of the limited customization of AWS Security Hub."
"The solution lacks self-sufficiency."
"Whenever my team gets some alarms from the central team, my team needs to initiate whether it's a real or false trigger. The central team needs to keep adjusting to the parameters or at least the concerned IPs, whether it's really from the company's pool of IPs, so the trigger process can be improved. In the next release of AWS Security Hub, I'd like a better dashboard that could result in better alert visibility."
"We need more granular-level customizations to enable or disable the rules in AWS Security Hub."
"The user interface, graphs, and dashboards of the solution could improve in the future. They are not very sophisticated and could use an update."
"AWS Security Hub should improve the time it takes to update. It takes a long period of time when updating. It can take 24 hours sometimes to update. Additionally, when integrating this solution with more security tools, takes time."
"The vulnerability scan does not work correctly until the access privileges are set by the system administrator."
"Tenable SC can improve by adding more integrations with HCI-type tools and more accurate vulnerability detection."
"Support could be faster."
"The biggest issue I have with the solution is when I'm using the scanning it picks up the original DNS of that device. That means, before we image it and actually change the DNS to something within our company structure, it'll just be random numbers and letters and Tenable will stick to that DNS for a long time."
"It's good at creating information, it's good creating dashboards, it's good at creating reports, but if you want to take that reporting metadata and put it into another tool, that is a little bit lacking."
"Tenable SC can improve by making it easier to create complicated reports and have more effectiveness in the remediation area for comparison between the scans."
"The reporting needs a lot of work on the template."
"For downloading reports, we have to go to the scan and then we have to go to the reports and download the Excel or CSV or PDF. I think these menus and clicks can be minimized."
AWS Security Hub is ranked 13th in Cloud Security Posture Management (CSPM) with 17 reviews while Tenable Security Center is ranked 10th in Cloud Security Posture Management (CSPM) with 48 reviews. AWS Security Hub is rated 7.6, while Tenable Security Center is rated 8.2. The top reviewer of AWS Security Hub writes "A centralized dashboard that enables efficient monitoring and management of possible security issues". On the other hand, the top reviewer of Tenable Security Center writes "A security solution for vulnerability assessment with automated scans". AWS Security Hub is most compared with Microsoft Sentinel, Prisma Cloud by Palo Alto Networks, Microsoft Defender for Cloud, Google Chronicle Suite and Wazuh, whereas Tenable Security Center is most compared with Tenable Vulnerability Management, Qualys VMDR, Tenable Nessus, Rapid7 InsightVM and Prisma Cloud by Palo Alto Networks. See our AWS Security Hub vs. Tenable Security Center report.
See our list of best Cloud Security Posture Management (CSPM) vendors.
We monitor all Cloud Security Posture Management (CSPM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.