Microsoft Defender for Cloud vs. WithSecure Elements Vulnerability Management

I think it's good for cloud-native companies. A company that, from day zero, they're like, "We're going cloud, and this is how we're going to do it." They get it. It works well for them. Smaller organizations that are under X amount of resources- I don't know what that X might mean- but I feel like it plays well in smaller, more nimble organizations. If you're an older organization or if you're extremely large, it starts becoming a little difficult to manage at scale. And you have to sometimes throw bodies at the problem. Maybe not the most eloquent way of saying it, but that's what it feels like.

Incentivized

• It's really well laid out, with an easy-to-use, accessible UI.
• With Microsoft Defender for Cloud, it has everything you need with the Safelink attachment, the Safelink emails for URL, the way it scans those URLs and attachments within the product, and you're seeing the results. And that adds an extra layer of security for the user, so you feel comfortable knowing the product monitors those. That's something I really like about that product.

Incentivized

• Integrations with on-premise workloads can sometimes be challenging. Needs improvement and well standardised integration points
• Vulnerability categories can be difficult to understand. It should allow teams to focus on critical findings and help them keep aside low-severity or suppressed vulnerabilities
• Pricing can be improved as it can be over-priced for smaller businesses and would potentially affect their ROI due to the small scale

Incentivized

It is a great product that integrates nicely when running an Azure platform and even multi-cloud environment. Not looking for point-solutions but a suite that answers most requirements. It is very comfortable being able to use KQL, workbooks and automation that is native to the azure platform

My visibility is limited because I'm only doing very small pieces of what the overall org does. And also, we have limitations on what we're allowed to use. It's not like we get a new product as users or leadership level users, and everything is on, and we can just do whatever we want. We're very restricted in what we can use any tooling within the org because of the different levels of regulatory constraints we have, because of just the nature of who we are inherently. So that's why. I don't think it's necessarily the product. I think it's more or less of what we're able to do with the product.

Incentivized

I believe Microsoft Defender for Cloud stacks up well against the other tools we looked at. It is native to the Azure platform and provides the same insights as the other tools. We selected Microsoft Defender for Cloud because it integrates well with the Azure resources and gives the needed insight, security alerts and recommendations.

Incentivized

• Ensuring compliance with data protection regulations can prevent costly fines and legal issues, positively impacting ROI.
• Effective cloud resource protection can optimize cloud spending and resource utilization, ultimately reducing cloud infrastructure costs.
• The subscription costs associated with Defender for Cloud can add to an organization's operational expenses, impacting ROI.
• Smaller organizations may find the feature set and complexity of Defender for Cloud unnecessary, potentially overinvesting in security solutions.

Incentivized