
Your Vendors Will Be Breached. Your Readiness Is the Variable.
Lessons from the Canvas breach 2026: why vendor concentration risk and tabletop exercise frequency are the real story.
Instructure paid the ransom.
On May 11, 2026, the parent company of Canvas confirmed it reached an "agreement" with the ShinyHunters extortion crew after the group exfiltrated 3.65 terabytes of data covering roughly 275 million records and nearly 9,000 institutions. A 24-hour deadline. A wire transfer to extortionists. Instructure took the deal. (Coverage of the incident: The Hacker News.)
If you read that and thought "good thing I'm not in higher ed," you're missing the lesson. Swap "Canvas" for your industry's equivalent — an EHR in healthcare, an ERP in manufacturing, a payroll platform in HR, a core banking system in financial services, a CRM in revenue ops, an MSP in mid-market — and the story is identical. If you are a CISO, CIO, VP of IT, or Director of Security in any sector, this is your problem now.
"While there is never complete certainty when dealing with cyber criminals, we believe it was important to take every step within our control..." — Instructure, May 12, 2026
Translation: we had no leverage, no time, and no real options. So we paid. The lesson for the rest of us is not "pay the ransom." The lesson is: never be in that position to begin with.
Vendor Concentration Risk Is a Permanent Feature of Modern IT
It's tempting to look at the Canvas breach and conclude the answer is to undo three decades of consolidation. Spin everything back out to departments. Run your own infrastructure. Decentralize the data.
Let's be honest: centralization is not going anywhere. The economics are too strong. The compliance burden of doing it yourself is too high. The talent shortage is too real. Boards have already approved the multi-year SaaS migrations. CIOs who tell their executive committees "we should rebuild this in-house" do not get a second meeting.

And the centralized model genuinely delivers value. Standardized data. Real analytics. Reduced redundant spend. Anyone who lived through the 1990s' "every department has its own little Access database" era doesn't actually want to go back.
Centralization is the deal we've made. The question isn't whether to undo it. The question is whether we're rehearsed for the day it fails.
Concentration risk is not a problem to be eliminated. Like supply-chain risk for a manufacturer or counterparty risk for a bank, it's a permanent feature to be measured, stress-tested, and rehearsed for. (TechTarget made a similar point following the recent AWS outage: rehearse and practice using tabletop exercises for the next unanticipated event that disrupts a critical business system.)
The 24-Hour Vendor Breach Response Timeline
When a vendor breach lands on your desk, the clock starts immediately — and every hour you're not rehearsed costs you optionality. By T+24 hours, the choices have been made for you. The picture below is what most security leaders only see clearly after they've lived through it once.

None of the right-column behaviors come from a runbook nobody has practiced. They come from teams that have already run this exercise — multiple times.
Why Annual Tabletop Exercise Frequency Is No Longer Enough
Most security frameworks recommend quarterly tabletop exercises, but most organizations still run only one a year. Some run two. A handful of mature programs run four. The problem isn't that these exercises are bad — it's that the threat landscape moves at the speed of ShinyHunters, Scattered Spider, and a dozen others, while your team's preparedness quietly decays between sessions.

Annual tabletops are not enough. They have not been enough for years. Canvas proved it. Change Healthcare proved it. MOVEit proved it. MGM proved it. Every major incident in the last 24 months has been, in part, a failure of rehearsal — across every industry.
AI-Powered Tabletop Exercises: How Continuous Rehearsal Actually Works
AI agents can now generate cybersecurity tabletop exercise scenarios tailored to your specific environment, your specific vendors, and your specific industry threats — and run them with your teams on demand. The platform plays adversary, vendor, regulator, and press, pivoting in real time as your team makes decisions. Five stages, one afternoon, board-ready output.

