Auditinsure DirectEnterprise Underwriting Intelligence
Claims & Coverage

Tech E&O vs Cyber Insurance: Which Policy Pays When a Client Sues Over a Breach?

A client sues after a breach, and your E&O and cyber insurers each point at the other. Four claim scenarios, where the gaps sit, and which structure to buy.

By the Auditinsure Direct editorial team · November 2026 · 11 min read

The renewal question: which insurer pays when a client blames you for a breach

For a SaaS platform or IT services firm, the claim most likely to hurt isn't a hacker draining your bank account. It's a letter from a client's lawyer saying your product, your people or your advice caused their breach, and asking you to pay for it. Before renewal you need a clear answer to one question: which of your policies responds to that letter, and will the insurers fight over it?

Tech E&O vs cyber insurance usually gets framed as either/or. That framing is wrong. The two forms do different jobs, and they overlap exactly where client breach claims land. How you structure them decides whether a claim gets paid in weeks or stalls for months while two insurers argue over who pays what share.

Advertisement

Below, we put four claim scenarios for SaaS and IT service firms through both policy forms and flag the exclusions that drive coverage disputes. Then we give a verdict on when to buy a combined tech E&O and cyber policy, separate towers, or the professional indemnity (PI) plus cyber structure common in the UK, EU, India and Australia.

What each policy form is built to pay for

Technology errors and omissions insurance (tech E&O) is third-party liability cover. It responds when a client claims a financial loss caused by your negligent act, error or omission in delivering technology products or services, or by your product failing to perform. Think bad code, a botched migration, a missed go-live that costs the client revenue, or flawed advice.

Cyber insurance does two jobs. First-party, it pays your own costs after a security or privacy event: forensics, breach counsel, notification, data restoration, extortion and business interruption. Third-party, it covers privacy and network security liability, meaning claims that your weak security let an attack or a leak reach someone else.

Professional indemnity insurance for IT companies is what most of the world calls the E&O side. In the UK and much of the Commonwealth, PI is often written on a broad "civil liability" basis rather than negligence only. That can pick up breach of confidentiality, unintentional IP infringement and some contractual claims, and the breadth matters in scenario four.

Cover elementTech E&O / PICyber
Client sues because your service or product failedCore coverUsually not, unless a security event caused it
Client sues because data you held was exposedSometimes, depending on the cyber exclusionCore cover (privacy liability)
Your own forensics, notification, ransom, downtimeNoCore cover
Client sues over negligent security advice you gaveCore coverUsually not
Regulatory defense and finesRarelyCommonly offered, where fines are insurable by law

The overlap is the second row. That's where client breach suits live.

Scenario one: a misconfiguration in your SaaS exposes client data

Hypothetical: a 120-person HR software company pushes a configuration change that leaves a storage bucket publicly readable for nine days. Employee records from 60 client companies are exposed. Three large clients sue to recover their notification, call-center and credit-monitoring costs, plus legal fees.

Cyber carries most of this claim. It pays your incident response, your own notification obligations and your defense against the privacy liability suits. Under the EU GDPR, the UK GDPR and comparable regimes, you're typically the processor and your clients are the controllers (India's DPDP Act uses "data fiduciary" for the controller role). The clients handle their own notifications and then come to you to recover the cost.

Tech E&O may be triggered too, because the complaint will allege your software failed and your team made an error. Many E&O wordings now exclude claims "arising out of" a security or privacy event, which pushes the claim back to cyber. Others give that cover back.

Verdict: cyber leads and E&O sits behind it. If two different insurers write the policies, expect a negotiation over who pays which share of defense costs. That's manageable if the two wordings were drafted to fit together, and slow if they weren't.

Scenario two: your MSP is hit by ransomware and the attack spreads to clients

Hypothetical: attackers compromise a 35-person managed service provider's remote monitoring and management tool and use it to push ransomware into 40 client environments. The MSP's own systems are down for a week. Clients sue for downtime, recovery costs and lost revenue.

Structure decides the outcome here. Cyber pays the MSP's own response, extortion and business interruption losses, and its network security liability section responds to clients claiming the MSP's security failure caused their losses. Tech E&O responds to the parallel claim that the MSP failed to deliver the managed services it was paid for.

