One IT service provider, twelve vendors, one email: how EIFBYTE keeps track of client updates with patchletter
Guest post by EIFBYTE, an IT systems house from Euskirchen, Germany.
An IT service provider with several clients has an update problem that a single admin doesn’t know in quite the same way: it doesn’t look after one environment, but many small ones. One client has a Synology NAS in the storage room, the next runs virtual servers on Proxmox VE, the third adds Veeam. Each of these vendors publishes in its own way. At some point we stopped keeping all of that in our heads and let patchletter tell us instead.
The problem: the most dangerous devices don’t speak up
Windows, Edge and Chrome fetch their updates on their own. That’s the easy part. It gets difficult with everything that stays where it is unless someone nudges it:
- the firewall that sits directly on the internet,
- the NAS holding the data that gets encrypted in an attack,
- the hypervisor that runs all of a client’s servers,
- remote-support and admin tools that have access everywhere.
For each of these there is a newsletter, a forum or a release-notes page somewhere. With a dozen products that makes a dozen channels in different formats, between webinar invitations and advertising. The one important email gets lost in there.
How we set up patchletter
We ticked the products that run at our clients and in our own environment, and confirmed the email address. An excerpt from the list:
- Virtualisation and backup: Proxmox VE, Veeam Backup & Replication, Windows Server
- Storage: Synology DSM
- Remote support and access: RustDesk, OpenSSH
- Web and collaboration: WordPress, PHP, Nextcloud
- Containers: Kubernetes, Docker Engine, Traefik
As a rhythm we use the daily digest. In the morning there’s an email in the inbox with everything that changed the day before. If there’s nothing new, nothing arrives. That sounds trivial, but it is the actual reason it works: an email that only comes when it has something to say actually gets read.
What happens after the email
The email is the start, not the work. For us the same routine always follows:
- Read the release notes. Does the update close a security hole, or does it only bring features?
- Map affected clients. Which client runs the product in which version? For this we keep documentation for every environment.
- Schedule it. A hole in a firewall gets closed promptly; a feature update for a NAS goes into the next maintenance window.
- Check the backup, install, verify. Only once the latest backup demonstrably works do we update.
Step 2 is the one patchletter can’t take over, and doesn’t want to: the service knows that Proxmox VE 9.2 is out, but not which version is running at the client. We do that matching ourselves.
The underrated part: end of support
Next to the current version, the product pages also show the support cycle. For Proxmox VE you can see at a glance that only the 9 series is still maintained. In conversations with clients that is often more important to us than the individual update. A system without vendor support can no longer be patched, no matter how attentive you are. A link to the product page explains that to a managing director faster than any presentation.
Who it’s worth it for
For small businesses that run their own IT, the free update email is enough to start with. For service providers with several clients it gets interesting as soon as several people work through the notifications, or warnings about actively exploited vulnerabilities should arrive before the vendor has a patch. Those are the features of the Pro plan.
How we explain the topic to businesses from the client’s point of view, with a step-by-step guide, is described in detail on our website (in German): Software-Updates überwachen: Warum wir patchletter nutzen.
About EIFBYTE
EIFBYTE is an IT systems house from Euskirchen and supports businesses in the Euskirchen district, in Bonn, Cologne and the Rhineland, as well as DevOps and Kubernetes environments. Part of the managed IT services from EIFBYTE is not leaving updates to chance: from the notification to the documented installation.