If your adversary uses AI to compress attacks into hours, your defense must use AI to compress preparedness into weeks.
This is what "managing vendor concentration risk" looks like in practice. Not a five-year migration plan. Not a decentralization initiative your board will never approve. A regular drill that surfaces real gaps and produces real remediation work, scoped to the vendors you actually depend on.
What CISOs Should Do This Quarter
Five things you can do in the next ninety days that materially shift your organization's readiness — regardless of industry:
- Run a vendor-failure tabletop exercise. Your largest SaaS vendor pays a ransom without consulting you. You find out via press release. Who owns the response? If your team can't answer in 30 minutes, you have your answer.
- Quantify your vendor concentration risk. How many critical operations live with a single vendor? How many business units could operate for 72 hours if that vendor went dark? Put numbers on it. That's your board slide.
- Shorten your tabletop exercise cadence. Quarterly is the floor. Monthly is the goal. Continuous is where you're heading. AI tabletop exercise platforms make this an operational decision, not a budget one.
- Test the people, not the plan. Plans are fiction until they survive contact with a tired analyst at 11:47 PM on a Friday. Build exercises that stress humans, not paragraphs.
- Make rehearsal the answer to the board's vendor-risk question. Next time someone asks "what are we doing about our dependency on [critical vendor]?" — answer with a cadence, a coverage matrix, and a trend line on response times. Not an RFP that won't ship for three years.
Frequently Asked Questions
What is vendor concentration risk in cybersecurity?
Vendor concentration risk refers to the cybersecurity exposure created when an organization depends heavily on a single SaaS vendor, cloud provider, or service partner for critical operations. When that vendor experiences a breach, outage, or ransomware incident, every downstream customer is affected simultaneously. The Canvas breach of 2026 — which impacted nearly 9,000 institutions through a single Instructure vulnerability — is a textbook example. Concentration risk cannot be eliminated in most modern enterprises, but it can be measured, rehearsed for, and mitigated through continuous incident response preparation.
How often should you run a cybersecurity tabletop exercise?
Most security frameworks recommend tabletop exercises at least quarterly, though high-risk industries and organizations undergoing significant change benefit from more frequent drills. Annual exercises — historically the default — are widely recognized as insufficient given the speed of the modern threat landscape. The practical target is quarterly as a floor, monthly for higher-risk functions like the SOC and IR team, and continuous (weekly drills via AI-powered platforms) for organizations with high vendor concentration risk. Cadence matters more than length: shorter, more frequent exercises build durable muscle memory in a way annual half-day workshops cannot.
What is an AI-powered tabletop exercise?
An AI-powered tabletop exercise uses generative AI agents to create scenarios, play adversary roles, and adapt the exercise in real time based on participant decisions. Unlike traditional consultant-led tabletops — which rely on pre-written scenarios and human facilitators — AI-driven platforms can generate fresh scenarios from live threat intelligence, run multiple functions in parallel (IR, SOC, exec, legal, comms), and produce after-action reports in hours instead of weeks. This makes continuous rehearsal operationally and economically feasible for security teams that previously could only afford one or two exercises per year.
What was the Canvas breach of 2026?
In April and May 2026, the ShinyHunters extortion group breached Instructure's Canvas learning management platform, exfiltrating approximately 3.65 terabytes of data — roughly 275 million records covering usernames, email addresses, course names, enrollment information, and messages — from nearly 9,000 schools and universities. After defacing login portals at around 330 institutions and issuing a 24-hour ransom deadline, Instructure announced on May 11, 2026 that it had reached an "agreement" with the attackers, in what is widely seen as a precedent-setting vendor ransom payment affecting an entire downstream customer base.
What should organizations include in a vendor-failure tabletop exercise?
A robust vendor-failure tabletop exercise should test: (1) initial detection and confirmation that a vendor incident actually affects you; (2) decision authority and escalation paths when the vendor is your single source of truth; (3) communications across customers, employees, regulators, board, and press; (4) downstream operational continuity for affected business units; (5) regulatory notification timelines under relevant regimes like GDPR, HIPAA, SEC cyber disclosure rules, or DORA; and (6) post-incident lessons-learned workflow. The most realistic scenarios involve the vendor making decisions you wouldn't have made — including paying a ransom — without consulting you.
How is a ChaosTrack exercise different from a traditional tabletop?
Traditional cybersecurity tabletop exercises typically take weeks of preparation, involve a consultant-led facilitation session, and produce a written after-action report days or weeks later. ChaosTrack's AI-powered platform compresses this into a single afternoon: scenarios are generated from live threat intelligence and tailored to your environment and vendors; the AI plays adversary, vendor, regulator, and press in real time; every participant decision is captured and measured; and the after-action report is delivered in hours, mapped to controls and pre-drafted remediation tickets. This shifts tabletop exercises from an annual budget item to a continuous operational practice.
The Bottom Line
Instructure made a calculation. The downstream institutions had no calculation to make. They were spectators to a decision that affected their students, their staff, their reputations, their compliance obligations. That dynamic is going to repeat itself across every industry, with every major vendor. It's the cost of the centralized model we've collectively chosen.
You don't get to opt out of that reality. You do get to decide whether your organization is rehearsed for it.
The attackers are not slowing down. The vendors are not getting safer. The bureaucracy is not getting faster on its own.
But your readiness can. Start this quarter. Your future self — the one not on a 2 AM bridge call with extortionists — will thank you.
Stop running tabletop theater. Start running tabletop reps.
See how ChaosTrack runs continuous AI-powered tabletop exercises for security teams who can't afford to rehearse just once a year.
As a founder building in this space, I'm not neutral about the value of continuous, AI-driven preparedness. But the gap exposed by the Canvas breach is real, and it's the same gap across every industry that depends on centralized platforms — which is to say, all of them.