Cyber insurance pays to respond to and recover from a security incident, and to defend the claims that follow. Paired with Tech E&O, it covers both sides of a technology failure. This guide explains what each covers, where the gaps hide and how to tell whether your current policy would actually respond.
When something goes wrong in your systems, the bills arrive fast: forensic investigators to find out what happened, breach counsel to tell you what you are legally required to do, negotiators if your data is held for ransom, engineers to restore it, and the revenue you lose while you are down. Cyber insurance pays those first-party costs. It also pays third-party claims, such as customers or regulators coming after you because personal data was exposed.
Tech E&O covers a different failure. If your platform goes down, an integration sends bad data or a release breaks a customer’s workflow, and that customer loses money, Tech E&O pays to defend and settle the claim. Cyber is about someone getting into your systems. Tech E&O is about your product not doing what you promised. Most technology companies need both, ideally written together so a single incident can’t fall between two policies.
SOC 2 and strong security reduce the odds of an incident and improve your terms, but they don’t pay for one. Insurance is what funds the response when controls are not enough.
Short answer: any company that holds customer data, runs software customers depend on or signs enterprise contracts. Cyber and Tech E&O usually become non-negotiable the first time a customer’s security questionnaire or contract asks for proof of both.
Exposure grows with every customer, integration and record you hold. This table maps common milestones to what we would typically recommend. It is general guidance, and your lawyers can tell you where specific contractual or legal duties apply.
Little customer data, few contracts. Low urgency, but controls you set up now are cheaper than retrofits.
PrepareSecurity questionnaires begin and customers ask who is liable if something breaks.
Get readyMaster agreements name minimum cyber and Tech E&O limits and ask for certificates.
Buy nowHealth, financial or biometric data and payment flows raise regulatory exposure.
Raise limitsLarger records counts, diligence and tail questions arrive together.
Plan the tailRead the insurance clause of your biggest customer contract before you buy. It sets the floor for limits, and the wording of that clause is often stricter than the policy you would have picked on your own.
| Where you are | Cyber? | Tech E&O? | Why |
|---|---|---|---|
| Pre-revenue, no customer data in production | Worth discussing | Not yet | Few people can claim harm. Revisit before the first pilot or paid customer. |
| Early customers, a SaaS product, some personal data | Yes | Yes, soon | A single incident or outage can reach every customer at once, and early contracts start asking for proof of cover. |
| Enterprise or regulated customers (finance, health, government) | Yes, with higher limits | Yes | Contracts often set minimum limits and require specific wording such as additional insured status. |
| Payments, lending or custody of customer funds | Yes, with social engineering and funds transfer cover | Yes | Fraud losses and regulator attention follow the money. Coordinate with crime cover. |
| AI product that touches customer data or makes decisions | Yes, check AI exclusions | Yes, check AI exclusions | Underwriters ask how models are trained and monitored, and some forms now carve out AI-related losses. |
| Hardware or connected devices | Yes, ask about bricking cover | Yes | A faulty update can disable devices in the field, which is a cost most cyber forms do not assume. |
| Preparing a sale or winding down | Keep or extend | Keep or extend | Claims often appear after the deal or the closure. Ask about extended reporting before you sign or cancel. |
Most cyber policies exclude or limit:
Short answer: first-party cyber coverage pays your own costs after an incident, such as investigators, restoration and lost income. Third-party cyber coverage pays when someone else claims you caused them harm, such as customers, individuals or regulators. Most policies bundle both, but the limits, retentions and triggers are often separate.
The difference matters because the two halves are triggered differently. Your own losses begin with an event in your systems and a notice to the carrier. Liability losses begin with a demand, a lawsuit or a regulatory request. Read first-party coverage and third-party coverage side by side in your policy, because a strong liability section does not help if the response costs are sublimited, and the reverse is also true.
| What it pays | Typical examples | What starts it | |
|---|---|---|---|
| First-party | Your own costs of responding and recovering | Forensics, breach counsel, restoration, extortion response, lost income, notification | A security event or covered system failure that you report |
| Third-party | Defense and damages when others claim against you | Privacy liability, network security liability, regulatory defense, some contract claims | A claim, demand, suit or regulatory request made against you |
| Hybrid costs | Items that sit between the two | Credit monitoring, call centers, public relations, media liability | Depends on the form, so check which section and which limit applies |
Tech E&O sits on the third-party side but covers a different trigger: your product or service failed to do what you promised. E&O responds to the customer who lost money, while cyber responds to the incident that caused it, when there is one. That is why we prefer the two written on one form or at least on forms that were read against each other.
Short answer: usually yes, including negotiation, specialist support, restoration and lost income, but often with a sublimit, coinsurance or specific application conditions. A ransom payment itself is paid only where the law allows it and the carrier agrees.
Ransomware is the claim most buyers think about, which is why it is also the area where wording differences matter most. Ransomware coverage is rarely one line. It is a chain of costs, and each link can carry its own limit.
The costs of negotiating, validating the attackers and handling the crisis are often covered separately from any ransom itself. Whether a payment is allowed depends on law, sanctions screening and the carrier’s consent.
Why it matters: ask who decides, how fast, and what happens if the carrier says no. Counsel can advise on the legal limits in your situation.
Policies typically pay to restore data and systems to where they were, not to improve them. Replacing everything with better infrastructure is usually your cost.
Why it matters: a clean rebuild can be the fastest path back, so know in advance whether the policy pays for it or only for recovery.
Attackers increasingly look for backups first. Underwriters ask whether backups are offline or immutable and whether you have tested a restore.
Why it matters: the answer on your application can decide both price and whether a ransomware claim is paid in full.
Many forms cap ransomware losses below the main limit or make you share a percentage of each loss.
Why it matters: the headline limit may not be the limit that responds. See the sublimit section below.
Many attacks now steal data and threaten to publish it even if you can restore from backup. Check that extortion over stolen data is covered, not just encryption.
Why it matters: restoring your systems does not end the problem when the data is already outside.
Ask for the ransomware limit and the ransomware retention as numbers, not as a yes or a no. If the broker cannot give you both numbers in one sentence, the policy probably has a trap in it.
Short answer: business interruption pays the income you lose, plus continuing expenses, while a covered event keeps your systems down, usually after a waiting period. Dependent business interruption extends that to outages at providers you rely on, such as cloud hosting or payment processors.
For a software company, revenue stops when the service stops, so this is often the largest part of a cyber loss and the part least understood at purchase. Four parts of the wording decide the payout.
| Wording | What it controls | What to negotiate |
|---|---|---|
| Waiting period | How many hours of downtime pass before income loss is covered | A shorter period for always-on services, and clarity on whether the clock starts at the outage or at discovery |
| Trigger | Whether only a malicious attack counts, or also a non-malicious system failure such as a bad update or a human error | Cover for system failure, not just security failure, if your risk is mostly operational |
| Period of restoration | How long income loss is covered after systems return, including the ramp back to normal | A defined tail for lost customers and delayed renewals, if available |
| Calculation | How lost income and continuing expenses are measured and proven | Agree on the method and records early, because documentation is the usual friction point |
| Dependent providers | Which outside vendors are covered, and whether the list is named or all providers | Cloud, identity, payments and other critical vendors included, ideally without a list that goes stale |
See contingent business interruption for the property equivalent. The cyber version has one wrinkle: many forms cover dependent outages caused by a security event at the vendor but not a plain technical failure. Since provider outages are often operational rather than malicious, that distinction matters more than the headline.
Map your three most critical vendors, then ask whether an outage at each one is covered and whether it must be caused by an attack. The honest answer sorts good forms from weak ones in a few minutes.
Short answer: often it covers the cost of defending a regulatory investigation after a privacy or security event, and sometimes fines and penalties where the law allows them to be insured. Coverage varies by policy wording, jurisdiction and the type of penalty, so treat it as something to confirm rather than assume.
After a breach, regulators and contract counterparties may ask what you did, when you did it and whether your safeguards were reasonable. The cost of answering those questions is real even if nothing is ever fined.
Legal costs of responding to an inquiry, subpoena or proceeding tied to a covered privacy or security event.
Why it matters: defense cost often exceeds the penalty, so confirm that informal requests, not only formal proceedings, are covered.
Insurable only where the law permits, and typically subject to a sublimit. Many policies say “where insurable” and leave the rest to the applicable law.
Why it matters: ask whether the policy favors an insurable reading, and speak to counsel for what applies to you.
Card brands can assess costs after a breach involving payment data. Some forms cover these under a contractual liability extension and others exclude them.
Why it matters: if you process or store card data, check this one by name.
Enterprise agreements may make you responsible for a customer’s notification costs and legal bills. Policies often limit liability assumed under contract.
Why it matters: compare the indemnity in your contract with the exclusion in your policy before you sign.
A single technology incident can touch four different policies. Here is how common situations usually map.
| Scenario | Cyber | Tech E&O | Crime | D&O |
|---|---|---|---|---|
| Ransomware encrypts your production systems | Covered | No | No | No |
| A breach exposes customer personal data | Covered | Customer contract claims, if bundled | No | No |
| Your platform goes down and a customer claims lost revenue | No | Covered | No | No |
| Your cloud provider has an outage and you can’t serve customers | Your lost income, if dependent BI is included | Customer claims, if not excluded | No | No |
| Finance pays a fake invoice after a vendor’s email is compromised | Covered, up to a sublimit | No | Covered, with social engineering cover | No |
| An employee pastes customer data into a public AI tool | Depends on the wording | No | No | No |
| A customer sues over a bug that shipped before your retroactive date | No | Depends on the retroactive date | No | No |
| Shareholders sue the board over how a major breach was handled | No | No | No | Covered |
Short answer: a retroactive date is the earliest date a wrongful act or error can occur and still be covered by a claims-made policy. Cyber and Tech E&O policies are usually claims-made, so the date you choose, and whether you keep it when changing carriers, decides which past events are covered.
Many cyber policies treat the incident as the trigger and offer broad prior acts, while Tech E&O more often works from a stated date. Because the details differ by form, the practical advice is the same: ask what the retro date is, and what happens to it at renewal and at replacement. See also claims-made policies and prior acts coverage.
A bug ships, or an attacker gets in and stays quiet.
Before retro?Coverage continues, or a new carrier writes the account.
Keep the dateA customer complains, or you find the intrusion.
Claim madeOnly if the original event falls after the retro date.
Policy checkedWhen you switch carriers, ask for the retroactive date to carry over. A reset to the new inception date can leave years of past work uninsured, even if you never had a gap.
If a policy ends without a replacement, an extended reporting period can keep claims reportable afterward, but only if the option exists and is priced before you need it. See also tail coverage.
Short answer: multi-factor authentication, protected and tested backups, endpoint detection, controlled privileged access and a patching routine. Each is often required to get a quote at all, and strong evidence for each earns better terms.
Cyber underwriting is closer to a security review than most lines. The point is not to achieve perfect security. It is to show a carrier that you know where the risks are and that your answers on the application match what you really run.
Required on email, remote access, administrative accounts and backup consoles, not just on a few users.
Why it matters: a gap on one admin account is the kind of detail that appears in a claim file.
Offline or immutable copies, kept apart from the main network and restored on a schedule to prove they work.
Why it matters: untested backups are an assumption, and underwriters treat them that way.
Monitoring on company laptops and servers that can isolate a compromised device quickly.
Why it matters: it is often the line between a contained incident and a company-wide encryption event.
Regular checks of who can reach production, customer data and cloud consoles, with prompt removal of departed staff and contractors.
Why it matters: stolen or stale credentials are a leading way in, including from contractors.
A defined timeline for fixing known weaknesses, with critical issues handled fastest.
Why it matters: carriers ask because attackers move quickly once a flaw is public.
Logs retained long enough to investigate, and a written plan that names who does what, tested at least once.
Why it matters: forensics firms work faster and cheaper with usable logs.
Fill in the application with the person who runs your infrastructure, not just the person who signs it. Answers that are slightly generous are a common reason claims are disputed and policies are rescinded.
Short answer: a sublimit caps one type of loss below your main limit, and coinsurance makes you share a percentage of every covered loss. Both are common in cyber policies, so the number on the front page is rarely the number that pays a specific claim.
Pricing pressure usually shows up here rather than in the headline limit. Two quotes with the same limit and similar premiums can pay very different amounts on the same incident.
| Trap | How it works | Question to ask |
|---|---|---|
| Sublimit | A cap on ransomware, social engineering, regulatory fines or another loss, set below the main limit | What is the exact amount for each major loss type, and is it inside or on top of the main limit? |
| Coinsurance | You pay a share of every covered loss of that type, and the carrier pays the rest | Is there coinsurance on ransomware, and does it apply to the full loss or only part of it? |
| Separate retentions | Different retentions by coverage, sometimes higher for ransomware or for larger companies | What do I pay first for each coverage section? |
| Shared aggregate | Cyber and Tech E&O share one limit, so a large cyber loss can erode what is left for customer claims | Are the limits separate or shared, and can we buy more than one limit? |
| Defense inside the limit | Legal costs reduce the limit instead of sitting on top of it | Do defense costs erode the limit, and by how much? |
| Reporting conditions | Notice must be given within a stated window, or the claim can be denied | What is the exact notice requirement, and who in the company knows it? |
See also limit of liability and deductible for the basic terms.
Short answer: call the carrier’s incident line or your broker before hiring outside vendors, because most policies require notice and approved or consented vendors to protect coverage. Then contain the incident, preserve evidence and let breach counsel direct the investigation.
Isolate affected systems without wiping them, and preserve logs and images.
First hoursUse the incident line or your broker. Late notice is a common reason coverage is questioned.
Right awayBreach counsel engages forensics so findings can stay privileged, using panel or approved firms.
Day one to twoWork out what was taken, which duties apply and who must be told. Counsel advises on the legal requirements.
Days to weeksRebuild systems and document costs and lost income for the claim.
Weeks to monthsPanel vendors and your own advisers. Many carriers keep a panel of breach counsel, forensic firms and notification vendors whose rates are pre-agreed. Using them is usually the smoothest path. If you already have a counsel or incident response firm, ask the carrier in advance whether they can be approved, rather than asking during an emergency. Policies differ on whether outside vendors are paid in full, partly or not at all, which is why the consent language is worth reading before you need it.
When you report, a carrier may acknowledge the claim while reserving its rights on parts it is unsure about. That is normal, and it is a signal to keep records and ask what is and is not accepted. See also first notice of loss and defense costs.
Keep the incident hotline number and your policy number somewhere outside your own systems, such as a printed page or a personal phone. An attack on email and cloud tools can lock you out of the information you need most.
Short answer: some cyber policies exclude losses from war, state-backed attacks and failures of widespread infrastructure, and a growing number carve out losses tied to AI. The impact depends entirely on wording, so these are the clauses to read closely and, where possible, narrow.
Older wording excluded war broadly. Newer wording tries to define when a state-backed attack counts, often through attribution or the scale of impact.
Why it matters: who decides attribution, and how, affects whether a large attack is paid. We read it with an eye to narrow, clear language. Counsel can advise on specific legal questions.
Exclusions for power, utility, internet backbone or telecom failures outside your control, sometimes with carve-backs for providers you contract with.
Why it matters: cloud and hosting outages can look like infrastructure to an insurer that wants them to be.
Wording that removes cover for losses involving machine learning, model output or automated decisions. Some are narrow and some are broad.
Why it matters: written broadly, it can undo cover for the core product of an AI company. We negotiate scope before binding. See our AI liability guide and AI liability article.
Some forms exclude or reduce cover if you did not keep the controls you described.
Why it matters: it ties the application to the claim, so accuracy matters at both ends.
Costs of improving systems beyond what existed before the incident are usually excluded.
Why it matters: ask whether any portion is covered when replacement equals improvement.
Because exclusions are written by the carrier and can change at renewal, compare the wording year to year rather than relying on a summary.
Smaller limits inside your overall limit for specific losses, most often ransomware, social engineering and regulatory fines.
Why it matters: a $3 million policy with a $250,000 ransomware sublimit is a $250,000 ransomware policy.
The number of hours your systems must be down before business interruption coverage begins.
Why it matters: for a real-time platform, a 12-hour waiting period can erase most of the claim; shorter periods are negotiable.
Extends income coverage to outages at vendors you rely on, such as cloud hosting, payments or identity providers.
Why it matters: for most software companies, a vendor outage is more likely than a direct attack.
What you tell the carrier about MFA, backups, endpoint detection and patching becomes part of the policy.
Why it matters: if a control you described wasn’t actually in place, the carrier may deny the claim or rescind the policy.
Many policies require you to use the carrier’s approved breach counsel and forensics firms, or get consent first.
Why it matters: hiring your own firm in the first hour without consent can leave those costs uncovered.
New wording that removes coverage for losses involving machine learning, model output or automated decision-making.
Why it matters: written broadly, it can deny almost any claim against an AI company; we negotiate it out before binding.
Two cyber policies with the same limit can respond very differently. These are the features we raise most often, in plain terms. Availability depends on the market and your controls.
Covers income lost to an outage at any provider you rely on, not only a named list.
Why it matters: a named list goes stale as you add vendors.
Pays for downtime caused by non-malicious failures such as a bad update, in addition to attacks.
Why it matters: for many software companies this is the likelier event.
Reduces the hours before income loss begins to count.
Why it matters: for a service that is always on, hours matter.
Treats ransomware like other cyber losses instead of capping or sharing it.
Why it matters: it is the loss buyers worry about most.
Pays to replace hardware that a cyber event renders unusable.
Why it matters: especially relevant for connected devices and hardware companies.
Pays for lost income after a publicized incident, beyond the downtime itself.
Why it matters: for some businesses, customer loss is the larger cost than the outage.
Lets you use your existing counsel or forensics firm with agreed terms.
Why it matters: it reduces friction in the first hours of an incident.
Keeps past work covered when you change carriers.
Why it matters: a reset to inception can leave a gap you never see.
Short answer: growth, new products and new vendors usually change your risk faster than your policy changes, so the common events below are the ones to tell your broker about.
| Event | What typically happens | What to do |
|---|---|---|
| Revenue and customer count grow | Business interruption and notification exposure rise, and your limits can look thin | Revisit limits at renewal and when large contracts arrive. |
| You launch an AI feature | Underwriters may ask new questions and some forms add AI exclusions at renewal | Tell your broker before launch and ask for an AI wording review. |
| You change cloud or payment providers | Dependent BI and application answers may no longer match your setup | Update the application and confirm the provider list. |
| An incident or near miss occurs | Many policies let you report circumstances that may become a claim | Report promptly and ask about notice of circumstances. |
| You change carriers | Retroactive dates and prior acts can reset | Negotiate the date to carry over before binding. |
| You are acquired or you acquire | A change in control clause usually ends cover for new events at closing | Plan an extended reporting option into the deal terms. |
| You wind down | Claims can arrive well after operations end | Ask about extended reporting before you cancel. |
What happenedAttackers used a stolen contractor login to encrypt production and the backups stored alongside it. The platform was down for five days.
The claimForensics, negotiation, restoration and nearly a week of lost revenue.
What respondedCyber paid response and restoration costs, and lost income after the waiting period.
What happenedA vendor’s email account was compromised and sent updated bank details. Finance paid $180,000 to the fraudster.
The claimA social engineering loss with no hack of the company’s own systems.
What respondedOnly $100,000, because social engineering carried a sublimit nobody had questioned at binding.
What happenedA leaked API key exposed an enterprise customer’s user data. The customer then sued under its data processing agreement.
The claimNotification and forensics costs, followed by a breach of contract claim.
What respondedBoth, without a coverage fight, because cyber and Tech E&O were written together on one form.
What happenedA major cloud provider had a multi-day outage. A SaaS company that depended on it could not serve customers and lost revenue, though its own systems were never attacked.
The claimBusiness interruption caused by a vendor’s failure.
What respondedOnly a policy with dependent business interruption coverage extended to cloud providers responded. Many forms limit it or exclude non-malicious outages.
What happenedAn employee pasted a customer export into a public AI tool while troubleshooting. The customer demanded notification and an explanation.
The claimA privacy event with notification, legal and forensic costs, and a customer relationship at risk.
What respondedIt depended on the wording. Many policies treat it as a privacy or security event, but some carriers are adding AI-related exclusions that can remove it.
What happenedFollowing a breach, a state attorney general opened an inquiry into whether the company had reasonable security and notified customers on time.
The claimA regulatory investigation, with defense costs and potential penalties.
What respondedRegulatory defense and fines where insurable were covered under a form that included them, subject to sublimits and the limits of the law.
Scenarios are illustrative composites based on common claim patterns, not specific Alton Risk clients.
Cyber pricing is driven by your security controls more than any other line of insurance, which means it is the policy where preparation pays off most. A company with MFA everywhere, immutable backups and endpoint detection can see a very different quote than a peer of the same size without them.
| Factor | Why it moves your premium |
|---|---|
| Security controls | MFA, endpoint detection, tested offline backups and a patching process are often required just to get a quote, and strong controls earn better terms. |
| Revenue and record count | Business interruption losses scale with revenue, and notification costs scale with the number of people whose data you hold. |
| Type of data | Health, financial and biometric data carry heavier regulatory exposure than business contact information. |
| Industry | Fintech, health tech, crypto and AI companies attract more targeted attacks and regulatory scrutiny. |
| Vendor dependencies | Reliance on a few critical providers increases business interruption exposure, especially with dependent BI cover. |
| Claims history | Prior incidents, even small ones, are priced in and can trigger specific exclusions. |
| Limits, retention and sublimits | Higher limits and full ransomware or social engineering limits cost more; a higher retention lowers premium. |
Short answer: have your security evidence and customer contract requirements ready before you ask for quotes. Carriers move faster and offer better terms when the application is complete and the controls are described accurately.
Incomplete security answers, an unmentioned past incident, and submitting only days before a contract deadline.
Why it matters: each one is avoidable with a short review before you start.
Answering the application from memory, comparing premiums without comparing sublimits, and assuming a certificate means the policy is strong.
Why it matters: a cheaper quote that pays less on ransomware or outages is not cheaper.
Often yes. Turning on multi-factor authentication broadly or testing a restore can change both eligibility and price.
Why it matters: a few weeks of preparation can change the quote, and the fix is useful on its own.
Having underwritten technology risks on the carrier side, we know cyber underwriting has become a security review. A submission that answers these questions clearly, with evidence, brings more carriers to the table and better terms with them.
If you can’t answer all eight with confidence, send us your policy and we will review it line by line.
→ The insurance requirements enterprise customers demand in contracts
→ Why emerging tech companies can’t ignore patent infringement liability
→ Errors & Omissions coverage guide
Cyber covers your own losses after a security event, such as forensics, notification, restoration and business interruption, plus third-party privacy claims. Tech E&O covers claims that your product or service caused a customer financial harm through failure, errors or missed SLAs. Most technology companies need both, ideally on one coordinated form.
Most cyber policies cover ransomware, including negotiation, lawful ransom payments, incident response, data restoration and business interruption. Terms vary widely, though, and many policies apply a ransomware sublimit or coinsurance. We review that language before binding so the coverage matches your real exposure.
For most technology companies, the starting point is the highest limit required in any customer contract, since enterprise agreements commonly specify cyber and Tech E&O minimums. From there we model a realistic incident for your business, including downtime, the records you hold and response costs, and benchmark against peers at your stage.
Yes. SOC 2 reduces your risk and helps you qualify for better terms, but it doesn't pay for a breach when one happens. Cyber insurance pays for the forensics, legal defense, notification, credit monitoring, regulatory fines where insurable and business interruption that no compliance framework covers.
Yes. Cloud providers operate under a shared responsibility model: they secure the infrastructure, while you remain responsible for your accounts, configurations, access credentials and data. Most breaches at cloud-hosted companies come from that customer side, and a provider outage is a business interruption exposure that dependent BI coverage can address.
Tech E&O covers financial losses when your platform fails to perform, such as downtime beyond your SLAs, API errors delivering bad data or integration failures that harm a client. This is distinct from cyber coverage, which addresses unauthorized access rather than product failure.
It depends on the wording. A data leak through an AI tool or a prompt injection attack may be covered as a security or privacy event, but some carriers are adding exclusions for losses involving machine learning or automated decisions. We scan every cyber and Tech E&O policy for these exclusions and negotiate to remove them before binding.
Call your carrier's incident hotline or your broker before engaging outside vendors. Most policies give you access to pre-approved breach counsel and forensics firms, and using them, or getting consent for your own, protects your coverage. Then preserve evidence and avoid wiping affected systems until forensics advises.
Yes. Investors, customers, landlords and partners often require specific policies, such as D&O, Tech E&O, Cyber and Crime, at minimum limits with additional-insured or waiver-of-subrogation language. We read your contracts, place coverage that satisfies them and issue certificates quickly so a deal never stalls on paperwork.
First-party coverage pays your own costs after an incident, such as forensics, restoration, extortion response and lost income. Third-party coverage pays when others claim against you, such as customers, individuals or regulators, including defense costs. Most policies bundle both, but limits and retentions are often separate, so check each section.
It is the amount of time your systems must be down before lost income is covered. Losses during the waiting period are typically yours. For always-on software, a shorter waiting period is often worth negotiating, and you should confirm when the clock starts.
Sometimes. Many policies cover the cost of defending a regulatory inquiry after a covered event, and some cover fines and penalties only where the law allows them to be insured, usually with a sublimit. It depends on the wording and the jurisdiction, and your counsel can advise on what applies to you.
It can sit on either policy, and sometimes both, each with its own sublimit. Check which policy responds first, whether a verification procedure is a condition of payment and whether impersonation of vendors and customers is covered, not just executives.
It is the earliest date a wrongful act or error can occur and still be covered under a claims-made policy. When you change carriers, ask for the date to carry over so earlier work stays covered. Details vary by form, so confirm how your policy treats past events.
Carriers commonly look for multi-factor authentication on email, remote access and administrative accounts, protected and tested backups, endpoint detection, a patching routine and a written incident response plan. Requirements vary by carrier and company size, and accurate answers matter as much as the controls themselves.
Sometimes, but many policies require panel vendors or the carrier’s prior consent. If you already work with a firm, ask in advance whether it can be approved, because hiring first and asking later can leave those costs uncovered.
Some policies do, and the wording varies from a broad war exclusion to narrower language about state-backed attacks and their scale. The clause is worth reading closely, and legal counsel can advise on how it would apply in a specific situation.
Coinsurance means you share a percentage of each covered loss of a certain type, most often ransomware, with the carrier paying the rest. It reduces the money available for a claim even when the stated limit looks large, so ask whether it applies and to which losses.
Only if the policy includes dependent business interruption that reaches that provider, and some forms limit it to outages caused by a security event. Ask whether cloud, payments and identity vendors are included and whether a non-malicious technical failure counts.
It depends on the policy wording. Many Tech E&O forms respond to claims that your technology failed a customer, but some now carry AI-related exclusions or conditions. Ask for the AI wording to be reviewed before you launch an AI feature.
Can't find an answer to your questions? Reach out to our team →
The gaps in cyber coverage live in sublimits, waiting periods and exclusions that rarely come up until a claim. We review your current cyber and Tech E&O against your contracts, your controls and the wording carriers are adding this year, then tell you plainly what we would change.
Sources and further reading: CISA, "Cybersecurity best practices" (opens in a new tab); NIST, "Cybersecurity Framework" (opens in a new tab); Triple-I (Insurance Information Institute): Cyber insurance, a key part of a robust business strategy (opens in a new tab); Triple-I: Cyber liability risks (opens in a new tab); U.S. GAO: What is cyber insurance, and why is it in high demand? (opens in a new tab); IRMI: Technology errors and omissions insurance (opens in a new tab); Lockton: Understanding technology errors and omissions coverage (opens in a new tab); Insurance Journal: U.S. Treasury Warns Cyber Insurers Against Paying Ransomware Demands (opens in a new tab); Hunton: While OFAC Cautions Cyber Insurers, Policyholders Should Ensure They Are Covered (opens in a new tab); FBI IC3: Business Email Compromise, public service announcement (opens in a new tab). This page is general information, not legal or insurance advice. Coverage terms vary by carrier, policy form and state.
Is social engineering covered by cyber or by crime?
Short answer: it can be either, and sometimes both, with a sublimit on each. Where it sits depends on how the policies are written, so the useful question is not “do we have it” but “which policy pays first and how much.”
Social engineering fraud and business email compromise involve a person being tricked into sending money, not a system being hacked. That is why they often fall between a cyber policy, which focuses on systems, and a crime policy, which focuses on theft of money. See our crime and fidelity guide for the other side.
Verification conditions
Some forms pay only if you followed a call-back or dual-approval procedure before sending funds.
Why it matters: a policy can be strong on paper and weak in practice if your process is not the one it expects.
Which policy responds first
When both a cyber and a crime form offer cover, an “other insurance” clause decides who pays and in what order.
Why it matters: two sublimits that point at each other can leave you with less than either one promised.
Impersonation of vendors, executives and customers
Check that the form names all three, not only fake executives.
Why it matters: fraud against suppliers is common, and gaps in the definition show up late.