Critical Infrastructure Security

Black October and November’s outages show why businesses must rethink downtime

(Adobe Stock)

COMMENTARY: Black October delivered a global warning about the growing role of AI in vulnerability discovery, and the rapidly shrinking window cybersecurity teams have to detect, assess, and respond to threats.

Among the month's most significant developments, researchers using advanced AI models uncovered remote code execution (RCE) vulnerabilities affecting PHP, estimated to run roughly 70% of websites. The disclosures triggered emergency patching efforts across cybersecurity teams.

[SC Media Perspectives columns are written by a trusted community of SC Media cybersecurity subject matter experts. Read more Perspectives here.]

November showed what unplanned downtime looks like. In six days, outages hit Microsoft 365, U.S. air travel, online banking at major U.S. banks, Apple's services, and NSANet. None has been linked to a cyberattack. Two trace back to a change. Microsoft's to a latent defect in an earlier fix, Apple's to an internal update. Every patch represents a change, and every change can take something down.

Black October was a wake-up call for the cyber industry, November was a warning to the world about the consequences of outages. But very little has changed except the volume and the speed. We need to rethink how the business absorbs the downtime that faster patching brings, and how quickly it can finish user acceptance testing after each patch, especially on mission-critical ERP systems.

A growing volume of vulnerabilities

The number of reported vulnerabilities has risen year-over-year, and 2026 broke the trend line. CVE Program records show about 98,000 new CVEs published by mid-November, roughly double the whole of 2025. October alone brought 17,050, four times as many as October 2025 and more than 10 times as many as October 2020. As technology becomes more complex, the number of potential weaknesses grows with it. And AI helps both researchers and attackers find flaws faster.

At the same time, the window between disclosure and exploitation continues to shrink. For years, the average time to exploit has moved closer to zero as attackers have become faster at turning publicly-available vulnerability information into working attacks. Today, we're seeing the disclosure of vulnerabilities after attackers have already exploited them, which leaves defenders confronting zero-day threats with little or no warning.

Black October taught us that we have to patch faster and more often. For business-critical systems, though, patching equals downtime. Taking an ERP platform offline, for example, can affect quarter-end financial processes, production operations, supply chains, and customer commitments. Companies must have the ability to tolerate disruption.

Here are three ways to make faster patching more manageable:

  • Reduce the attack surface: Start by reducing the number of systems and devices exposed to the internet. Management interfaces, such as admin consoles for network devices and websites, matter most. Attackers look for accessible entry points. The more internet-facing apps, devices, remote-access services, and management interfaces an organization has, the more opportunities an attacker has to exploit a weakness. Organizations should identify systems that do not need to be externally accessible and remove that exposure wherever possible. For assets that must remain internet-facing, compensating controls such as zero-trust network access, web application firewalls, strong authentication, network segmentation, and continuous monitoring help reduce risk. Reducing the attack surface also reduces the patching burden. Fewer exposed systems mean fewer urgent remediation decisions and fewer maintenance events that could affect business operations.
  • Build resilience for unplanned downtime: Business continuity planning has traditionally focused on fire, fools, and floods. Cyber has become the fourth category. Teams can work around a planned outage. For example, staff switch to pen and paper and catch up in the system afterward. But unplanned outages are different. Work stops and people go home. We must aim to make patching planned, frequent, and routine, so an urgent fix never becomes an unplanned outage. Vendors have already set a monthly pace. SAP releases security notes every month, and, since May 2026, Oracle has added monthly critical patches between its quarterly updates. Where the platform supports it, use hot patching, such as Windows Hotpatch or Linux live patching, to apply fixes without a reboot. Expect emergency patches between monthly cycles too, whenever a disclosure or threat intelligence demands it. Emergency patching also wears out the people doing it. Routine patching protects the team as well as the business. Unplanned outages will still happen, as November showed. Organizations need to understand which systems are critical, and also how those systems connect and what happens when one of those dependencies fails. This means identifying single points of failure, testing failover procedures, maintaining alternative ways to perform essential business functions, and ensuring recovery plans work.
  • Master the security fundamentals: No automated tool or advanced AI capability can compensate for weak security fundamentals. Organizations must continue to prioritize foundational controls, including: an accurate asset inventory, including end-of-life and unsupported systems; phishing-resistant multi-factor authentication (MFA); endpoint detection and response (EDR) and vulnerability management on every asset, not most of them; monitoring that someone acts on.

There’s no point deploying a tool if no one acts on what it finds.

What’s next for patching?

My prediction for 2027: monthly patch windows will become the minimum for business-critical systems such as ERP. But the reality: Quarterly doesn’t cut anymore, and we’re headed to weekly, even daily, patching windows. That doesn't mean patching every day. It means being able to patch on any day, with a business ready for the disruption.

Discovery will continue to escalate to the point where manual patching processes can’t keep up. Vulnerability management, including patch deployment, will need to become more automated. Automated patching carries its own risks, like compatibility issues or broken applications, but so does waiting on critical updates. Organizations must find ways to accelerate remediation without compromising business operations.

The bottleneck will not be the patch, but rather the testing. Few businesses can staff a round of user acceptance testing every week, so automated patching has to come with automated testing that proves critical business functions still work.

Many in the industry now hope that AI will eventually turn the tide, catching flaws before software ships and leaving less technical debt behind. I'm not convinced yet. Without security built into the development pipeline, AI-written code does not necessarily mean more secure code, just differently insecure code. Expect several years of high vulnerability volumes before that changes and even longer for systems too old to patch.

As organizations head into 2027, cybersecurity leaders face a faster threat cycle and a less predictable technology environment. Preparing for it will require reducing exposure, strengthening operational resilience, and treating cyber and technology disruption as a business continuity issue. Automating patching and testing will help teams match the speed and volume of new flaws.

Black October demonstrated what happens when vulnerability discovery outpaces an organization's ability to respond. November's outages reinforced that technology failures can have far-reaching business consequences. The organizations best positioned to withstand what comes next will stop treating vulnerability management and business continuity as separate problems and start approaching both as ongoing business priorities.

Jack Cherkas, global chief information security officer, Syntax

SC Media Perspectives columns are written by a trusted community of SC Media cybersecurity subject matter experts. Each contribution has a goal of bringing a unique voice to important cybersecurity topics. Content strives to be of the highest quality, objective and non-commercial.

Get daily email updates

SC Media's daily must-read of the most current and pressing daily news

By clicking the Subscribe button below, you agree to SC Media Terms of Use and Privacy Policy.

You can skip this ad in 5 seconds