Seven Dependent Business Interruption Gaps That Leave Supplier Outages Uninsured
Your cyber policy may pay when your own network goes down but not when your cloud host, MSP or payroll provider does. Seven wording gaps to find, and the endorsement language to ask for.
Why supplier outages are where cyber claims get disputed
When an outage starts at your cloud host, managed service provider or payroll processor instead of on your own network, the claim rests on one part of the policy: dependent business interruption cyber insurance, which some markets call contingent business interruption. Many buyers learn mid-claim that this cover is narrower than they assumed. It may have a smaller limit, a longer wait before it pays, or a trigger that doesn't match what actually happened.
The cover itself is usually there. Many mid-market cyber policies written in London, continental Europe, Singapore, the Gulf and North America include some form of it. The problem is the wording: which suppliers count, what kind of event qualifies, and how much the insurer pays.
Below are seven gaps that recur in renewal reviews, each with the endorsement wording or risk fix to ask your broker for. Before you start, pull your current policy wording, the declarations page and your supplier list. Most of these gaps only show when you read all three together.
Mistake one: accepting a named-provider schedule that misses half your stack
Some policies cover dependent BI only for providers on a schedule. That works only if the list is complete, and it rarely is. Finance teams tend to list the big cloud platform and the ERP vendor, then forget the payroll bureau, the logistics provider's warehouse system, the payment gateway and the MSP that holds admin credentials for everything.
Red flag: wording like "Dependent Business means only those entities scheduled in Endorsement X."
What to do instead: ask for unscheduled cover, meaning any entity you depend on under a written contract to provide services. If the insurer insists on a schedule, build it from accounts-payable data, not memory. Say a 120-person distributor pulls 12 months of AP and finds 30-plus vendors that touch operations (a hypothetical figure). Those are the names to check against the schedule. Also ask for a clause that automatically covers new providers for a set period, often 60 to 90 days, until they can be added.
Mistake two: assuming system failure coverage extends to your suppliers
Many supplier outages aren't attacks. A botched update, a configuration error or a failed data-center migration can take a provider offline just as completely as ransomware. Many policies now include system failure coverage for your own systems but limit dependent BI to a "security failure" or "cyber event" at the provider.
Red flag: the dependent BI insuring clause refers only to "Security Breach" or "Cyber Attack," while the first-party BI clause uses a broader "System Failure" definition.
What to do instead: ask for dependent system failure cover: unintentional, unplanned outages at a provider, added by endorsement. Expect a lower sublimit or longer waiting period for non-malicious events. Accept that trade. For most organizations, an accidental outage at one cloud region or SaaS platform is likelier than a targeted attack on that provider.
Mistake three: ignoring how the cyber waiting period interacts with short outages
The cyber waiting period is a time deductible: loss in the first hours of an outage isn't covered. On first-party BI it commonly runs from a few hours to around 12. On dependent BI it's often longer, sometimes 24 hours or more. Most supplier outages are fixed within a day, so a long waiting period can mean the cover never pays for the outages you're most likely to have.
Red flag: a dependent waiting period well beyond the first-party one, or wording that starts the clock when the provider confirms the incident instead of when your operations are actually affected.
What to do instead: ask for the same waiting period on dependent and first-party BI, with the clock starting at the first interruption of your operations. If the insurer won't move, request a quote for a shorter period. Cutting the wait usually costs a modest premium increase, and it's better value than a higher limit you'll rarely reach.
Mistake four: treating a sublimit as if it were the full limit
Dependent BI is often sublimited to a fraction of the aggregate limit. A US$5 million policy with a US$500,000 dependent sublimit looks solid on the summary page. It looks very different when an e-commerce business loses its hosting platform for three days at quarter-end.
| Typical structure | Indicative range | Who it suits |
|---|---|---|
| Low sublimit | Roughly 10%–25% of aggregate | Firms with on-premises redundancy and few critical suppliers |
| Mid sublimit | Roughly 25%–50% of aggregate | Most SaaS-heavy mid-market companies |
| Full limit | Up to 100% of aggregate | Online-revenue businesses with single points of failure |
What to do instead: size your actual exposure. Take gross profit per day lost when your most critical provider is down and multiply by a realistic outage of three to five days. Ask for a sublimit that covers that number. These are indicative 2026 market ranges that vary by insurer, region and contract, so confirm terms with your broker.
Mistake five: letting "IT provider" exclude your payroll and logistics partners
Some wordings define the dependent business as an "IT Provider" that hosts, processes or maintains your data. Under that definition, a payroll bureau or a freight forwarder whose booking system fails may not qualify, even though the outage stops your operations. The contingent business interruption cyber trigger then fails on a definition.
Red flag: a definition limited to "outsourced IT services," with no mention of business-process or supply-chain providers.
What to do instead: ask for a two-tier definition. The first tier covers IT providers. The second, often called "non-IT providers" or "supply chain," covers any provider of goods or services whose computer system fails. Insurers usually attach a smaller sublimit to the second tier, which is reasonable. For manufacturers and distributors in Southeast Asia, India and Latin America that rely on outsourced logistics, the second tier is often the more important one.
Mistake six: missing the infrastructure and widespread-event exclusions
A broad dependent BI grant can be undone by exclusions elsewhere in the policy. Two matter most: the infrastructure exclusion, which typically covers power, telecoms, internet backbone and DNS, and the widespread or systemic event exclusion. Lloyd's state-backed cyber attack requirements and similar language in other markets can also narrow cover when a large event hits many policyholders at once.
Red flag: exclusion wording that treats "cloud service providers" as infrastructure, or a catastrophe exclusion with no carve-back for your contracted providers.
What to do instead: ask for a carve-back stating that your contracted cloud and SaaS providers are not infrastructure. Ask how the insurer would treat an outage at a single major hyperscaler region, and get the answer in writing before you bind. Regulated firms should also map this against their resilience obligations, such as DORA in the EU or outsourcing guidance from regulators like MAS in Singapore or the RBI in India. There, a coverage gap becomes a governance problem too.
Mistake seven: a restoration period that ends before your business recovers
Many policies end the indemnity period when the provider restores service. Your revenue doesn't bounce back that hour. Orders pile up, customers go elsewhere, and staff reconcile data by hand. The cloud outage insurance coverage you bought then pays for the outage but not the recovery.
What to do instead: ask for an extended period of indemnity after restoration (often 30 to 120 days is negotiable), plus extra-expense cover for workarounds such as manual payroll runs or temporary hosting. Pair that with risk fixes: contractual exit plans, secondary payroll arrangements and multi-region hosting all reduce loss and strengthen your submission.
| Gap | Ask for |
|---|---|
| Named-provider schedule | Unscheduled cover plus 60–90 day auto-add |
| Security-only trigger | Dependent system failure endorsement |
| Long waiting period | Parity with first-party; clock starts at your interruption |
| Low sublimit | Sublimit sized to 3–5 days' gross profit |
| IT-only definition | Non-IT/supply-chain tier |
| Infrastructure exclusion | Carve-back for contracted cloud/SaaS |
| Restoration ends early | Extended indemnity period plus extra expense |
Next step: send this table to your broker at least 90 days before renewal and ask for a clause-by-clause comparison from at least two markets. A licensed broker or coverage counsel should confirm how each wording would respond before you bind.
Quick answers
Is dependent business interruption the same as contingent business interruption?
In cyber policies the two terms are generally used interchangeably. Both describe loss from an outage at a third party you rely on, not on your own systems. Property policies use "contingent BI" differently, for physical damage at a supplier, so confirm which policy and which trigger your broker means.
How much does broader dependent BI cover typically add to premium?
It varies widely by insurer, region, revenue and controls. Raising a dependent sublimit or adding non-malicious system failure cover typically adds a modest percentage to the cyber premium, though some markets price these extensions far more aggressively than others. Ask your broker for quotes on several structures and confirm current pricing.
Will my cyber policy pay if a major cloud provider has a global outage?
It depends on three things: whether the outage was malicious or accidental, whether the policy covers dependent system failure, and how its widespread-event and infrastructure exclusions are worded. Some wordings would respond and others wouldn't. Ask your insurer to confirm in writing how it would treat a single-provider cloud outage, and have a licensed broker review the answer.
Written by the Breach Underwrite Group editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.