Summarize with AI
Open this article in your favorite AI assistant for a quick summary.
When Vendors Fail, MSPs Absorb the Risk: Rethinking Cyber Risk in Managed Services
When a major technology vendor suffers an outage or security incident, the impact rarely stops with the vendor. For managed service providers, it often lands directly on their desks. MSPs become the ones explaining the disruption to customers, managing workarounds and absorbing the fallout, even when they had no control over what went wrong.
A recent cluster of incidents illustrates the point. An N-central service disruption, a ScreenConnect vulnerability, a Microsoft 365 outage and an FAA outage unfolded in quick succession. Each raised different questions, but together they exposed a structural feature of managed services and cyber risk: MSPs are accountable to their customers for services that depend on vendors they do not control.
The MSP is in the middle
Customers engage an MSP to keep their IT running, and few distinguish the MSP’s responsibilities from those of the cloud, remote-access or security vendors behind the service. When a vendor’s product goes offline, the MSP still has to communicate with customers, manage workarounds and protect the relationship.
The Microsoft 365 outage also exposed a practical gap in many incident response plans: what happens when email, the usual channel between an MSP and its customers, is itself unavailable? Restoration can bring its own risk as well, as phishing attempts may follow once service returns. An out-of-band communication plan, established before an incident occurs, gives MSPs a way to reach customers when primary channels fail.
Who carries vendor risk?
The core dilemma can be described as “oversight without control.” MSPs deploy vendors’ tools into customer environments, and those tools often carry broad privileges. Yet vendors frequently limit their own liability, while customers look to the MSP when something goes wrong.
The result is a concentration of reputational and operational risk on MSPs, risk they did not create. That raises several open questions for the industry. Should vendor oversight become a defined component of managed services? Should customer agreements more clearly separate MSP-controlled systems from vendor-controlled ones? And will cyber insurers begin to scrutinize the vendors MSPs rely on more closely?
The “kill switch” question
One proposed response is a “kill switch”: a way for MSPs to quickly disable a vulnerable tool across customer environments. Such a capability would give MSPs more control over when action is taken during an incident.
But a kill switch would introduce risks of its own. MSPs would need clear criteria for when it can be used and a continuity plan for customers if a critical tool is shut off. It is a question the profession needs to debate, not a simple fix.
MSPs need a voice in what comes next
These incidents showed MSPs responding under real-world pressure, often on behalf of customers affected by events outside the MSP’s control. That frontline experience gives the profession a strong case for helping shape the policies, agreements and industry practices that follow.
The larger question is not simply how MSPs respond to the next outage. It is how responsibility should be shared across the technology supply chain, and how MSPs can protect their customers without being left to carry risks they cannot control.