We performed a comparison between AWS Security Hub and Microsoft Defender for Cloud 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 offers regulatory compliance, ransomware protection, access controls, real-time assessment, incident alerts, and UEBA features. AWS Security Hub is highly valued for its integration capabilities, real-time alert capabilities, and comprehensive alerts about potential compliance issues with CIS standards. Microsoft Defender for Cloud needs work in consistency, customization, integration, collaboration, and protection. Meanwhile, AWS Security Hub requires more integration options, a better user interface, self-sufficiency, multi-cloud compatibility, and faster updates and integration.
Service and Support: Some users have had positive experiences with Microsoft Defender for Cloud's customer service, while others have encountered issues with outsourced support, slow response times, and difficulty reaching the appropriate level of support. On the other hand, AWS Security Hub's technical support has been characterized as prompt and satisfactory by clients.
Ease of Deployment: Microsoft Defender for Cloud and AWS Security Hub have fairly easy and straightforward initial setup processes. Microsoft Defender for Cloud may require some prior knowledge, but it generally takes less than 24 hours to deploy. Maintenance for both solutions is minimal, with AWS Security Hub requiring little to no maintenance after deployment. However, policies still need to be configured for AWS Security Hub during setup.
Pricing: M Microsoft Defender for Cloud's pricing depends on the license and metrics used, while AWS Security Hub's pricing is considered reasonable. Reviewers generally find Microsoft Defender for Cloud's pricing to be fair and cost-effective, but note that it may not be suitable for small businesses due to cost. AWS Security Hub's pricing is viewed as satisfactory, although there is some ambiguity for those not part of the central team.
ROI: Microsoft Defender for Cloud is user-friendly and cost-effective, while AWS Security Hub has been beneficial for users.
Comparison Results: According to user feedback, Microsoft Defender for Cloud is the preferred option when compared to AWS Security Hub. It offers more comprehensive features, such as regulatory compliance, ransomware protection, access controls, and UEBA features that are important for cloud environments. Although AWS Security Hub is commended for its integration capabilities, users suggest it could benefit from more integration options with open-source cloud security solutions and improvements to the user interface.
"It's a security posture management tool from AWS. Basically, it identifies misconfigurations, similar to Trusted Advisor but on a larger scale."
"The most valuable features of the solution are the scanning of all the cloud environments and most of the compliances available in the cloud."
"I find all of the features to be highly valuable."
"AWS Security Hub provides comprehensive alerts about potential compliance issues with CIS standards. The integration with third-party tools is another excellent feature. All our workloads are on AWS."
"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 like that AWS Security Hub currently has several good features, around four or five. The technical support for AWS Security Hub is also responsive."
"Most importantly, it's an integrated solution. We not only have Defender for Cloud, but we also have Defender for Endpoint, Defender for Office 365, and Defender for Identity. It's an integrated, holistic solution."
"The product has given us more insight into potential avenues for attack paths."
"The entire Defender Suite is tightly coupled, integrated, and collaborative."
"The security policy is the most valuable feature for us. We can go into the environment settings and attach any globally recognized framework like ISO or any benchmark."
"When you have commissioned Defender, you have these things visible already on your dashboard. This gives the efficiency to the people to do their actual work rather than bothering about the email, sorting out the email, or looking at it through an ITSM solution, whey they have to look at the description and use cases. Efficiency increases with this optimized, ready-made solution since you don't need to invest in something externally. You can start using the dashboard and auditing capability provided from day one. Thus, you have fewer costs with a more optimized, easier-to-use solution, providing operational efficiency for your team."
"Using Security Center, you have a full view, at any given time, of what's deployed, and that is something that is very useful."
"Everything is built into Azure, and if we go for cross-cloud development with Azure Arc, we can use most of the features. While it's possible to deploy and convert third-party applications, it is difficult to maintain, whereas Azure deployments to the cloud are always easier. Also, Microsoft is a big company, so they always provide enough support, and we trust the Microsoft brand."
"The most valuable feature is that it's intuitive. It's very intuitive."
"The solution will only give you insight if you have configure rule enabled. It should work more like Prisma Cloud and Dome9 which have a better approach."
"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."
"It is not flexible for multi-cloud environments."
"One aspect that could be improved in the solution is its adaptability to different markets and geopolitical restrictions. In certain regions like Thailand, specific services from certain countries or providers, such as AWS or Azure, might be limited or blocked. It also needs improvement in would require configuring the solution more adaptable to AWS infrastructure and function."
"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."
"Adding SIEM features would be beneficial because of the limited customization of AWS Security Hub."
"The telemetry doesn't always go into the control center. When you have multiple instances running in AWS, you need a control tower to take feeds from Security Hub and analyze your results. Sometimes exemptions aren't passed between the control tower and Security Hub. The configuration gets mixed up or you don't get the desired results."
"From an improvement perspective, there is a need to add more compliance since, right now, AWS Security Hub only provides four to five compliances to control the tool."
"There is no perfect product in the world and there are always features that can be added."
"It needs to be simplified and made more user-friendly for a non-technical person."
"If a customer is already using Okta as an SSO in its entire environment, they will want to continue with it. But Security Center doesn't understand that and keeps making recommendations. It would help if it let us resolve a recommendation, even if it is not implemented."
"I felt that there was disconnection in terms of understanding the UI. The communication for moving from the old UI to the new UI could be improved. It was a bit awkward."
"You cannot create custom use cases."
"Azure is a complex solution. You have so many moving parts."
"Microsoft can improve the pricing by offering a plan that is more cost-effective for small and medium organizations."
"Azure's system could be more on point like AWS support. For example, if I have an issue with AWS, I create a support ticket, then I get a call or a message. With Azure support, you raise a ticket, and somebody calls back depending on their availability and the priority, which might not align with your business priority."
AWS Security Hub is ranked 13th in Cloud Security Posture Management (CSPM) with 17 reviews while Microsoft Defender for Cloud is ranked 3rd in Cloud Security Posture Management (CSPM) with 46 reviews. AWS Security Hub is rated 7.6, while Microsoft Defender for Cloud is rated 8.0. 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 Microsoft Defender for Cloud writes "Provides multi-cloud capability, is plug-and-play, and improves our security posture". AWS Security Hub is most compared with Microsoft Sentinel, Prisma Cloud by Palo Alto Networks, Wiz, Google Chronicle Suite and Oracle Security Monitoring and Analytics Cloud Service, whereas Microsoft Defender for Cloud is most compared with AWS GuardDuty, Prisma Cloud by Palo Alto Networks, Microsoft Defender XDR, Wiz and Wazuh. See our AWS Security Hub vs. Microsoft Defender for Cloud 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.