Security Updates and Patch Management
Plan a patch rollout that tests an update, installs it on every device quickly and verifies the result, and explain why outdated software is a standing risk.
The button that says "Remind me later"
Every morning at the Nashik Road store, the billing laptop shows a small box: "MedLedger update available. Fixes a security flaw." And every morning, with three customers already waiting, Arjun Pawar clicks "Remind me later". He has done it 23 times. Nothing seems to go wrong, so the update starts to feel optional. It is not, and the reason lies in what that box is actually telling him: the makers of MedLedger have found a weakness in their own software, written a fix, and are waiting for each shop to install it.
A software update is like a vehicle recall notice. The maker has found the flaw and made the fix, but the fix only protects you once you act on it.
Software flaws are mistakes in the instructions
A program is a long list of instructions written by people, and people make mistakes. Most mistakes are harmless: a button in the wrong place, a slow screen. Some mistakes, though, let a stranger make the program do something it was never meant to do, such as show another customer's bill, accept a login without the right password, or run a file sent over the network. A mistake of that kind is a software vulnerability: a weakness in software that someone could use to read data they should not see, change it, or stop the system working.
Vulnerabilities exist in every kind of software: the operating system (the base software that runs the computer, such as Windows on the billing laptops or Android on the store phones), the web browser, apps like MedLedger, and even the small programs inside a Wi-Fi router. They are usually found long after the software is sold, by the company's own testers, by outside researchers, or sometimes by criminals. A flaw that attackers know about before the maker has a fix is called a zero-day, because the maker has had zero days to fix it. Most real attacks, however, do not use zero-days. They use old flaws that already have a fix which nobody installed.
A patch closes one known door
When a maker finds a flaw, it writes a correction and sends it out. That correction is a security patch, so named because it covers the hole in the way a tailor's patch covers a tear. Patches usually arrive inside an update, a new version of the software that may also bring new features or fix ordinary bugs. The update box on Arjun's laptop is exactly this: Rathi Softech, the company that makes MedLedger, found that its billing screen could leak data and has sent version 4.2 with the fix.
Think of the recall notices that vehicle makers send. When a company discovers that the brakes on some scooters can fail, it announces the fault, makes the repair free, and asks owners to visit a service centre. The scooter does not repair itself. An owner who ignores the letter rides around with a known brake fault, and now the fault is public, so anyone can know which scooters have it. A security patch works the same way, with one uncomfortable twist: publishing the fix also tells attackers where the weakness was.
That twist creates a race. On release day, criminals compare the old and new versions of the software to work out what changed, and within days they may have a working way to attack every copy that is still unpatched. The time between a fix being available and you installing it is your window of exposure, the period when a known door is open and attackers know it.
Both shops had the same flaw and the same fix on day 0. What differs is how long each left the door open after attackers started trying it.
Why old software is a standing risk
Outdated software is software still in use after a fix has been released, or after the maker has stopped supporting it altogether. The second case is worse. When a maker announces end of support for an old version (an old Windows release, an old phone that no longer receives Android updates), it stops making patches. Every flaw found afterwards stays open forever on that device, like a scooter model so old that the company no longer stocks its parts.
The danger is real and well recorded. The WannaCry ransomware of 2017 spread across hospitals and businesses worldwide using a Windows flaw for which a patch had been released about two months earlier; the computers it reached were mostly the ones that had not installed it. At Tulsi Health, outdated software could mean a counter laptop running an old MedLedger with a known data leak, a store phone stuck on an Android version that stopped receiving updates two years ago, or a Wi-Fi router that has never been updated since the day it was installed.
Automatic updates and why they are not the whole answer
The simplest defence is automatic updates: letting the device download and install fixes by itself, often overnight. For phones, browsers and personal laptops this is almost always the right setting, because it removes the "Remind me later" problem entirely. Riya's own phone and laptop update automatically, and she never has to think about it. On the store phones, Neha has switched automatic updates on for the operating system and every app.
For the billing laptops, automatic updates are helpful but not enough by themselves. An update occasionally breaks something: a new MedLedger version that cannot talk to the receipt printer would stop billing in all 14 stores during the evening rush. Some updates need a restart, which nobody wants in the middle of a sale. And someone needs to know whether every laptop really did update, because a laptop that was switched off on update night quietly stays behind.
Patch management: a routine, not a reaction
Patch management is the organised routine of finding out which updates are needed, testing them, installing them on every device, and checking that it worked. It turns "whenever someone clicks Install" into a repeatable process. Neha's routine for Tulsi Health has five parts, and it runs in a loop because new patches keep coming.
You cannot patch what you do not know you have, and you cannot trust a rollout you never checked. The loop starts again with each new patch.
First comes an inventory, a list of every device and the software and versions on it, because a forgotten laptop in a back room is never patched. Next comes prioritising: a fix for a flaw that criminals are already using goes first, a fix for a rare crash can wait for the monthly round. Then the update is tested on one laptop, ideally at a quiet store, to catch problems like the printer failure before they reach every counter. Then it is deployed to the rest, and finally every laptop's version is checked against the list.
The trade-off sits in the middle of that loop. Testing takes time, and every day spent waiting is a day of exposure. Skipping the test is faster but risks breaking billing everywhere at once. The skill is to test quickly rather than not at all, and then roll out fast. Try it below: Rathi Softech has just released the MedLedger fix, and attacks on pharmacies are expected from day 4.
With the plan in place, the order of the steps matters as much as the speed. Arrange Neha's rollout of MedLedger 4.2 so that a faulty update is caught early and no laptop is missed at the end.