Building an Incident Response Plan Your Cyber Insurer Will Accept: A 10-Step Playbook
Underwriters no longer accept "yes, we have an IR plan." This ten-step sequence maps each part of your plan to the questions carriers ask and the evidence they expect to see at renewal.
What underwriters are really testing when they ask for your IR plan
Most renewal questionnaires ask some version of the same question: do you have a documented incident response plan, and has it been tested in the last 12 months? A checked box used to be enough. Many carriers now follow up with ransomware supplements asking who can shut down systems, whether the plan exists offline, and whether you can show evidence of a recent exercise. A plan downloaded from a template site rarely survives those follow-ups. It doesn't name your insurer, your claims hotline or your panel firms, and it says nothing about who decides on an extortion demand.
An incident response plan for cyber insurance has two jobs. It has to guide your team through the first 72 hours of an incident. It also has to show an underwriter that a loss will be contained quickly and that the claim will be handled the way the policy requires. A plan that does only the first job can still cost you money: a team that hires its own forensics firm before calling the insurer may find part of that spend disputed.
The ten steps below are built in order, and each answers a specific underwriting question. Use the table as a checklist.
| Step | What you build | Underwriting question it answers | Evidence to keep |
|---|---|---|---|
| 1 | Scope and severity tiers | Do you know what counts as an incident? | Approved severity matrix |
| 2 | Decision roles and authority | Who can isolate systems or engage on extortion? | Signed role table with deputies |
| 3 | Contact sheet | Can you reach decision makers out of hours? | Dated contact list, tested quarterly |
| 4 | Insurer notification procedure | Will you give notice in time and get consent before spending? | Policy extract, hotline number, notice steps |
| 5 | Breach coach and panel vendors | Will you use approved responders? | Panel list, pre-agreed engagement terms |
| 6 | Regulatory notification map | Can you meet legal deadlines in each country? | Jurisdiction table reviewed by counsel |
| 7 | Offline and out-of-band copies | Can you respond if email and the network are down? | Storage locations, alternate channels |
| 8 | Tabletop exercise | Has the plan been tested? | After-action report, attendance, findings |
| 9 | Remediation tracking | Did you fix what the test exposed? | Findings register with owners and dates |
| 10 | Annual review tied to renewal | Is the plan current? | Version history, approval record |
Steps 1 to 3: severity tiers, decision authority and a contact sheet that works at 2 a.m.
Step 1: Define scope and severity. Write three or four tiers with concrete triggers. Tier 1 might be a single compromised mailbox with no sign of data access. Tier 3 might be encryption on more than one server, confirmed exfiltration, or an extortion message. For each tier, state who gets notified and whether insurer notice is required. Underwriters want a ransomware event to escalate automatically, not after a day of internal debate.
Step 2: Assign decision roles, with named deputies. This is where most plans are weakest. At a minimum, name:
- An incident commander who runs the response (often the CISO or head of IT)
- An executive decision owner with authority to take systems offline, approve emergency spend and halt operations (usually the CEO or COO)
- A legal lead who engages outside counsel and controls privilege
- A finance lead who handles insurer communication on costs and any payment questions
- A communications lead for staff, customers and media
Spell out who may engage with an extortion demand and who may not. Paying a ransom raises sanctions questions in many places, since the US, UK and EU all maintain sanctions regimes that can apply, and a growing number of countries require payments or demands to be reported. Australia, for example, has introduced reporting obligations for certain businesses. Check current rules with counsel. Your plan should state that no one engages with threat actors without the legal lead, the breach coach and the insurer involved.
Step 3: Build a contact sheet and test it. List personal mobile numbers, a backup for every role, and your insurer's claims hotline. Say a 300-person firm has offices in London, Dubai and Singapore. It should name an on-call deputy in each region so the first decision doesn't wait eight hours for someone to wake up. Test-call the list every quarter and date the sheet.
Steps 4 to 6: insurer notice, your breach coach and regulatory clocks
Step 4: Write the insurer notification procedure from the policy wording. Pull the notice clause, the consent-to-costs clause and the claims hotline straight from your policy and paste them into the plan. Cyber policies commonly require notice "as soon as practicable" or within a fixed period, and many require the insurer's prior written consent before you incur response costs, sometimes with a short emergency window. Make the first call to the hotline a Tier 2 or 3 action item, logged with the time and the name of the person you spoke to. Have your broker confirm your reading of the clause.
Step 5: Pre-arrange your breach coach and panel vendors. A breach coach is an outside lawyer, usually drawn from the insurer's panel, who coordinates the response, retains forensics firms through counsel to support legal privilege where local law recognizes it, and manages notification decisions. Privilege differs by country, and common-law and civil-law systems often treat it differently, so ask your breach coach how it applies where you operate.
Your plan should list the insurer's approved panel for forensics, legal, public relations, data restoration and extortion negotiation. If you want an incident response retainer outside the panel, get the insurer's written approval at binding or renewal, not mid-incident. Retainers typically run from roughly $10,000 to $50,000 a year in prepaid hours for mid-size firms. These are typical 2026 market ranges that vary by contract and region, so confirm pricing with vendors. Some policies include discounted or bundled pre-breach services, so check before you buy separately.
Step 6: Map your regulatory notification clocks. Underwriters ask because missed deadlines create fines and coverage disputes. The examples below show how far deadlines vary. Rules change, so verify each one before you rely on it.
| Regime | Typical deadline |
|---|---|
| EU and UK GDPR | 72 hours to the regulator after becoming aware of a reportable breach |
| EU NIS2 (in-scope entities) | 24-hour early warning, 72-hour incident notification |
| India CERT-In directions | 6 hours from noticing a reportable incident |
| Singapore PDPA | 3 calendar days after assessing a breach as notifiable |
| Brazil LGPD | Short, regulator-set deadline (currently about 3 working days) |
| US public companies (SEC) | 4 business days after determining materiality |
Sector rules (finance, health, telecoms) and US state laws add more. Treat this table as a starting point and have counsel in each jurisdiction confirm the list for your company.
Steps 7 and 8: offline copies and a tabletop that produces evidence
Step 7: Keep the plan reachable when your systems aren't. If ransomware encrypts your file shares and takes down single sign-on, a plan stored on SharePoint is useless. Keep at least three copies: printed binders with the incident commander and executive owner, an encrypted copy on a device that isn't on the corporate network, and a copy in a separate cloud tenant the response team can reach. Name an out-of-band channel, such as a pre-created Signal or WhatsApp group or a bridge line that doesn't depend on corporate email. Ransomware supplements often ask about this directly.
Step 8: Run a tabletop exercise and keep the evidence. A 2- to 4-hour scenario session with the decision owners from Step 2 is what underwriters mean by "tested." Pick a realistic scenario. Double-extortion ransomware that starts at a third-party IT provider is a good default. Build in the moments that matter for the policy. When does someone call the hotline? Who approves the forensics engagement? What happens when the threat actor demands payment within 48 hours?
The evidence matters as much as the session. Keep:
- The scenario document and the date
- An attendance list with roles
- An after-action report listing gaps, owners and target dates
- Sign-off from the executive decision owner
Externally facilitated tabletops typically cost roughly $5,000 to $25,000, depending on scope, number of locations and whether a technical exercise is included. These are typical 2026 market ranges, and local pricing differs. Some brokers and insurers offer facilitated sessions with the policy. For a 40-person company, an internally run session using a published scenario is usually enough. For a multinational with board-level exposure, pay for an external facilitator, because underwriters tend to give independent evidence more weight.
Steps 9 and 10: closing findings and locking the review to your renewal date
Step 9: Track remediation like an audit finding. Suppose a tabletop reveals that a backup restore takes four days, and nothing is fixed by renewal. That can work against you. Keep a findings register with an owner, a due date and a status for each gap. A short list of closed items, such as "out-of-band channel created, deputy CFO added to extortion approvals," reassures an underwriter even if a few longer projects are still open.
Step 10: Set an annual review cycle anchored to renewal. Schedule the full review and tabletop 90 to 120 days before the policy renews. That leaves time to close findings and hand your broker a clean evidence pack. Trigger an off-cycle update whenever you change insurers, the panel changes, a key role holder leaves, you enter a new country, or you have a real incident. Record version numbers and approval dates in the document itself.
Red flags underwriters notice
- No insurer name, policy number or hotline in the plan
- A single person in every role with no deputies
- A last-tested date older than 12 months, or no after-action report
- Non-panel vendors named with no pre-approval
- Only one copy of the plan, stored on the corporate network
- Notification deadlines for only one country when you operate in several
Your decision rule for this renewal: if you can't hand your broker a dated plan, a signed role table, panel contacts and a tabletop after-action report within one business day, start with Steps 2, 4 and 8. Those three answer most of what underwriters ask, and most teams can finish them in four to six weeks.
Frequently asked questions
Will my insurer refuse cover if I don't have a documented incident response plan?
It depends on the carrier and the market. Some insurers decline or restrict ransomware cover without a tested plan. Others quote a higher premium or retention, or add exclusions. Your broker can tell you how the carriers you're approaching treat the question.
What exactly is a breach coach, and do I have to use the insurer's?
A breach coach is an outside lawyer who coordinates the response, retains forensics and other vendors, and advises on notification. Most policies strongly favor or require panel counsel. Using your own firm usually needs prior written consent, and without it some costs may not be reimbursed. Agree on any exceptions at binding, not during an incident.
How often should we run a cyber insurance tabletop exercise?
At least once a year is the common underwriting expectation, timed a few months before renewal so findings can be closed. Larger or highly regulated companies often run an executive session and a separate technical exercise. Rerun one after any major change to your insurer, panel or leadership team.
Can we use our existing incident response retainer if the firm isn't on the insurer's panel?
Often yes, but only with the insurer's written approval, ideally recorded in the policy or an endorsement. Without it, the insurer may reimburse at panel rates or dispute the costs. Raise it with your broker during renewal negotiations.
What evidence should we give the underwriter about our IR plan?
A current, dated plan or summary, the role table with deputies, the insurer notification procedure, and the most recent tabletop after-action report with remediation status. Some underwriters only want confirmation and a summary. Others ask for documents. Keep a ready-to-send pack so you aren't rebuilding it every year.
Do regulatory breach-notification deadlines differ enough to need separate plan sections?
Yes, if you operate in more than one country. Deadlines range from hours, as under India's CERT-In directions, to several days elsewhere, and sector rules add more. A single jurisdiction table in the plan, confirmed by qualified local counsel, is usually enough to keep the response on track.
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.