Three wording points decide whether that's enough:

  • Aggregation. Is one attack on 40 clients one claim or 40? Most policies treat related claims as a single claim, which means one retention but also one limit. Say each client claims $150,000. That's $6M against a $2M limit, and 30 or so clients go unpaid.
  • Widespread-event wording. Some cyber forms sublimit or exclude events that spread through shared software or infrastructure. Check how yours treats an attack routed through a third-party tool you depend on.
  • Absolute cyber exclusions on E&O. If your E&O excludes anything connected to a security event and the cyber limit runs out, the remaining client claims have no policy to go to.

MSPs should size limits against this scenario. It's the one where a single incident multiplies into dozens of claims.

Scenario three: the indemnity clause in your MSA outruns your policy

Hypothetical: a SaaS vendor has a modest breach. An enterprise client invokes the master services agreement, which commits the vendor to indemnify it for "all costs arising from any data security incident," with no cap, plus service credits for the outage.

Here the contractual liability exclusion bites. E&O and cyber forms typically exclude liability you took on by contract, except where you'd have been liable without the contract. A court might find you negligent and liable for part of the client's costs. A promise to pay "all costs" regardless of fault goes further than the law would, and that excess is often uninsured.

Carve-backs worth asking for:

  • Liability assumed under confidentiality or data protection indemnity clauses
  • Payment card industry (PCI) fines and assessments owed under a merchant agreement
  • Service credits, which most policies exclude unless you buy a specific endorsement

Regulatory fines are a separate question, because whether they can be insured at all depends on the jurisdiction. UK regulatory guidance has long treated fines as generally uninsurable on public policy grounds. EU member states and US states take differing positions, and how fines under newer regimes such as India's DPDP Act will be treated isn't settled. Policies promise cover "where insurable by law," which hands the question to local counsel.

No policy form rescues a contract that was signed without being checked against your wording. Cap indemnities at your insurance limits and get the carve-backs endorsed in writing.

Scenario four: your security advice was wrong, but your systems were never touched

Hypothetical: a 20-person IT consultancy designs a client's cloud identity setup and runs its annual penetration test. Eight months later the client is breached through a privileged account that the consultancy's design left with too many permissions. The client sues for its full breach costs.

The consultancy's own network was never compromised, and it didn't hold the stolen data. Most cyber policies define network security liability around failures of your computer systems, so cyber is unlikely to respond. This is a straight professional negligence claim, and tech E&O or PI pays. That holds only if its cyber exclusion is limited to your own systems. Wording like "any claim arising from any cyber event" wipes out cover for the very service you sell.

Security consultancies, MSSPs, pen testers and systems integrators should check this before anything else. A broad cyber exclusion on a PI policy is exactly how these firms end up uninsured for their core work.

ScenarioTech E&O / PICyberBiggest gap risk
SaaS data exposureSecondaryPrimaryAllocation between insurers
MSP ransomware spreads to clientsSharedShared, plus own lossesLimit exhaustion, aggregation
Uncapped MSA indemnityPartialPartialContractual liability exclusion
Negligent security advicePrimaryRarelyCyber exclusion on PI

Premium drivers, regional market differences and wording red flags

These are typical 2026 market ranges. They vary widely by insurer, country, controls and contract terms, so treat them as indicative only. A combined tech E&O and cyber policy with a $1M aggregate limit for a SaaS or IT firm under $5M revenue often falls somewhere around $2,500 to $15,000 a year. Firms with $5M to $50M revenue buying $5M limits commonly see roughly $15,000 to $100,000. MSPs and firms handling payment or health data price toward the top of those ranges. Separate towers for the same limits usually cost more in total. Local markets in Europe, India, the Gulf and Southeast Asia price differently, so confirm figures with your broker.

What moves the premium:

  • Revenue, and how much of it comes from large enterprise or regulated clients
  • How much client data you store or can reach, and how sensitive it is
  • Privileged access to client environments (the MSP factor)
  • Controls: MFA everywhere, EDR, tested offline backups, privileged access management
  • Contract terms: uncapped indemnities and liquidated damages push rates up or shrink insurer appetite
  • Retention: often in the $5,000 to $50,000 range for smaller firms and $50,000 to $250,000 or more for mid-size firms

