Why one RMM compromise strains standard MSP cover
If an attacker gets into your remote monitoring and management (RMM) console, they don't stop at one company. They can push ransomware to every endpoint you manage. Then the claims arrive. Clients want compensation for revenue lost during downtime. Their insurers try to recover what they paid. In some countries, regulators ask why personal data was exposed. For many MSPs, this is the first time they read their MSP professional liability insurance wording closely.
The seven gaps below recur in supply-chain incidents. Each comes with a fix. Some fixes are policy wording; others are client-contract terms. Raise them at renewal, while you still have leverage. Policy forms differ a lot between the London, EU, US, Indian, Singapore and Australian markets, so test this list with a broker who places tech E&O for MSPs every week, not once a year.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Gap one: cyber and E&O bought from different carriers
Red flag: your managed service provider insurance is a tech E&O policy from one carrier and a standalone cyber policy from another.
An RMM-borne attack triggers both kinds of cover at once. Your own incident response, downtime and extortion costs fall under first-party cyber. Client claims fall under third-party E&O or network security liability. If both policies include a network security liability grant and both carry "other insurance" clauses, each carrier can argue the loss belongs to the other, while your defense costs pile up. Some E&O forms also exclude security events outright, assuming you bought cyber elsewhere.
Do instead: for most smaller and mid-size MSPs, a combined tech E&O and cyber form from one carrier, handled by one claims team, is the better choice because it removes the dispute over which policy pays. If you must split the cover, get written confirmation of which policy is primary, and keep the network security liability grant in only one of them.
Gap two: the contractual liability exclusion swallows your MSA
Almost every form has a contractual liability exclusion. It removes liability you assumed by contract unless you would have owed it anyway under general law. Now read your master services agreement. If it promises to indemnify clients for "any loss arising from a security incident", or offers uncapped liability, liquidated damages or service credits, the part beyond what the law would impose may be uninsured. Fee refunds and service credits are excluded under most forms whatever the contract says.
Do instead, on the policy: ask for a carve-back covering contractual indemnities for breach of confidentiality and network security failures. Some carriers offer this by endorsement, sometimes for extra premium.
Do instead, on the contract:
- Cap aggregate liability at a multiple of fees (12 months' fees is common) or at your insurance limits, whichever is lower.
- Limit indemnities to third-party claims and exclude indirect or consequential loss where local law permits.
- Require clients to keep their own cyber cover and to waive subrogation against you where their policy allows it.
Enforceability of caps varies. UK reasonableness tests, civil-law limits on excluding gross negligence, and consumer-protection rules all differ, so have a local commercial lawyer review your template.
Gap three: limits sized for one client, not forty
Most MSP forms include a related-claims clause, which bundles claims from the same event into one claim. You pay one retention instead of 20. But one per-claim limit now has to cover every affected client.
Hypothetical: say a 25-person MSP with 60 clients carries $1M per claim and $1M aggregate, with defense costs inside the limit. An RMM compromise encrypts 18 clients, and each claims $80k to $400k. The demands far exceed $1M, and legal fees come out of the same pot. Whatever is left is uninsured and lands on the owners.
| Limit structure | What happens in a multi-client event | Indicative annual premium (MSP, $2M–$5M revenue) |
|---|---|---|
| $1M / $1M, defense inside limits | Defense costs reduce the money available for settlements | $5,000–$12,000 |
| $2M / $2M, defense outside limits | Settlement capacity is protected from legal fees | $10,000–$25,000 |
| $1M primary + $4M follow-form excess | Broader capacity, provided the excess truly follows the primary wording | $18,000–$45,000 |
These are typical 2026 market ranges and vary by country, controls and claims history. Confirm with carriers. A simple sizing rule: estimate how many clients one RMM tenant can reach, multiply by a realistic per-client loss, and buy limits near that number.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Gap four: rebuilding client systems before anyone sues
In the first 72 hours your technicians will rebuild client environments around the clock, and you may hire outside forensics firms for client networks. First-party cyber covers your systems. E&O pays only once a claim has been made. Voluntary work on clients' systems falls between the two, and costs can reach six figures before anyone sends a demand letter.
Do instead: ask for a mitigation-costs or pre-claim remediation extension covering costs to prevent or reduce a likely third-party claim. Sublimits in the low-to-mid six figures are common, though they vary. Ask also whether replacing damaged client hardware is covered. Get carrier consent before you spend; unapproved costs are routinely declined.
Gap five: exclusions for vendor flaws and control warranties
Supply-chain incidents such as the 2021 Kaseya VSA attack showed that the weak point can sit in the RMM software itself rather than in anything the MSP configured. Some forms exclude failures of third-party software or "infrastructure" broadly enough to catch your own tooling.
Do instead: narrow any infrastructure exclusion to utilities, power and telecom providers. Confirm that network security liability responds whether or not the vulnerability was in code you wrote.
The other half of this gap is the proposal form. If you stated that MFA is enforced on every RMM, PSA and privileged account, and a legacy admin login turns out not to have it, the carrier may allege misrepresentation or apply a ransomware sublimit or coinsurance. Answer precisely and disclose known exceptions in writing. Ask for severability and innocent non-disclosure wording, which is standard in some markets and negotiable in others.
Gap six: territory and regulatory cover built for one country
Your clients may operate under GDPR, UK GDPR, India's DPDP Act, Brazil's LGPD, Singapore's PDPA or Gulf data protection laws. Under several of these regimes, an MSP acting as a processor carries direct obligations. Many policies grant worldwide territory but restrict jurisdiction, for example by excluding suits filed in the US or Canada unless endorsed.
Do instead: request worldwide territory and jurisdiction, regulatory defense costs, and fines and penalties "where insurable by law". Some countries don't allow fines to be insured, so expect cover to vary by client location.
Gap seven: losing control of notice, retro dates and settlement
MSP cyber and E&O policies are almost always claims-made. That creates three risks. You can report late. You can lose prior-acts cover when you change carriers. And a hammer clause can push you toward a settlement you'd rather fight. Under a typical 50/50 hammer clause, if you reject a settlement the carrier recommends, you bear half of the costs above that figure.
Do instead:
- Give notice of circumstances at the first RMM anomaly, not when the first client writes to you.
- Keep your original retroactive date, or full prior acts, whenever you change carriers.
- Negotiate the hammer clause toward 70/30 or 80/20 in your favor.
- Pre-approve your preferred breach counsel and forensics firm if they aren't on the carrier's panel.
Next step: about 90 days before renewal, send your broker your MSA template and this list. Ask for a written gap analysis mapping every client indemnity to a policy clause. If a promise in your contract has no matching cover, buy the cover or remove the promise.