AutoMox - Patching Saver
Use Cases and Deployment Scope
We as a company need to be Cyber Security Plus compliant, therefore we need to ensure that our devices are patched regularly. Having over 250 devices, making sure all those devices are updated manually is very difficult. Automox allows me to push updates across the organization via one portal. I then can allow updates to be pushed through an Agent that then updates all devices affected. This allows our tenable reports to be in SLA standards.
Pros
- Worklet scripts to push via powershell
- Autoupdate that you can arrange according to patches
- Groups of devices that need certain updates which other devices might not needed.
- Show when a devices needs a restart for updates.
Cons
- There are some applications that updates to the wrong version causing Channel version issues, this then needs to be excluded from the policy and updated via a script.
- Certain software like NET. is not updated
- The worklet / remediation / evaluation system is not always effective, does not work all the time. Needs to be very detailed for it work.
Return on Investment
- AutoMox saved around 3 hours a day from our Internal IT team, they would have to open tenable and run scan and then arrange meetings with users who have not patched their device, this takes time from our IT guys and from the end users who have not updated.
- This also allowed us to decom our WSUS server that was on prem, which we then moved into entra ID and Azure for Domain services, Automox is similar to our old Wsus System, but with more functionality and automation.
- Visability was also Major, the ability to both see the numbers of issues coming up and how many we resolve allows us to manage our performance reviews. It allows our senior team how effectivly we are manage the system, and where our resources are being used.
Usability
Other Software Used
Kandji, Tenable Vulnerability Management, Microsoft Intune
