If You Pull the Plug Yourself, Will Your Cyber Policy Pay for the Downtime?
Taking systems offline to contain an attack can be the right call and still leave your downtime uninsured. Here's which clauses decide it, how the waiting period runs, and what to add before you bind.
The trigger wording that decides whether a deliberate outage is covered
Your security team spots ransomware moving sideways at 2 a.m. and recommends shutting down the ERP, the warehouse system and the customer portal before encryption spreads. That's usually the right technical call. Whether your cyber policy pays for the lost revenue that follows is a separate question, and the answer sits in one short definition: what counts as an interruption.
Most cyber business interruption sections pay only when the interruption is caused by a defined event, typically a "security failure" or "network security breach," and sometimes a "system failure." A strictly worded policy lets the insurer argue that the attacker didn't take your systems down. You did. If nothing had been encrypted yet, the insurer may say the loss came from a business decision, not from the covered event.
Voluntary shutdown coverage closes that gap. It's language, either inside the main BI definition or added by endorsement, saying a shutdown you start on purpose to limit a covered event's impact counts as an interruption. Many mainstream cyber forms include it in some shape. Plenty don't, and the versions vary widely. Don't assume you have it. Find the wording.
Voluntary, precautionary and regulator-ordered shutdowns compared
Shutdowns fall into three groups, and wordings treat each differently. The table shows common market patterns, not any one insurer's form.
| Shutdown type | Typical scenario | How wordings commonly treat it | What to look for |
|---|---|---|---|
| Voluntary (in response to a confirmed event) | Ransomware found on two servers; you isolate the whole network | Covered where a voluntary shutdown clause exists; disputed where cover needs the event itself to cause the outage | Express wording that a shutdown "to mitigate" a covered event is an interruption |
| Precautionary (suspected but unconfirmed event) | A supplier is breached and you cut your VPN link to it as a precaution | Often excluded or limited, because nothing has happened to your systems yet | Whether a "reasonable belief" of a security failure is enough, and whether advice from the insurer's breach panel counts |
| Regulator- or authority-ordered | A financial, health or data-protection regulator orders processing suspended pending review | Frequently excluded under "governmental action" or "order of civil authority" language; sometimes carved back in | Whether the exclusion has a carve-back for orders that follow a covered cyber event |
The precautionary shutdown is the hardest of the three to claim. There's no confirmed compromise, the adjuster sees an outage you chose, and the policy may require a security failure to have "occurred." Wordings that accept a shutdown on reasonable belief of an event, or on the recommendation of the insurer's approved incident response firm, are worth a lot here.
Regulator-ordered shutdowns differ by country. Under the GDPR, EU and UK supervisory authorities can order a temporary or permanent limit on processing. Sector regulators in India, Singapore, the Gulf states and Latin America have their own powers over banks, insurers, payment firms and healthcare providers. A policy built around one jurisdiction's regime doesn't always fit a group operating in five. Check that the carve-back is broad enough to cover the authorities that actually regulate you.
When the cyber business interruption waiting period starts
Even after the shutdown is accepted as covered, a time-based retention applies before the policy pays. Waiting periods commonly run from a few hours to a day, and roughly 8 to 12 hours is typical for mid-market buyers. Larger risks sometimes accept longer periods to bring premium down.
The start time matters more than the length. Wordings use different anchors:
- When the interruption begins (most favorable to you, provided a voluntary shutdown counts as an interruption)
- When the security failure is first discovered
- When the security failure first occurred, which can predate discovery by weeks and work against you
- When the insurer is notified
Also check whether the waiting period is a straight time deductible or a qualifying period. With a time deductible you absorb the first 10 hours and the insurer pays from hour 11. With a qualifying period, once the outage passes 10 hours some policies pay from hour zero. That difference can matter more than the length.
Hypothetical worked example: Say a 150-person distributor earns about $60 million a year with a 30% gross margin, roughly $2,000 of gross profit per hour on a 24/7 order cycle. It shuts down for 72 hours under a 12-hour time deductible. The first 12 hours, about $24,000, stay with the company. If the clock starts at discovery and discovery came six hours before the shutdown, part of the deductible may already have run before you went offline, so the uninsured downtime shrinks. If the clock runs from first compromise, the waiting period may have expired before anyone knew there was a problem. That helps on the deductible but invites arguments over when the loss began.
Proving the loss after you chose to go offline
BI claims are proven with numbers. A voluntary outage adds one more thing to prove: that the shutdown was reasonable and proportionate to the threat. Expect the adjuster to ask why you shut down everything instead of one segment, and why systems stayed down as long as they did.
Build the record while the incident is still running:
- Keep a timestamped log of who ordered each shutdown and the technical reason given.
- Get written recommendations from your incident response firm, ideally one on the insurer's panel, before or right after isolating systems.
- Notify the insurer as soon as possible. Many wordings expect notice before or right after a voluntary shutdown, and late notice hands the insurer a separate defense.
- Record when each system was cleared to return and why restoration took as long as it did.
- Pull baseline revenue and margin data for comparable periods so seasonality can't be used against you.
Look at the period of restoration as well. Many policies cap indemnity at a set number of days and stop once systems are restored "with reasonable speed." An extended period of indemnity pays for lost customers after systems come back, typically for a further 30 to 90 days if purchased. Also confirm the policy pays forensic accountants to prepare the claim. A well-run BI claim can cost tens of thousands of dollars to put together.
Red flags in system failure and shutdown wordings
System failure coverage is related but separate. It responds to non-malicious outages such as a bad patch, an operator error or a failed update. Some insurers include it in full, some sublimit it heavily, and some leave it out. A precautionary shutdown after a false alarm can fall into the gap between the security failure and system failure definitions, with neither responding.
Watch for these:
- "Directly caused by" language with no voluntary shutdown wording. It invites the argument that you caused the loss.
- Separate sublimits for voluntary shutdowns, often a fraction of the main BI limit.
- Insurer pre-approval required before a shutdown counts. That's impractical at 2 a.m.
- Broad governmental-action exclusions with no carve-back for orders that follow a cyber event.
- Longer waiting periods for system failure or dependent business interruption than for security failures.
- Infrastructure and war exclusions wide enough to catch shutdowns forced by a power, telecom or cloud-region outage.
What to ask your broker to add before binding
Ask for these changes at renewal, not mid-incident. Send the list to your broker in writing and require each answer to cite the actual policy wording.
- Add express voluntary shutdown coverage that treats any shutdown made to mitigate a suspected or actual covered event as an interruption.
- Make a reasonable belief of a security failure, or a recommendation from panel responders, enough to trigger cover.
- Carve back regulator- and authority-ordered shutdowns that follow a covered event, drafted to cover every jurisdiction you operate in.
- Align waiting periods across security failure, system failure and dependent BI, ideally in the 8 to 12 hour range, and start the clock when the interruption begins.
- Raise or remove any voluntary shutdown sublimit, and add an extended period of indemnity.
- Confirm that claim-preparation costs are covered outside the retention.
On cost, typical 2026 market ranges vary by contract: voluntary shutdown wording is often included at no extra charge or for a modest loading, while full system failure coverage and shorter waiting periods usually add a noticeable percentage to premium, depending on sector, controls and region. Confirm pricing with your broker and insurer. Local pricing and product availability vary widely between countries.
A simple rule: if your incident response plan tells staff to isolate systems on suspicion of an attack, your policy has to cover suspicion-based shutdowns. If it doesn't, change one or the other before you bind. Have a licensed broker or coverage counsel review the final wording.
Frequently asked questions
Is voluntary shutdown coverage standard in cyber policies?
It's common in mainstream forms but not universal, and the wording varies a lot. Some policies cover only shutdowns that follow a confirmed security failure, and some apply a sublimit. Read the business interruption definition rather than relying on a summary of cover.
Will my policy pay if we shut down and it turns out there was no attack?
Only if the wording accepts a reasonable belief of a security failure or covers system failure broadly. Many policies need an actual covered event, so a false-alarm shutdown may not be covered. Ask your broker specifically how the policy treats precautionary shutdowns.
What is a typical cyber business interruption waiting period?
It commonly runs from a few hours to a day, and roughly 8 to 12 hours is typical for mid-size companies. Check when the clock starts and whether the period works as a deductible or as a qualifying period, because both affect the payout as much as the length does.
Are regulator-ordered shutdowns covered by cyber insurance?
Often not by default, because many policies exclude governmental or civil authority action. Some insurers will carve back orders that follow a covered cyber event. Make sure the carve-back covers the regulators in every country where you operate.
Do I need insurer approval before shutting systems down?
Some wordings require approval or prompt notification, and the strict versions are impractical during a live incident. Negotiate language that accepts shutdowns recommended by panel responders, and notify the insurer as soon as you reasonably can. A licensed broker can confirm what your specific policy requires.
Written by the Auditcover Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.