Do you recognize that nagging feeling that you have less control over the software in your organization than you would like? And do you actually know how that software is being updated—if you are not even aware of everything running on your systems?

Blink your eyes and read a news article: another organization falls victim to an attack. Cause? An unpatched vulnerability. Oh. Another sleepless night.

Let's change that. Test Automox today. This is a cloud-based Patch & Endpoint management tool that works with a local agent. Now you might be thinking: another agent? Yes. But this one has an extremely small footprint. Promised.

With Automox, you take direct control over updating operating systems (Windows, Linux, Mac) and over 580 third-party applications. Think of CVE suppliers like Java and Adobe, browsers like Firefox, Chrome, and Brave, but also applications like Zoom and the entire Office suite.

Backlog maintenance? We'll fix that

In organizations where patch management was not a priority, there is a high chance of a 'debt' of backlog maintenance. Software that has not been updated for years quietly runs in the background and no one pays attention to it. That's asking for trouble. Time to do something about it.

We'll show you how quickly and easily you can test Automox—completely free. 

Getting started in five steps (basket edition):

1. Request a trial tenant  2. Download the agent  3. Install the agent  4. Set policy  5. Patching and becoming more secure

Want more details? Here is the comprehensive approach:

1. Request a trial: Send us an email at help@brandaris.it requesting a trial tenant, and we'll make sure you have it in no time. Let us know in your email if you want to handle the configuration yourself or if we should set up a patch schedule for you. Both are fine and both are free. This way, you can test Automox for two weeks immediately.
   
   
2. Install the agent: Download the agent from your trial tenant and install it with your unique token. Prefer to roll out centrally? You can do that through your standard software manager. You can add as many systems as you want.
   
   
3. Automatic scan: Once a system is added to Automox, it is immediately scanned for existing software and connectivity. This process only takes a few minutes. After that, Automox knows exactly which versions are running and, more importantly, which updates are available.
   
   
4. Set policy: Now Automox needs to know how you want the patching to be done. You want to control when patches are rolled out. Should systems restart immediately? Or should users receive a notification first? Or do you force a reboot if they dismiss it too often? You determine all of this in a patch policy.
   
   You have the following options:
   ✅ Patch All – Patches all supported software.
   ✅ Manual Approval – Patches only after approval.
   ✅ Severity-based patching – Patches only vulnerabilities with a certain criticality.
   ✅ Patch All Except… – Patches everything except specific exceptions.
   ✅ Patch Only… – Patches nothing except what you explicitly select.
   ✅ Advanced – Full control with manual criteria. In addition, you set when the patch round can run and what should happen if the patching moment is missed.
   
   

Manage patches per group:
You can create multiple policies with different patch times and rules. In addition, you can divide systems into groups. Think of:
• A pilot group to test updates first
• Location-specific policies for offices in different locations
• Separate policies per type of system, such as workstations, servers, or test environments

Creating groups is simple:
✔ Add systems based on name, location, or hardware type
✔ Link one or more policies to a group
✔ Manage everything centrally and apply settings directly

Whether you want everything tightly regulated or want to leave room for flexibility—you decide what your patch management looks like.

Tested and convinced? Or still waiting?

If you like Automox, we'll effortlessly convert your trial into a production license. Still unsure? No problem. With one click, you can remove the agent and clean up your systems.

Are you willing to invest an hour in this?