Automox vs. Microsoft Defender for Cloud

The reason I would score it a nine is because of the inability to “run as.” Since it only runs as a system, this makes some tasks impossible. It would be beneficial to have an encrypted set of credentials in the UI that we can use to “run as,” and also the ability to run as the current user with elevated permissions would be nice. In terms of patching, Automox does a good job, and being able to use Automox to run PowerShell on a computer without needing to open up ports for WinRM is a great feature.

Incentivized

If you need to proceed with pay as you go service then go ahead with Microsoft Defender for Cloud. This could be expensive in the long run but if the organization usage is slightly less than then this would suite the purpose. Also, it has the latest threat updates, so you're future proof in terms of potential treats.

Incentivized

• Shows applications installed on a specific asset
• Able to push policies and updates remotely , creating policies is easy.
• Keep track of compliant devices and when is the last time they have connected to the servers
• All the great information provided within one single device

Incentivized

• detect and respond to security threats in the cloud environment, reducing the risk of data breaches and unauthorized access.
• The product assists our organization dealing with sensitive data in achieving and maintaining compliance with data protection rules.
• The product provides real-time visibility into the cloud environment, offering insights into ongoing security activities.
• It guarantees that security teams can actively handle possible threats by delivering real-time monitoring and notifications, reducing the impact on business operations.

Incentivized

• I would like to see more detailed error messages when a patch fails. Perhaps at which step it failed at, downloading, installing, etc.
• It would be helpful if we could see what stage of installing or downloading a patch is at through a percentage or status bar instead of a vague "Installing..." message
• It would also be helpful to have a way to kill or end scripts that are stuck instead of waiting 24 hours for them to automatically end. Something like an "End all actions" button for endpoints on our side would be extremely helpful when testing a script that had a bad line or action in it.

Incentivized

• 'Regulatory Compliance' is definitely an area of improvement for MDC. The complex and high number of controls within a specific framework should allow a more helpful and detailed guidelines in order to tackle them.
• The limitation of options in the incident management menu of MDC has proven to be a hassle while managing security alerts. For example, an analyst cannot even provide a comment about the actions taken on an incident.
• There is a missing functionality of connecting other EDR or XDR solutions to MDC which I think should be there for a CSPM tool.

Incentivized

It's been a great tool for me. It has helped me become more efficient in my job and securing our network and machine footprint.

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

Automox has excellent dashboards that help to identify key performance indicators of where your patching program stands, what to prioritize, and what issues you have. Where Automox struggles is easily identifying what issues are preventing successful patching, seeing what manual patches are successfully installing/not installing, and easily remediating issues with installation issues.

Incentivized

In my experience, they were responsive but the fixes were more like bandaids than a fix for the underlying problems which they admitted were on their end.

Incentivized

i was able to implement automox with the help from their support to push it out via our MDM of maas360

Incentivized

Automox is able to scale better than PDQ Deploy. We were happier with the 3rd party software patching since we have a lot of different software we use across departments. PDQ deploy required a lot more manual intervention to stay on top of deployments. Automox just ended up being a timesaver for us in the end.

Incentivized

We used to use Symantec and McAfee. It's been mostly defenders since, gosh, the last eight to 10 years. So we're a small organization. We don't have a lot of folks, so single-painted glass is really important to be able to see the whole environment in a single place. And the Microsoft tooling gives us that.

Incentivized

• We used to use a different patching solution and since switching to Automox, I have been able to cut the amount of time I spend on vulnerability management by 50% or more. I love how "set it and forget it" some of the policies can be. I love how simple it is to keep an eye on things.

Incentivized

• It simplifies security management and saves time. I'm not sure, but I'm very confident it saved me a couple of paychecks by centralizing the data I need to secure the cloud environment.
• I also utilize the inventory overview to monitor my team's activities and verify they are following internal regulations, as well as cost overruns.
• The recommendations can be utilized as a valuable instructional tool. I have the team explain why they are receiving them, why they are not following them, and what they are doing differently.

Incentivized