
Why Having a Digital Disaster Plan Is Essential in the Age of AI
Nov 22, 2026 · @disc
One week of outages. One confirmed attacker.
In roughly seven days, Microsoft’s workplace tools went dark, the FAA stopped every departure in the country, bank apps stumbled, Apple Pay and iCloud faltered, and a website-testing vendor became a malware delivery channel for 178 brands.
Only one of those has a confirmed attacker behind it.
That is the point a lot of people missed. Technology doesn’t need criminals to fail. It fails on its own, through an upgrade, an update, an aging system, or a vendor you forgot you depend on.
In my last post on the Optimizely compromise, the lesson was that your attack surface is everything your pages are allowed to load. This week widens it. Your resilience is everything your business is allowed to depend on.
And in 2026, more of what we depend on is AI. When Outlook goes down, people walk over and talk. When the assistant that drafts, summarizes, triages, codes and answers customers goes down, the work itself stops. Most companies have never planned for that day.
What actually happened
The disruptions landed back to back, but reporting so far shows no evidence they were connected (Fortune). Look at what failed and why.
| When (2026) | What failed | Impact | What’s known about the cause |
| Thu, Nov 12 | Microsoft workplace services | Outlook, Teams and Copilot disrupted for organizations worldwide | Not detailed in the coverage I reviewed |
| Fri, Nov 13 | FAA air traffic systems | A rare nationwide ground stop of more than four hours; tens of thousands of delays and cancellations, and over 1.5 million passengers affected | Reporting points to a network upgrade at an FAA facility that overloaded an older system; the FAA has paused a router rollout |
| Mon, Nov 16 | JPMorgan Chase and other banks | Problems with transactions and online services; Wells Fargo and Capital One customers also hit | Described as a technical issue |
| Tue, Nov 17 | Optimizely | A “security incident” affecting customers’ digital infrastructure, including Zoom | Attacker exploited the vendor’s platform to push malicious code to 178 organizations |
| Tue, Nov 17 | Apple | Apple Pay, the App Store and iCloud disrupted for some users | An internal update, per Apple |
One attack. Two failures traced to change: a network upgrade and a software update. The rest are, so far, unexplained “technical issues.”
Zach Iscol, who ran New York City’s emergency management, put it well in ABC’s coverage: this is no reason to panic, but it is a reason to check the plans you already have. We live in a deeply interconnected world, and we lean hard on critical infrastructure whether we notice it or not.
Theresa Payton, CEO of Fortalice Solutions and a former White House CIO, went further. She said these events show why everyone, from government agencies and companies down to individual households, needs a current digital disaster plan, built before the outage, not during it.
Why AI raises the stakes
A classic disaster recovery plan asks one question: what if the system goes down? AI adds three harder ones. What if it is slow? What if it is wrong? And what if it is quietly doing something you didn’t authorize?
Here are the five ways I see AI changing the disaster math for the B2B SaaS and financial services firms I work with.
1. Concentration: a few providers, everywhere at once
A handful of model providers and clouds now sit underneath your copilots, support bots, coding assistants and the AI features inside your SaaS tools. One provider outage can stop work across departments that think they use “different” tools. One health system in Fortune’s coverage said its growing reliance on Copilot pushed it to rethink redundancy for those apps.
- Risk: a single upstream outage halts many business processes at once.
- Threats: denial of AI service and unbounded consumption (OWASP Top 10 for LLM Applications, LLM10; MITRE ATLAS, Denial of ML Service).
- Control: tier AI workflows by criticality and give Tier 1 workflows a fallback model or a manual path.
- Evidence: a tiered AI dependency list with a named fallback for each Tier 1 entry.
2. Hidden fourth parties
You know you buy a CRM. You may not know which model provider your CRM’s AI feature calls, or that a vendor switched on an AI feature by default last quarter. The Optimizely incident showed how one trusted vendor can reach 178 companies at once. AI features add another layer of vendors behind your vendors.
- Risk: a failure or compromise you can’t see, can’t plan for and can’t fail over from.
- Threats: supply chain compromise (OWASP LLM03; MITRE ATLAS, ML Supply Chain Compromise).
- Control: require AI disclosure in vendor intake and contracts: which models, which providers, what data, what notice of change.
- Evidence: vendor AI disclosures on file, mapped to your dependency list.
3. Change at machine speed
Two of this week’s failures came from change: an upgrade and an update. AI accelerates change. Coding assistants ship more code. Agents with production access make changes without waiting for a change advisory board. Model providers retire and swap model versions on their own schedule.
- Risk: more changes, made faster, with less human review in the loop.
- Threats: excessive agency (OWASP LLM06) and improper output handling (OWASP LLM05).
- Control: keep AI-generated and agent-initiated changes inside change management, with tiered approval gates for privileged actions.
- Evidence: change records that show which changes were AI-initiated and who approved them.
4. “Wrong” is a failure mode, not just “down”
A crashed server is obvious. A model that starts returning confident, wrong answers after a silent provider update is not. Neither is an agent that keeps running after its instructions were hijacked through a poisoned document. Your monitoring sees green while the business makes bad decisions.
- Risk: degraded integrity that no uptime monitor will catch.
- Threats: prompt injection (OWASP LLM01), data and model poisoning (LLM04), misinformation (LLM09).
- Control: quality monitoring on AI outputs, plus a kill switch someone is authorized and trained to use.
- Evidence: output-quality alerts, a named kill-switch owner and a log of when the switch was tested.
5. Attackers love an outage
Every widespread outage triggers a wave of “verify your account” messages. AI makes those lures cheaper and more convincing: cloned voices of a “bank representative,” flawless phishing in any language, fake status pages. Confusion is the attacker’s best cover.
- Risk: staff and customers act on fake instructions during the chaos.
- Threats: AI-enabled social engineering and impersonation.
- Control: pre-agreed verification steps and official channels people know to check before acting.
- Evidence: a published outage communication policy and phishing-awareness content tied to outages.
Start at home: the personal plan
Resilience starts with the people who run your company, so the household basics matter. Iscol’s advice is classic emergency preparedness: keep shelf-stable food, water for several days, a first-aid kit and flashlights at home. Think about who depends on you, including older relatives, anyone on medication, and pets. Keep some cash, and protect the documents you’d need if systems were unavailable.
Payton’s advice was more digital. Make the plan before the outage, and keep it current. And don’t tie all of your money to a single financial institution. If one bank’s systems go down, a second account keeps rent, payroll and groceries moving.
I’d add a few items that matter more now that AI is in the mix:
- Offline copies of IDs, insurance policies, account numbers and key contacts, stored securely and printed.
- Recovery codes for MFA and the emergency kit from your password manager, kept somewhere you can reach without your phone.
- A second way to talk: a backup messaging app or phone plan agreed with family or co-founders in advance.
- Your bank’s real phone number, written down. During an outage, never call a number from a text, email or search ad.
- A family code word. If a cloned voice of a relative calls in a panic asking for money, the code word ends the scam in one question.
Where a digital disaster plan lives in your frameworks
You don’t need a new framework for this. ISO/IEC 27001 already covers continuity. ISO/IEC 42001, the NIST AI RMF and the EU AI Act extend it to AI systems. Here’s how the pieces line up.
| Plan element | ISO/IEC 42001 | ISO/IEC 27001:2022 | NIST AI RMF | EU AI Act |
| AI and dependency inventory | Cl. 4.3 scope; A.4 resources for AI systems | A.5.9 inventory of assets | MAP 1, GOVERN 6 | Art. 11 technical documentation |
| Third-party and fourth-party AI risk | A.10 third-party and customer relationships | A.5.19–A.5.23 supplier and cloud services | GOVERN 6.1–6.2, MANAGE 3 | Art. 25 value-chain responsibilities |
| Continuity, redundancy and failover | Cl. 6.1 risk treatment; A.6.2.6 operation and monitoring | A.5.29, A.5.30, A.8.14 | MANAGE 2.3–2.4 | Art. 15 robustness, including backup and fail-safe plans |
| Human oversight and kill switch | A.9 use of AI systems | A.5.29 security during disruption | MANAGE 2.4 disengage or deactivate | Art. 14 human oversight, including the ability to stop the system |
| Change control for AI and agents | A.6.2.5 deployment; Cl. 6.3 planning of changes | A.8.32 change management | MEASURE 2.4, MANAGE 4.1 | Art. 72 post-market monitoring |
| Incident response and communication | A.8.4 communication of incidents | A.5.24–A.5.27 | MANAGE 4.3 | Art. 73 serious incident reporting |
| Testing and exercises | Cl. 9.2 internal audit; Cl. 9.3 management review | A.5.30 ICT readiness | MEASURE 2.6 fail safely | Art. 9 risk management and testing |
Verify clause and control references against the current published texts before an audit. Numbering in guidance documents.
What I see in the field
I led Virtual Data Room through ISO/IEC 42001 Stage 2 certification on the first audit attempt. Virtual Data Room runs virtual data rooms for M&A and financial transactions. That is the hard mode of compliance: customers test every control, and “we think so” is never an answer.
The work started the same way every time. We mapped every AI use case first, including the shadow AI nobody had registered. We built the risk register before we wrote policies. And we collected audit evidence as we went, not in a panic at the end.
Across that engagement and others, three patterns keep showing up when I ask about AI continuity:
- The inventory stops at the front door. Teams list the models they built or bought. They miss the vendor features that call a model behind the scenes, so those dependencies never reach the continuity plan.
- Oversight is a checkbox, not a log. A policy says a human reviews AI output. Nobody can show me what the reviewer saw, what they changed, or why. When the model misbehaves, there’s no trail to tell you since when.
- Nobody owns the off switch. Ask who is authorized to disable an AI feature or an agent at 2 a.m. and you usually get silence. If no one owns the switch, you don’t have one.
If the artifact doesn’t exist, the control doesn’t either. That applies to disaster plans more than anything else.
My perspective: how to build a digital disaster plan for the AI era
Here’s my view. Most business continuity plans were written for a world where systems were either up or down, and where you knew who your vendors were. Neither is true anymore. A digital disaster plan for the AI era has to cover outages, bad outputs, compromised vendors and the scams that follow all three.
The good news is that it isn’t a giant project. It’s eight steps, and each one ends in an artifact you can show a customer, an auditor or your board.
- Map what you actually depend on. List your systems, SaaS tools, cloud services, model providers, agents and the AI features inside your vendors’ products. Give each one an owner.
- Evidence: a dependency map with owners, including fourth-party model providers.
- Rank by time to harm. For each dependency, ask how long the business can run without it before customers, revenue or compliance suffer. Put the answers into three tiers.
- Evidence: a tiered list with the maximum tolerable downtime for each entry.
- Define degraded mode for every Tier 1 AI workflow. Decide what happens when the model is down, slow or wrong. That might be a fallback model, a rules-based path, or a human queue with a runbook.
- Evidence: a written runbook and a named owner of the kill switch.
- Remove the single points of failure that hurt most. Add a second communication channel, route AI calls through a gateway that can switch providers, keep a second bank relationship, and hold offline copies of what you can’t lose.
- Evidence: a failover that has actually been tested, with the date and result.
- Learn to tell “down” from “attacked.” Optimizely showed that a trusted vendor can be the attacker’s path. Your incident plan needs triage criteria that separate a provider outage from a compromise, a poisoned model or a hijacked agent.
- Evidence: a decision tree in the incident response plan, with escalation contacts.
- Write the messages before you need them. Pre-approve templates for customers, employees and the board. Commit to sharing what you know early, and pad your recovery estimate rather than overpromising. Include a line warning people about outage-themed scams.
- Evidence: approved communication templates and an agreed list of official channels.
- Rehearse the bad day. Run a tabletop on a realistic scenario: your primary AI provider is unavailable for 18 hours, or your support agent starts giving customers wrong answers. Time how long it takes to notice, decide and switch.
- Evidence: an exercise report with findings and owners for each fix.
- Put it into contracts and governance. Ask AI vendors for uptime commitments, incident notice timelines and advance notice of model changes. Feed the results into your AI risk register and management review, so the plan is updated, not just filed.
- Evidence: contract clauses, risk register entries and management review minutes.
Then go back to step one. Dependencies change every time someone signs up for a new tool or a vendor ships a new AI feature, so the plan is a loop, not a document.
One of the CIOs Fortune interviewed this week put it in a way I agree with: resilience isn’t a binder or a backup system. It’s a muscle you build with your operations team before anything breaks. AI doesn’t change that. It just raises the price of skipping the workout.
Free tool: find your AI blind spots before the next outage does
Step one of any disaster plan is seeing what you depend on. That’s what the free AI Governance & Risk Exposure Assessment is for. It asks 25 questions across six areas: Governance, Security, Compliance, Third-Party Risk, Human Oversight, and Model & Agent Monitoring. It takes about eight minutes.
What you get:
- An AI exposure index from 0 to 100
- A radar chart of your six areas, so the weak spots are obvious
- Your top five priority exposures, each with remediation steps
- A board-ready PDF mapped to ISO/IEC 42001, the NIST AI RMF, the EU AI Act, the OWASP Top 10 for LLM Applications and MITRE ATLAS
How to read it through this post: if your lowest scores sit in Third-Party Risk or Model & Agent Monitoring, your disaster plan has a blind spot. You can’t fail over from a dependency you never mapped, and you can’t switch off an agent nobody is watching.
Take the free AI Governance & Risk Exposure Assessment
How DISC InfoSec can help
| Service | What you get | Best for |
| AI Governance Quick-Start | AI and agent discovery, a shadow AI and data exposure review, a risk register with named owners, and a remediation roadmap in 7–10 days | Teams that need their AI dependency map, step one of the plan, fast |
| AI Security Risk Assessment | Threat modeling, prompt injection testing and agent permission review, mapped to the OWASP Top 10 for LLM Applications and MITRE ATLAS | Firms running agents or AI features with production access |
| Application Assessment | Security testing of your applications, including the third-party scripts and AI features they load | SaaS companies that learned from Optimizely that a vendor can become the attack path |
| ISO/IEC 42001 Control Gap Assessment | A two-week gap analysis with a prioritized roadmap | Organizations preparing for certification or a customer audit |
| ISO/IEC 42001 implementation | A full AI management system built to produce audit evidence, integrated with ISO/IEC 27001 continuity controls | Firms facing customer or regulatory AI governance deadlines |
| vCAIO / vCISO advisory | Fractional AI governance and security leadership, including NIST AI RMF advisory and tabletop exercises | Leadership teams that need an owner for AI risk without a full-time hire |
See everything on our AI governance page, or book a free 30-minute call to talk through your plan.
DISC InfoSec (Deura Information Security Consulting LLC) is a boutique AI governance and cybersecurity consultancy in Petaluma, California, serving B2B SaaS and financial services firms, and a PECB Authorized Training Partner. “DiscInfoSec” Deura holds CISSP, CISM, ISO/IEC 42001 Lead Implementer and ISO/IEC 27001 Lead Implementer credentials. Contact: info@deurainfosec.com | (707) 998-5164 | deurainfosec.com
Sources
- ABC News: Cybersecurity expert shares why people should have a “digital disaster plan” (Zach Iscol and Theresa Payton)
- ABC News: Nationwide ground stop lifted after more than 4 hours
- ABC11: FAA halts router installation following nationwide ground stop
- Good Morning America: What to know about recent tech outages (Apple statement and FAA cause reporting)
- Fortune: After a week of outages, CIOs are already preparing for the next disruption (John Kell)
- DISC InfoSec: “Cyber Attack Hits Major Websites,” our earlier post on the Optimizely compromise
- OWASP Top 10 for LLM Applications and MITRE ATLAS
Mastering Digital Preparedness: Storing ID’s, Cash, and Maps on a USB Drive
- Tech Fails Without Hackers: Your Digital Disaster Plan for the AI Era
- Question 14 Is Stalling Your Enterprise Deals
- Before You Govern the World, Examine What Governs Your Mind
- Your Agents Already Have Keys. Do You Know Which Doors They Open?
- 178 Brands. Zero Breaches of Their Own. One Trusted Script


























