Lightweight and Powerful Patching Agent for Modern Day Reporting
Overall Satisfaction with Automox
We use Automox to stay on top of system patching for a fleet of Linux VMs running in AWS. Per our policy, which is regularly tested via a SOC 2 audit, we are required to patch critical level vulnerabilities within 30 days, Highs in 45 days, and mediums in 60+
The platform is very easy to maintain, has matured nicely with worklets and additional features, however we have only required the very basic patching and reporting features, which have been great for us.
The platform is very easy to maintain, has matured nicely with worklets and additional features, however we have only required the very basic patching and reporting features, which have been great for us.
Pros
- Manage patching policies by tag (Development, Staging, Production)
- Ease of installation / rollout to VM fleet via a simple batch script
- Simple reporting complete with visuals for easier digestion for stakeholders
Cons
- Some AWS VMs can appear as "clones" of one another if they are of identical configuration. This can cause part of your fleet to appear as offline. This has been an issue for years.
- It has freed up our engineers limited resources, and given them nights back during patch Tuesday that were otherwise spent doing more manual patching
Less concern around missing a patch window, and subsequently facing an audit finding. Greater visibility into which patches were applied.
Do you think Automox delivers good value for the price?
Yes
Are you happy with Automox's feature set?
Yes
Did Automox live up to sales and marketing promises?
Yes
Did implementation of Automox go as expected?
Yes
Would you buy Automox again?
Yes


Comments
Please log in to join the conversation