One mistake in your stack reaches every client at once.
Cover for MSPs and IT service providers — where an error, or a compromise of your own tooling, aggregates across the whole client base rather than affecting one of them.
Tell us the situation.
A licensed human replies the same business day — not an auto-responder, and not five producers calling at once. We shop it across our carriers and tell you if the policy you already have is the right one.
We use this to quote and service your insurance, and we do not sell it or pass it to lead networks. Privacy policy.
What MSP businesses actually need.
Technology E&O
A configuration, migration or recommendation that cost a client money.
Without it — The routine claim against an MSP and not a cyber claim.
Cyber liability, first and third party
Your own breach, and liability for client environments you administer.
Without it — An MSP holds privileged access to every client network it manages.
Aggregation exposure
Limits set against a supply-chain event hitting many clients simultaneously.
Without it — A per-claim limit sized for one client is exhausted by the first ten.
Contingent business interruption
Loss when a vendor or platform you depend on goes down.
Without it — A tool in your stack failing stops your service to everyone.
Contractual requirements
The limits and additional insured wording client MSAs demand.
Without it — Enterprise clients will not sign without evidence.
What MSP operators ask us.
What is the aggregation problem?
That MSP losses are not one client at a time. Your RMM, your backup platform, your credential store and your privileged access reach every client you serve, so a compromise or a bad push is a simultaneous event across the whole book — and the supply-chain attacks of recent years targeted exactly that. It means the limit has to be sized against the portfolio rather than the largest client, which is a different and larger number than most MSPs first buy.
Our clients ask us to sign security commitments. Does insurance cover those?
Only up to a point, and the assumed obligations are where MSPs get hurt. Contractual liability cover generally responds to liability you would have had anyway, not to obligations you took on voluntarily — so promising uptime, a recovery time objective, or to indemnify a client for any breach can create exposure the policy does not follow. Have the MSA reviewed against the policy before signing, not after a claim reveals the gap.
Do we need cover for our clients’ breaches?
You need cover for your LIABILITY arising from them, which is the part MSPs underestimate. When a client is breached, the first question is whether the provider managing their security should have prevented it — patching, MFA, backup integrity, alert response. That claim is against you, it blends E&O and cyber, and it is much easier to handle when one insurer holds both rather than two disputing which policy is on the hook.
Not ready to talk? The guides answer the questions this page raises in more depth. Already insured with us and need a certificate or a policy change? Ask the service team rather than starting a quote — it is faster and it goes to the people whose job it is. We also write home and auto, which is usually cheaper alongside the business policy than apart from it.