Our 2027 forecast: one 24/7 desk for outages and attacks
This week Microsoft 365 and Workday went down and an attack hit 178 organizations through Optimizely. All three ran overnight. Our forecast: in 2027 more of the O&M and security budget buys a round-the-clock desk that watches outages and attacks together.
- GAO says agencies typically report spending about 80 percent of federal IT money on operating and maintaining existing systems. The budget already pays to keep things running.
- In 2026, 161 of 297 new KEV entries gave agencies three days or fewer, against 7 of 245 in 2025. This week's Microsoft 365 and Workday outages and the Optimizely attack all ran overnight.
- Our forecast: 2027 money shifts toward 24/7 desks that watch outages and attacks together. The first hour decides both, and most first hours are still a scramble.
Our forecast for 2027: more agencies and companies will pay for a desk that answers around the clock and handles outages and attacks together. In practice that is a security operations center and a network operations center under one roof: tier 1 support at all hours, plus operations and maintenance (O&M) for the applications they already run. The reason is the first hour. Outages and attacks are won or lost there, and for most organizations the first hour is still a scramble.
This week, an outage and an attack began the same way
Microsoft 365 went down at 11:20 a.m. Eastern on Thursday, November 12, and was fully back at 11:10 a.m. the next day. Microsoft’s preliminary report says a bug shipped in July reached its gateway servers fleet-wide in “less than two hours” (BleepingComputer). Microsoft called it “a technical issue not related to cyber,” and still saw attackers use it: phishing emails posing as service notices cited the real incident number (SecurityWeek). Workday went offline at about 5:15 p.m. Eastern on Friday, by one customer’s account, after a disaster-recovery test went wrong. It said service was back by 11 a.m. Saturday and the disruption was not related to a cybersecurity incident (UC Today).
In the week’s attack, Report URI’s timeline puts the first malicious change to scripts served by Optimizely at 04:21 UTC on November 16, which was 11:21 p.m. Sunday in Washington. By 21:52 UTC, about 17 and a half hours later, one infected script was left. Report URI counted 178 affected organizations (SecurityWeek). For the customers, all three events looked alike at the start: a provider they rely on changed, and something of theirs broke. All three ran through a night.
Washington time. Shaded bands are 6 p.m. to 6 a.m.
Data
| Item | When | Note |
|---|---|---|
| Microsoft 365 outage | Thu 11:20 a.m. to Fri 11:10 a.m. | |
| Workday outage | Fri about 5:15 p.m. to Sat by 11 a.m. | |
| Optimizely script attack | Sun 11:21 p.m. to Mon about 4:52 p.m. | 04:21 to 21:52 UTC on November 16 |
That is the normal pattern now. Over nine years of tracking publicly reported outages, the Uptime Institute counts third-party IT and data center providers behind “about two-thirds” of them. Its May 2026 release adds that resiliency assessments “remain more focused on internal systems than on external and systemic risks.”
The clocks run on nights and weekends
Attackers keep no office hours. In the March 2026 Trivy compromise, GitHub’s advisory shows a poisoned scanner action live from about 1:43 p.m. Eastern on a Thursday until about 1:40 a.m. Friday. A second wave of bad images began on a Sunday.
The federal clock has tightened to match. We counted the CISA Known Exploited Vulnerabilities catalog (version 2026.11.13). Of 245 entries added in 2025, 7 gave federal agencies three days or fewer to fix. Of 297 added in 2026 so far, 161 did. Twenty-six 2026 entries were added on a Friday and due Monday, most recently two on November 13. Defense contractors must report a cyber incident to DoD within 72 hours of discovery under DFARS 252.204-7012.
Most federal IT money already goes to running what exists
GAO’s July 2025 report on legacy systems says the government spends more than $100 billion a year on IT and cyber, and “agencies have typically reported spending about 80 percent on operations and maintenance of existing IT” (GAO-25-107795, summary republished by OrangeSlices). GAO gave the same share in 2021 Senate testimony. On those figures, O&M is on the order of $80 billion a year. Our read: in 2027 more of that line should buy someone watching those systems at 3 a.m.
Security budgets are growing as well. IDC’s March 3, 2026 forecast puts global security spending at $308 billion in 2026, up 11.8%, with federal and central government among the top five industries. Among services, IDC expects managed security services to “see the highest growth this year,” and ties it to “the persistent global shortage of in-house security talent.” Its October update raised 2026 to $310.42 billion, up 13.2%. Across all of IT, Gartner forecasts $7.35 trillion in 2027, up 15% (Network World).
One counterweight. IDC’s Asia/Pacific forecast has managed security services there growing 7.0% a year through 2029, slower than project work, because AI now handles “tasks L1 analysts in a SOC used to perform.” Our read: AI will take much of the routine sorting. Someone on shift still has to own the call.
What a 24/7 desk does in the first hour
Tools raise alerts. A desk decides what they mean and who acts. In June, Analysys Mason described what happens when the two teams are kept apart: “When operators optimise network performance and security separately, resilience is an accident rather than a design principle.” It was written about telecom; we think it holds for agency and enterprise IT. The steps below are our read.
- Detect. Availability and security alerts go to one queue, so a failing gateway and a changed script reach the same people.
- Triage bug against intruder. Check the change log and the provider’s status page first, then look for signs of tampering. This week’s Microsoft outage traced to a code change; the Optimizely attack traced to an exploited vulnerability.
- Page the right owner. The configuration management database (CMDB) says which service runs on the failing component and who owns it, so the call goes to one named person.
- Hold an honest statement. “We are investigating” is still true on day 30. More in our piece on this week’s outages.
- Start the reporting clocks. Log the time of discovery, because DFARS counts from it. FedRAMP providers face new vulnerability rules from December 7 (our FedRAMP piece), and a three-day KEV due date can land on a Monday.
Our two forecasts for 2027
Our forecast: by December 31, 2027, IDC’s next Worldwide Security Spending Guide release will again name managed security services as the fastest-growing security services segment. The 2026 release came March 3.
Our forecast: through December 31, 2027, any GAO report or testimony that states the O&M share of federal IT spending will put it at about 80 percent or higher. If either forecast misses, we will say so here.
Our question: who answers at 3 a.m. when your vendor breaks, and can the same person tell an outage from an attack?
What we’d do first
- Stand up one tier 1 desk that watches outages and attacks together, around the clock, with a named escalation path per service.
- Write runbooks for the shared providers you depend on: cloud, identity, payroll and HR platforms, and the scripts your public sites load. Say who calls the vendor and who can pull a script.
- Connect ServiceNow ITSM and ITOM event management to the CMDB, so an alert lands on the service owner with the latest change record beside it. Our ITSM, ITOM and CSM piece covers the modules.
- Fund O&M support for the applications you already run: patching inside the KEV window and someone who knows each application at night.
- Draft the holding statements now, one for an outage and one for a suspected attack, both still true on day 30.
Where we fit: our capabilities include security operations and vulnerability response around the clock, plus incident, change and problem management with 24/7 delivery. On ServiceNow we implement ITSM, ITOM and CMDB governance, and our ServiceNow risk and efficiency assessment is now in implementation. Our work has supported the intelligence community, DHS, the Department of War (DOW) and Google, and our Next-Gen GRC beta uses the dependency graph to show affected systems in seconds. See our capabilities or compare notes with us.
Common questions
How much of federal IT spending goes to operations and maintenance?
Is security spending still growing?
Why put outages and attacks on one desk?
Will AI replace the tier 1 desk?
Sources
- BleepingComputer, Microsoft says months-old bug caused global Microsoft 365 outage (Nov 2026)Microsoft's preliminary post-incident report: start and end times, cause, 'in less than two hours'. Accessed Nov 17, 2026.
- SecurityWeek, Microsoft Rules Out Cyberattack in Outage, Warns of Phishing Campaign (Nov 2026)Microsoft statement; Microsoft Threat Intelligence on phishing that cited incident EX1550543. Accessed Nov 17, 2026.
- UC Today, Workday outage after disaster-recovery test (Nov 2026)Offline about 22:15 GMT Friday (Emerson College); restored by 11 a.m. EST Saturday (Workday to ABC10). Accessed Nov 17, 2026.
- SecurityWeek, Optimizely Vulnerability Exploited to Serve Malware on Major Websites (Nov 2026)Report URI's timeline (first injection 04:21 UTC Nov 16; one script left by 21:52 UTC) and count of 178 organizations. Accessed Nov 17, 2026.
- Uptime Institute, Annual Outage Analysis Report 2026 press release, May 13, 2026 (republished by Brandspace Online)uptimeinstitute.com refused automated requests; this is the release text. Accessed Nov 17, 2026.
- GitHub Advisory Database, GHSA-69fq-xp46-6x23: Trivy ecosystem supply chain compromise (March 2026)Exposure window table, converted to US Eastern time in make_first_hour_2027.py. Accessed Nov 17, 2026.
- CISA, Known Exploited Vulnerabilities catalog, version 2026.11.13 (JSON, public mirror cisagov/kev-data)Pinned commit of github.com/cisagov/kev-data. Counts of three-day windows and Friday-to-Monday entries; make_first_hour_2027.py reproduces them. Accessed Nov 17, 2026.
- Acquisition.gov, DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting'Rapidly report' means within 72 hours of discovery. Accessed Nov 17, 2026.
- OrangeSlices AI, GAO: Information Technology: Agencies Need to Plan for Modernizing Critical Decades-Old Legacy Systems (GAO-25-107795, July 17, 2025)Republishes GAO's summary. gao.gov refused automated requests. Accessed Nov 17, 2026.
- GAO-21-524T, Information Technology: Agencies Need to Develop and Implement Modernization Plans for Critical Legacy Systems (testimony, April 27, 2021), Senate HSGAC copyGAO's own text, hosted by the Senate committee. Accessed Nov 17, 2026.
- IDC, Global Security Spend to Exceed $300 Billion in 2026 as the Adoption of AI-Driven Security Platforms Gains Momentum (press release, March 3, 2026)Accessed Nov 17, 2026.
- IDC, Security Budgets Are Up: Why CEOs Still Worry (Oct 28, 2026)Worldwide Security Spending Guide V2: $310.42 billion in 2026, up 13.2%. Accessed Nov 17, 2026.
- IDC, APAC Security Services Growth Shifts to Advisory (Sep 3, 2026)Asia/Pacific excluding Japan and China; managed security services 7.0% CAGR 2025 to 2029. Accessed Nov 17, 2026.
- Network World, Gartner forecasts 15% global IT spending growth (Oct 22, 2026)Reports Gartner's forecast of $7.35 trillion in 2027. gartner.com refused automated requests. Accessed Nov 17, 2026.
- Analysys Mason, Why NOC-SOC convergence is becoming a strategic priority for telecoms operators (June 24, 2026)Accessed Nov 17, 2026.
Updates
- Nov 18, 2026. Added two figures: the three incidents against the clock, and the KEV deadline shift. No text or data changed.
Share on LinkedInFollow AusperSubscribe by RSS
Related reading
Working on this now?
Tell us where your program stands and we'll tell you what we would do next.
Talk to Ausper