Patch Management for Small Business: Why It's Getting Harder

Key takeaways
Palo Alto Networks CEO Nikesh Arora said critical and severe vulnerabilities are being discovered at nearly seven times last year’s monthly average, Yahoo Finance reported on November 19, 2026.
Arora suggested that rushed patches and configuration changes may have contributed to some recent outages. Yahoo Finance reported the incidents appeared unrelated, with no evidence of a coordinated cyberattack.
IT workers on r/sysadmin say the real limits are staffing, budget and lost institutional knowledge, and those limits apply to a 25-person office as much as to a bank.
Patch management for small business is getting harder for the same reason it is getting harder for airlines and banks: far more serious flaws are being found, and the fixes have to go on faster than they can be tested. On a November 18, 2026 earnings call, Palo Alto Networks CEO Nikesh Arora said critical and severe vulnerabilities were being discovered at nearly seven times the previous year’s monthly average, while AI was helping attackers move faster, according to Yahoo Finance. He suggested that rushed patches and configuration changes may have contributed to some recent disruptions.
What did Yahoo Finance report about the recent outages?
Yahoo Finance reported on a series of outages involving United Airlines, JPMorgan Chase, the FAA and Microsoft Outlook. In the earnings call, Arora pointed to two pressures facing IT teams: the surge in vulnerabilities that need patching, and AI helping attackers move faster.
Yahoo Finance reported that the incidents appeared unrelated and that there was no evidence of a coordinated cyberattack. Arora also expects the heavy volume of patches to continue for at least the next 18 months, Investing.com reported. We covered the outages themselves in our earlier post on the nationwide outages and business continuity.
How many more vulnerabilities are there to patch?
The number of published software vulnerabilities has been climbing for years. Researcher Jerry Gamblin’s annual counts show 28,818 CVE records published in 2023, 40,009 in 2024 and 48,185 in 2025. Every one of those is a flaw someone has to assess, and many need an update installed.
Meanwhile, the fixing has slowed down. Verizon’s 2026 Data Breach Investigations Report found the median time to fully patch a vulnerability rose to 43 days, from 32 days a year earlier. The share of known exploited vulnerabilities that organizations fully fixed fell to 26%, from 38%. The same report found that exploiting vulnerabilities is now the most common way breaches begin, at 31% of cases.
What are IT teams saying about patching?
The Yahoo Finance article was picked up on r/sysadmin, the Reddit community for system administrators. Six reactions stood out.
Cybersecurity spending could rise, but where will it go? One of the leading commenters, who said they work directly on these problems, predicted a wave of cybersecurity investment and vendor changes. A reply raised a question familiar to anyone working in IT. Will that spending create more jobs for the people doing the work, or will companies put more of it toward outsourcing?
Treating IT as a cost center has consequences. Another commenter argued that companies routinely ignore IT recommendations and run with skeleton crews, even though employees across the business depend on those systems. Their frustration was with the gap between what leadership expects during an outage and what it funds before one happens.
At one major bank, vulnerability management is crowding out routine work. An infrastructure worker said several understaffed teams were already struggling to keep up. They expected companies to lean more on AI for incident response and raised a harder question about how much authority those tools should have. Taking a live system offline to contain an intrusion could protect the business from further damage while also interrupting services customers rely on.
Some readers questioned the CEO’s incentives. One commenter argued that executives already understand these risks but prioritize short-term results. A reply took aim at Palo Alto Networks specifically, suggesting the warning sounded like a pitch to sell more firewalls and questioning how much the CEO knew about the causes of the individual outages.
Some teams are already accepting the risks of immediate patching. One commenter predicted that internet-facing equipment would increasingly update automatically. In a reply, a sysadmin said their organization had already made immediate patching the default, even on Windows. Leadership signed off after weighing the risk of an update breaking something against the risk of leaving a known vulnerability exposed.
Layoffs also take institutional knowledge out the door. Another commenter felt the article overlooked what happens when IT teams get smaller and lose senior staff. An experienced administrator may know which applications depend on an old server or which systems need to come back online first after a restart. That knowledge matters when a team has to test and deploy an urgent patch in hours. The commenter was skeptical that buying another AI product would make up for losing it.
What does this mean for a business with 10 to 75 employees?
The same tradeoff applies at a smaller scale. A law firm, financial office or medical practice in suburban Chicago does not have a vulnerability management team, but it has the same Windows PCs, the same Microsoft 365 and often the same brand of firewall as the companies in the headlines. Someone still has to decide how quickly updates go on and what happens if one breaks something.
In a small office, the institutional knowledge the commenters described often lives in one person’s head, or with an outside provider of managed IT services. If nobody has written down which program depends on which server, an urgent patch becomes a guess.
What steps should a small business take now?
These steps come out of the points the IT teams raised, sized for a small office.
Agree on a patching speed before the next emergency. Decide with leadership how quickly updates go on, and have them sign off on the tradeoff, the way the sysadmin in the thread described.
Patch internet-facing equipment first. Firewalls, VPNs and remote access devices are where automatic updates were predicted to become the norm.
Write down what only your senior people know. Record which applications depend on which server and what needs to come back online first after a restart.
Keep a tested backup. If an update breaks something, a recent backup that has actually been restored once is what lets you roll back.
Decide who, or what, can take a system offline. If a security tool or outside provider can isolate a machine during an intrusion, agree on the limits ahead of time.
Frequently asked questions
Why is patching getting harder?
More serious flaws are being found, and attackers are moving faster. Palo Alto Networks’ CEO put the discovery rate for critical and severe vulnerabilities at nearly seven times last year’s monthly average, as reported by Yahoo Finance.
Did a cyberattack cause the recent outages?
Yahoo Finance reported that the incidents appeared unrelated and that there was no evidence of a coordinated cyberattack. Arora suggested rushed patches and configuration changes may have contributed to some of them.
How long do companies take to install patches?
Verizon’s 2026 Data Breach Investigations Report put the median time to fully patch a vulnerability at 43 days, up from 32 days in the prior report.
Should a small business patch immediately or wait and test?
Both choices carry risk. One organization in the r/sysadmin thread made immediate patching the default after leadership weighed an update breaking something against leaving a known vulnerability exposed. The important part is that the decision is made on purpose, by the people who own the risk.
Where Edward Technology fits
Edward Technology provides managed IT services from Elmhurst and Barrington for suburban Chicago businesses with 10 to 75 employees. Patching, cybersecurity and vulnerability and penetration testing are part of that work, and so is recovery when something goes wrong, as in how we recovered a flooded office.
We are an IT company. Nothing here is legal, financial or medical advice.
Written by Errol Janusz, owner of Edward Technology. 17+ years in business and 25+ years as Microsoft Certified Professionals.
Sources: Yahoo Finance; the full r/sysadmin discussion; Verizon 2026 Data Breach Investigations Report; CVE counts via YesWeHack and Trend Micro; Investing.com.




Comments