Automox vs. AWS CloudTrail

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

It is necessary to enable [AWS] Cloudtrail when using AWS in a production environment, otherwise you will not have any idea what is happening within your accounts. Third party monitoring applications will all require [AWS] CloudTrail to be enabled as well. I would not recommend it solely as a monitoring tool, to get the most out of it you must send the logs elsewhere. Either to Cloudwatch logs or a third party product.

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

• API Log
• User activity tracking
• Real-time alerts

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

• [In my experience] Cost can easily get out of control with multiple trails on full logging
• Logs can be difficult to decipher

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

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

I think in the end, CloudTrail has more features and you can dive deeper inside the logs so it depends on your usage and what you expect in the end to make the right choice, I would say that both tools are really useful and bring a lot of benefits to I.T. companies.

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

• Allows us to investigate any strange api actions
• Increases security
• Audit trail of changes made in AWS

Incentivized