We performed a comparison between Microsoft Defender for Cloud 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: Microsoft Defender for Cloud focuses on regulatory compliance, ransomware protection, and access controls, while also providing real-time assessment, incident alerts, and UEBA features. On the other hand, Tenable.sc's strengths lie in accuracy in vulnerability detection, prioritization, automation, and risk-based approach. In terms of room for improvement, some users have cited issues with Microsoft Defender for Cloud's reporting capabilities and ease of use. On the other hand, Tenable.sc users have mentioned a need for more user-friendly interfaces and better integration with other security tools.
Service and Support: Some Microsoft Defender users faced challenges with slow response times and difficulty reaching the appropriate support level. Tenable.sc's support is generally positive, with some users finding it prompt and helpful, but others reporting delays and a lack of helpful information.
Ease of Deployment: The setup process for both Microsoft Defender for Cloud and Tenable.sc is reportedly easy, with Microsoft's requiring less maintenance. However, the on-prem version of Tenable.sc can take longer to deploy and needs integration with other solutions.
Pricing: The cost of Microsoft Defender for Cloud depends on the license and metrics, but is often seen as reasonable. Tenable.sc's pricing is based on the number of addresses to be scanned and can include extra costs for advanced support, leading to mixed opinions on its affordability.
ROI: Microsoft Defender for Cloud and Tenable.sc are two different tools that offer unique benefits. Microsoft Defender for Cloud has improved security measures and saved time, while Tenable.sc is useful for reducing the workload and has impressive reporting features.
Comparison Results: Microsoft Defender for Cloud is the preferred option over Tenable.sc due to its comprehensive cloud environment features, including regulatory compliance, ransomware protection, and access controls. Tenable.sc has accurate vulnerability detection and a user-friendly interface, but it lacks some critical cloud environment features and has mixed reviews on customer support and pricing.
"Our most important features are those around entitlement, external exposure, vulnerabilities, and container security."
"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."
"The security baseline and vulnerability assessments is the valuable feature."
"I like Wiz's reporting, and it's easy to do queries. For example, it's pretty simple to find out how many servers we have and the applications installed on each. I like Wiz's security graph because you can use it to see the whole organization even if you have multiple accounts."
"With Wiz, we get timely alerts for leaked data or any vulnerabilities already existing in our environment."
"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."
"The automation roles are essential because we ultimately want to do less work and automate more. The dashboards are easy to read and visually pleasing. You can understand things quickly, which makes it easy for our other teams. The network and infrastructure teams don't know as much about security as we do, so it helps to have a tool that's accessible and nice to look at."
"The solution is very user-friendly."
"Defender for Cloud is a plug-and-play solution that provides continuous posture management once enabled."
"It's got a lot of great features."
"The security alerts and correlated alerts are most valuable. It correlates the logs and gives us correlated alerts, which can be fed into any security information and event management (SIEM) tool. It is an analyzed correlation tool for monitoring security. It gives us alerts when there is any kind of unauthorized access, or when there is any malfunctioning in multifactor authentication (MFA). If our Azure is connected with Azure Security Center, we get to know what types of authentication are happening in our infra."
"One important security feature is the incident alerts. Now, with all these cyberattacks, there are a lot of incident alerts that get triggered. It is very difficult to keep monitoring everything automatically, instead our organization is utilizing the automated use case that we get from Microsoft. That has helped bring down the manual work for a lot of things."
"The product has given us more insight into potential avenues for attack paths."
"The technical support is very good."
"The most valuable features of the solution are the insights, meaning the remediation suggestions, as well as the incident alerts."
"The solution's robust security posture is the most valuable feature."
"Tenable.sc is user-friendly."
"The solution is one of the most, if not the most, stable product available."
"The most important features are the dashboard and reporting. The dashboard provides statistics with graphs and bar charts for our management."
"The solution is very intuitive and the dashboards are simple to use."
"The solution has a lean and easy-to-use interface that is not confusing to first-time users."
"Tenable.sc's best features are the availability model, accident management, and scoring."
"This solution has a much lower rate of false positives compared to competing products."
"Compared to other products, the most valuable features of the solution are its ease of use and ability to provide visibility over scan results while providing many templates to users, making it a helpful tool."
"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 only thing that needs to be improved is the number of scans per day."
"One significant issue is that the searches are case-sensitive, so finding a misconfigured resource can become very challenging."
"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 remediation workflow within the Wiz could be improved."
"After getting a recommendation, it takes time for the solution to refresh properly to show that the problem has been eliminated."
"The overview provides you with good information, but if you want more details, there is a lot more customization to do, which requires knowledge of the other supporting solutions."
"The documentation and implementation guides could be improved."
"The solution could improve by being more intuitive and easier to use requiring less technical knowledge."
"As an analyst, there is no way to configure or create a playbook to automate the process of flagging suspicious domains."
"The initial setup is not actually so complex but it feels complex because there are many add-ons. There are many options and my team needs to be aware of all of these changes happening on the backend which is a distraction."
"The most significant areas for improvement are in the security of our identity and endpoints and the posture of the cloud environment. Better protection for our cloud users and cloud apps is always welcome."
"For Kubernetes, I was using Azure Kubernetes Service (AKS). To see that whatever is getting deployed into AKS goes through the correct checks and balances in terms of affinities and other similar aspects and follows all the policies, we had to use a product called Stackrox. At a granular level, the built-in policies were good for Kubernetes, but to protect our containers from a coding point of view, we had to use a few other products. For example, from a programming point of view, we were using Checkmarx for static code analysis. For CIS compliance, there are no CIS benchmarks for AKS. So, we had to use other plugins to see that the CIS benchmarks are compliant. There are CIS benchmarks for Kubernetes on AWS and GCP, but there are no CIS benchmarks for AKS. So, Azure Security Center fell short from the regulatory compliance point of view, and we had to use one more product. We ended up with two different dashboards. We had Azure Security Center, and we had Stackrox that had its own dashboard. The operations team and the security team had to look at two dashboards, and they couldn't get an integrated piece. That's a drawback of Azure Security Center. Azure Security Center should provide APIs so that we can integrate its dashboard within other enterprise dashboards, such as the PowerBI dashboard. We couldn't get through these aspects, and we ended up giving Reader security permission to too many people, which was okay to some extent, but when we had to administer the users for the Stackrox portal and Azure Security Center, it became painful."
"The solution is expensive."
"The solution should provide better web application features and support."
"The vulnerability scan does not work correctly until the access privileges are set by the system administrator."
"The solution needs to improve the vulnerability assessment because we have experienced some challenges with accuracy."
"The web application scanning area can be improved."
"The GUI could be improved to have all concerns and priorities use the same GUI, allowing them to see all tickets, assign vulnerabilities, and assign variation failures to each member of their team."
"Tenable's reporting engine needs improvement. It needs to be more efficient and add more features."
"Support could be faster."
Microsoft Defender for Cloud is ranked 7th in Vulnerability Management with 46 reviews while Tenable Security Center is ranked 1st in Vulnerability Management with 48 reviews. Microsoft Defender for Cloud is rated 8.0, while Tenable Security Center is rated 8.2. The top reviewer of Microsoft Defender for Cloud writes "Provides multi-cloud capability, is plug-and-play, and improves our security posture". On the other hand, the top reviewer of Tenable Security Center writes "A security solution for vulnerability assessment with automated scans". Microsoft Defender for Cloud is most compared with AWS GuardDuty, Prisma Cloud by Palo Alto Networks, Microsoft Defender XDR, Microsoft Defender for Endpoint and Microsoft Sentinel, whereas Tenable Security Center is most compared with Tenable Vulnerability Management, Qualys VMDR, Tenable Nessus, Rapid7 InsightVM and Cisco Vulnerability Management (formerly Kenna.VM). See our Microsoft Defender for Cloud vs. Tenable Security Center report.
See our list of best Vulnerability Management vendors and best Cloud Security Posture Management (CSPM) vendors.
We monitor all Vulnerability Management 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.