Patch Management

Keeping every program and device you use up to date on a plan, because most updates are repairs for holes that are already public.

Also known as software updates security patching update management

Definition

Patch management is the plain job of keeping every piece of software you use up to date, on purpose rather than by accident. A patch is a small fix the maker sends out after the program is already in your hands. Most people meet it as the box that says an update is ready, with a button that says Later.

Here is the part people miss. Most updates are not new features. They are repairs to holes someone found in the program, and the maker publishes what the hole was on the day the repair comes out. That notice is public. Anyone can read it, and automatic tools read it within hours, then go looking for machines that have not been repaired yet.

So pressing Later for six months is not a delay. It is a decision. The shop keeps running exactly as before, nothing looks broken, and the door stays open with a published map of how to walk through it. Nearly every break-in Linkysoft is called in to clean up came through a hole that had a fix available months earlier. That is the uncomfortable pattern, and it is why a security check starts with a list of versions, not with new software.

The fear behind the Later button is fair. An update can break the till at the worst hour. The answer is a routine, not courage. Pick a quiet slot, Tuesday at seven in the morning for most shops. Update one machine first and use it for a day. Take a copy of your data before anything else. And keep a note of who to ring if the printer stops.

The other half sits where you cannot see it. The server that holds your website and your email needs the same treatment, and most owners assume somebody else is doing it. Ask your provider, in writing, who applies those fixes and how fast. On Hostrena hosting that work belongs to us and happens on a schedule. For a system Linkysoft built for you, ask the same question about the parts inside it, because a web application is made of dozens of borrowed pieces, and each one has its own repairs to install.

Questions about Patch Management

Are software updates really about security?
Most of them are. New buttons get the attention, but the bulk of a typical update is repairs for holes that are already known and written up in public.
What can happen if I skip updates for a year?
The known holes stay open the whole year. Automatic tools keep scanning for them, so the usual ending is locked files and a ransom demand, not a clever targeted attack.
Can an update break my system?
It can, which is why you update one machine first, take a copy of your data the same morning, and pick a quiet hour. That turns a real risk into a small inconvenience.
Who updates the server my website runs on?
It depends on what you bought. With managed hosting the provider does it. With a plain server it is your job, even if nobody told you. Ask in writing and keep the answer.
How often should a small business do this?
Once a month for the ordinary list, and within a few days for anything the maker marks as urgent. Phones, card readers and the website count as machines too.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.