Declined for Cyber Insurance? A 60-Day Playbook to Get Back to a Bindable Quote
A decline is usually a list of fixable control gaps, not a verdict on your company. Get the reasons in writing, fix what underwriters weigh most and go back to market in the right order.
What a Cyber Insurance Decline Is Actually Telling You
Your broker says the market said no. Before you decide the company is uninsurable, work out what kind of no you got. When cyber insurance is declined for a small or mid-size company, it usually means an underwriter couldn't price the risk from the controls and information in front of them. That's different from "too dangerous to cover," and much easier to fix.
Declines fall into three groups, and each needs a different response:
- Appetite declines. The carrier doesn't write your industry, revenue band, country or claims profile. Your controls don't matter to that market. Move on to markets that write your class.
- Control declines. A gating control is missing or only partly deployed. The usual ones are multi-factor authentication (MFA), endpoint detection and response (EDR), segregated backups, or remote desktop exposed to the internet. Many of these can be fixed in about 60 days.
- Information declines. The application had blank answers, contradicted the carrier's outside-in scan, or skipped a past incident. These are the fastest to fix and the most damaging to leave alone.
The 60-day frame is deliberate. It's long enough to deploy the controls underwriters treat as non-negotiable, and short enough that the same underwriters still remember your file. If your current policy expires sooner, ask the incumbent carrier through your broker for a short extension, often 30 to 90 days. Some grant one when they can see remediation underway. None are obliged to.
| Window | Goal | Output |
|---|---|---|
| Days 1–7 | Diagnose | Written decline reasons, scan reports, gap list |
| Days 8–40 | Remediate gating controls | MFA, EDR, backups and exposure fixes deployed at full coverage |
| Days 30–45 | Document | Evidence pack and cover letter |
| Days 45–60 | Remarket and bind | Quotes, negotiated subjectivities, bound policy |
Days 1–7: Get Every Decline Reason in Writing
A spoken "they had concerns about your security" is useless. You need each market's specific reasons, in writing, through your broker. Commercial insurers generally aren't required to explain a decline, and the rules differ by country. Still, most underwriters will tell a broker what they'd need to see if the broker asks directly.
- Ask for the reasons, market by market. Push for specifics: which control, which system, which application answer.
- Request the external scan findings. Many carriers and managing general agents (MGAs) scan your internet-facing assets before quoting. Ask for the open ports, vulnerable services, expired certificates or leaked credentials they flagged. Your own team may not know about them.
- Ask the reversal question. "What would you need to see to offer terms?" The answer is that carrier's real minimum security requirement for your size and sector, often narrower than the generic list in its marketing.
- Classify each decline as appetite, control or information.
- Audit your own application. Look for any answer that was optimistic, outdated or wrong. If your cyber insurance application was rejected partly because of inconsistent answers, correcting them is your first fix.
If you went direct or used a generalist intermediary, bring in a broker with a dedicated cyber practice now. In many markets, including much of the EU, India and the Gulf states, you'll need a licensed intermediary anyway. A specialist knows which markets have appetite this quarter, and that knowledge is worth more than any single control you can buy.
Triage: Fix What Underwriters Weigh Most, in That Order
Not every gap carries the same weight. Underwriters treat a handful of controls as gates. If one is missing, there's often no quote at any price. Everything else moves the premium or the retention, the amount you pay on each claim before cover starts. Spend your first 40 days on the gates.
| Control gap | Underwriter weight | Typical time to fix | Indicative cost (typical 2026 ranges) |
|---|---|---|---|
| MFA on email, remote access, cloud consoles and admin accounts | Gating | 1–4 weeks | Often already in your Microsoft 365 or Google Workspace licenses; otherwise roughly $3–8 per user/month |
| EDR on all endpoints and servers | Gating for most markets | 2–6 weeks | Roughly $5–15 per endpoint/month; managed detection and response (MDR) often $10–30 or more |
| Backups that are segregated, immutable and restore-tested | Gating for ransomware cover | 2–8 weeks | Roughly $500–5,000/month depending on data volume |
| Remote desktop (RDP) or other admin services exposed to the internet | Gating | Days | Mostly internal time; VPN or zero-trust access roughly $5–12 per user/month |
| End-of-life or unpatched internet-facing systems | High | Days to months | Wide range; replacement is the main cost |
| Privileged access management | High for mid-size and larger | 4–12 weeks | Roughly $15,000–80,000/year |
| Email security (filtering, DMARC enforcement) | Medium | 1–3 weeks | Roughly $2–6 per user/month |
| Incident response plan and tabletop exercise | Medium | 2–4 weeks | Roughly $5,000–20,000 for a facilitated exercise |
| Phishing awareness training | Medium | 2 weeks | Roughly $1–5 per user/month |
Pricing varies by region, reseller and contract length, so confirm with vendors. Microsoft Defender for Endpoint, CrowdStrike, SentinelOne and Sophos are widely recognized by underwriters and sold internationally. If your current product isn't a recognized EDR, expect questions.
The rule: don't buy a medium-weight control until every gating control is at full coverage. A new training platform won't offset admin accounts without MFA.
Days 8–40: Closing Gaps Without Overbuilding
Underwriters care about coverage percentages, not product names. If EDR sits on 85% of endpoints, many will treat it as missing, because attackers get in through the other 15%. The same goes for MFA that covers staff but skips service accounts, a legacy mailbox or the vendor remote-access tool.
Here's a hypothetical. Say a 120-person distribution company was declined over an exposed remote desktop gateway, no EDR on its servers, and backups written to a network share on the same domain. A sensible 40-day plan:
- Week 1: Shut down the exposed remote desktop. Move remote access behind a VPN or zero-trust gateway with MFA. Enforce MFA on every admin account.
- Weeks 2–4: Extend EDR to all servers, or buy MDR if nobody watches alerts overnight. Bring end-user MFA to 100% and keep a written list of exceptions.
- Weeks 3–6: Add an immutable or offline backup copy on separate credentials. Then run and time a full restore of one critical system.
Incremental first-year spend for a company that size might land somewhere around $25,000 to $60,000. The main driver is whether you buy MDR or watch alerts yourself.
Underwriters will notice these red flags:
- SMS-based MFA on privileged accounts. App-based MFA is the usual floor, and phishing-resistant keys are increasingly expected for admins.
- A managed service provider (MSP) with broad remote access and no MFA of its own. Your MSP's controls count as your controls.
- Undocumented exceptions. A short, signed exceptions register with compensating controls goes down better than an unexplained gap.
Building the Evidence Pack Underwriters Will Actually Read
A second submission has to persuade a skeptical reader quickly. Give them proof, not adjectives, in a pack they can review in 15 minutes.
- A one- or two-page cover letter listing each original decline reason, what you changed and the completion date. Map it line by line.
- A control attestation signed by the CISO, IT lead or a named officer.
- MFA evidence: screenshots of conditional access or equivalent policies, plus a report showing enrollment rates.
- An EDR coverage report exported from the console, showing protected device counts against your asset inventory.
- A backup architecture diagram plus your latest restore test: date, systems restored and time to recover.
- A clean external scan rerun after remediation, ideally with the same type of scanner the carrier used.
- An incident response plan and a retainer letter if you have a pre-agreed response firm.
- An incident summary if a past event contributed to the decline: root cause, remediation, closure and regulatory notification status.
That last item needs care. Notification rules differ widely. GDPR in Europe, and the UK equivalent, generally requires notifying the regulator within 72 hours of becoming aware of a qualifying personal-data breach. India's CERT-In directions set a much shorter window, currently six hours, for certain reportable incidents. Other jurisdictions have their own timelines. Have outside counsel review incident documents before they go to market, to protect privilege and to confirm the summary matches what regulators were told.
Remarketing Cyber Insurance to the Right Markets, in the Right Order
The worst move is to blast every market at once. A market that declines you twice in a quarter will be slower to look a third time, and if two brokers approach the same carrier for you, the resulting broker conflict can stall both submissions. Remarket in sequence.
| Market type | Best for | Trade-offs |
|---|---|---|
| The market that declined you on controls | Control declines now fixed | They already know the file. Approach once, with the full evidence pack. |
| Scan-driven MGAs (e.g., Coalition, At-Bay, Cowbell, where they operate) | Small and lower mid-market firms with clean scans | Fast quotes. Availability varies by country. Strict on scan results. |
| Major carriers (e.g., Beazley, Chubb, AXA XL, AIG, Allianz, Zurich, Munich Re, Tokio Marine HCC, Hiscox) | Mid-size and large firms, multinational programs | Broader wording and incident response panels. More underwriting questions. |
| Lloyd's/London wholesale; surplus lines markets where they exist | Hard-to-place classes, prior incidents | Flexible on risk. Higher premiums and retentions. |
| Local insurers with reinsurance backing or fronting | Markets where local admission is required (common in parts of Latin America, the Gulf, Africa and India) | Satisfies local rules. Wording is often driven by the reinsurer. |
Program structure matters as much as market choice. A higher retention, a lower first-layer limit, or a ransomware sublimit with coinsurance (where you share a percentage of each ransomware loss) can make a borderline risk bindable this cycle. You can buy back limit at the next renewal once the controls have a track record. For most mid-size buyers coming off a decline, a smaller policy bound now beats a perfect one quoted never.
Negotiating Cyber Insurance Subjectivities You Can Meet
Expect a conditional quote. Subjectivities are conditions you must satisfy before binding (pre-bind) or within a set period after (post-bind). Typical examples: MFA rolled out to all remaining users within 30 days, EDR on the last server group within 60 days, or a completed restore test within 90 days.
Post-bind subjectivities are where buyers get hurt. Miss one and the carrier may limit, suspend or cancel cover, depending on the wording. The danger is believing a policy is in force while a breach unfolds. To protect yourself:
- Negotiate deadlines you can hit with margin. If your team says 30 days, ask for 60.
- Calendar every subjectivity with a named owner, and send proof of completion through your broker.
- Get written acknowledgment from the carrier that each condition is satisfied. Don't rely on silence.
- Read control warranties closely. Wording that requires controls "at all times" can turn one lapsed laptop into a coverage dispute. Ask your broker or coverage counsel whether softer wording is available.
Also look for exclusions or reduced cover for losses tied to known vulnerabilities left unpatched past a set number of days. Some carriers use this approach, and it sets how fast your patching must be once the policy is live.
The Day-60 Decision Rule: Bind, Restructure or Keep Building
By day 60 you should have one of three outcomes. Decide in advance how you'll respond to each, so you're not negotiating under time pressure.
- A quote with a retention you can absorb and subjectivities you can meet. Bind it. Don't hold out for better terms from a market that hasn't responded.
- Quotes only with a ransomware sublimit, coinsurance or a reduced limit. Bind if the remaining cover still meets your contractual and lender requirements. Then remarket in six to nine months, once the new controls have a clean history.
- Nothing bindable. Go back to the written decline reasons and find which gate is still open. Meanwhile, check whether your property or package policies include limited cyber cover, and put an incident response retainer in place so a breach coach and forensics firm are on call. Tell any customers whose contracts require cyber cover before they find out on their own.
Treat the cost of controls and the premium as one budget line. For most mid-size companies, the controls that get you back to a bindable quote also make a claim less likely. If your cyber insurance was declined, your first step this week is to email your broker for the written reasons and the carrier's scan findings. Everything else here depends on that list. For decisions on wording, warranties and incident disclosure, work with a licensed broker and coverage counsel in your jurisdiction.
Frequently asked questions
Do I have to disclose a previous cyber insurance decline on new applications?
If the application asks, and many do, answer truthfully. A misstatement can give the insurer grounds to deny a claim or rescind (cancel) the policy, and the rules vary by jurisdiction. Have your broker explain the context and include remediation evidence, which often defuses the disclosure.
How soon after fixing controls can we reapply?
You can resubmit as soon as you can evidence the fixes, but some underwriters want controls in place for 30 to 90 days before they give full credit. A dated deployment report and a clean rescan help close that gap. Ask the declining market what bedding-in period it expects.
Will our managed service provider's security controls count toward our application?
Yes, and they're scrutinized. If your MSP has privileged remote access to your environment, underwriters will ask about its MFA, access logging and own security posture. Get a written summary of the MSP's controls and include it in your evidence pack.
Is it realistic to go without cyber insurance after a decline?
Some companies do for a period, but check customer contracts, lender covenants and sector regulations first, since many require cyber cover. Going uninsured also means paying for incident response, legal and notification costs yourself. An incident response retainer is a sensible stopgap while you remediate.
What happens if we miss a post-bind subjectivity deadline?
It depends on the policy wording. Consequences range from a reduced sublimit to suspension or cancellation of cover. If you can see you'll miss a deadline, ask your broker for a written extension before it passes. Carriers are generally more flexible before the date than after.
Will our premium be much higher after a decline?
Often the first bound policy after a decline costs more or carries a higher retention than a clean renewal, especially through wholesale or surplus markets. The increase depends on your industry, revenue, region and how convincing your remediation evidence is. Many buyers see terms improve at the following renewal once the controls have a track record.
Written by the Sentinel Underwrite Ops editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.