Market practice also differs by region. In North America, tech E&O is commonly sold bundled with cyber. In the UK, Ireland, Australia, New Zealand, Singapore, India, South Africa and much of the EU and Middle East, client contracts often require "professional indemnity" by name, frequently at a stated amount each and every claim rather than in the aggregate. A North American-style combined form with one aggregate limit may not technically satisfy that clause.

Escalate these to your broker:

  • An absolute cyber exclusion on your E&O or PI policy
  • A shared aggregate, where one breach can erode the professional liability limit your contracts require
  • Different insurers on E&O and cyber with no agreement on which pays first
  • No cover for service credits or contractually assumed data indemnities
  • A definition of "computer system" that leaves out the cloud services or third-party tools you run on

The verdict: combined form, separate towers, or PI plus cyber

Buy a combined tech E&O and cyber form if you're a SaaS or IT services firm under roughly $50M revenue, your contracts ask for limits up to about $5M to $10M, and none of them demand professional liability on an each-and-every-claim basis. One insurer, one claims team and one wording removes the allocation fight in scenarios one and two, and it's usually the cheapest route. Its weakness is the shared aggregate. Close it by asking for separate aggregates for the E&O and cyber sections, which some specialist insurers offer, or by buying excess limits.

Move to separate towers once you need more than about $10M in total limits, sell to enterprises or public bodies that specify dedicated E&O limits, or find the cyber market prices your risk better on its own. Put the same insurer at the lead of both towers where you can, since it shortens any argument over which policy pays first. Either way, align the cyber exclusions so every scenario above lands in at least one policy, and get the order of payment agreed in writing.

Choose PI plus standalone cyber if you trade mainly in the UK, EU, India, Australia, Singapore or the Gulf, or if your client contracts name professional indemnity at an each-and-every-claim limit. It's also the right fit for consultancies, integrators and security advisers whose largest exposure is scenario four. Insist on civil liability wording and a cyber exclusion that applies only to your own systems.

Next step: send your three largest client contracts and your current wordings to your broker. Ask for a written map showing which policy clause responds to each of the four scenarios. Treat any scenario they can't map as uninsured until it's fixed. Coverage decisions belong with a licensed broker and, where contracts or fines are involved, local counsel.

Quick answers

Do I need both tech E&O and cyber insurance if I run a SaaS company?

In most cases, yes. Cyber pays your own breach costs and covers privacy liability. Tech E&O covers client losses when your product fails or your team makes an error. For smaller firms, a combined form that provides both in one policy is usually the simplest and cheapest option.

Will my cyber policy cover a client who sues me after they were breached?

Usually only if the breach involved your systems or data you held. If the client was breached in its own environment and blames your advice or configuration work, that's normally a professional negligence claim for tech E&O or PI. Make sure your E&O or PI doesn't carry a broad cyber exclusion that blocks it.

What is the contractual liability exclusion and why does it matter?

It removes cover for liability you took on by contract beyond what you'd owe at law anyway. Uncapped indemnities or "all costs" clauses in client agreements can leave a large uninsured gap. Ask for carve-backs for data protection indemnities, and cap contractual indemnities at your policy limits.

Is a combined tech E&O and cyber policy acceptable to clients that require professional indemnity insurance?

Not always. Contracts in the UK, Australia, India and elsewhere often require PI at a stated limit each and every claim, and a combined form with one shared aggregate may not meet that wording. Show the clause to your broker and get written confirmation before you sign.

Are regulatory fines for a data breach covered?

Many cyber policies cover fines and penalties "where insurable by law," but whether a given fine is insurable depends on the jurisdiction and the type of fine. Positions differ across the UK, EU member states and US states, and treatment under newer regimes such as India's DPDP Act is unsettled. Take advice from a licensed broker and local counsel in each country where you operate.

How much limit should an IT services firm or MSP buy?

Start with the highest limit your client contracts require. Then test it against one incident hitting many clients at once, which is the realistic worst case for an MSP. Limits of $2M to $10M are common for firms under $50M revenue, but the right figure depends on your contracts, data volumes and client concentration.

Written by the Auditinsure Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.