Who runs a cyber incident response should be settled at inception, not mid-attack

Clients still ring their broker before the insurer’s hotline, and wordings differ on when excess-free cover starts
Who runs a cyber incident response should be settled at inception, not mid-attack
INSURANCE NEWS
By Bryony Garlick
18 Nov 2026

When a business discovers a cyber incident, the first call is often to its IT provider. The insurer’s incident hotline frequently comes after a call to the broker, even when the client has been told exactly what to do. 

Even after an hour-long onboarding call covering step by step what to do and which number to ring, clients still turn to their broker first, said Caspar Rogers (pictured), senior cyber broker at Assured. “We still see time and time again the client calls us before calling the insurer’s hotline number,” he said. 

Sometimes clients forget. More often they are unsure whether the event justifies a full incident response, or they worry the insurer might penalise them for notifying and running up costs with response vendors. 

Most policies Assured is placing include a nil retention on incident response for roughly the first 48 to 72 hours, to encourage clients to bring in the insurer’s panel vendors early. 

Wordings differ on when that window opens. Some insurers start it at discovery and others at the call to the hotline, and Rogers said brokers need to flag the difference to clients. Where the clock runs from discovery, time spent ringing round before calling the hotline comes out of the excess-free period. 

Legal leads, but the broker holds people to account 

The client is always the final decision maker, but often lack the expertise or the full facts in-house to make the right calls, so they lean on their IT provider, the insurer’s panel vendors and their broker. 

In his experience, legal breach counsel tends to lead the overall response, alongside separate digital forensics and incident response (DFIR) and PR workstreams. One reason is that triage run through lawyers can bring communications about the incident under legal privilege, though Rogers noted that privilege has yet to be properly tested. The client’s IT provider, often a local managed service provider for smaller firms, typically handles the first emergency call. Ideally it then steps back once panel vendors take over. 

That leaves the broker as the escalation point. “It’s important to have the broker on hand to basically make sure that everyone’s doing their job to the best of their ability and holding people to account where they’re not,” Rogers said. 

Why the client’s own IT firm causes friction 

Clients who want their own IT firm to handle the response are one of the biggest sources of claims friction. Insurers will cover pre-approved panel vendors. Anyone else triggers “some really difficult conversations that have to happen at the worst possible time, which is when you’re having an ongoing incident.” 

Clients argue that their own provider knows their systems, but Rogers said that rarely makes a difference. DFIR work involves detailed log analysis and knowledge of how specific threat actors operate, which local providers often lack. Rates are a second sticking point, because panel vendors offer insurers portfolio rates in return for volume. The third is conflict of interest. If the provider has been acting as the client’s outsourced security operations centre (SOC) and a major incident still happened, insurers will usually not let it lead the forensics, because that would amount to “marking their own homework”. 

Client and insurer usually want the same outcome, Rogers said: the lowest ultimate cost and the fastest return to operating. His advice is to agree rates and vet any preferred provider’s expertise before the policy goes on cover, and not to let the SOC run the post-incident investigation. 

Who a vendor answers to also matters as insurers buy into response firms. AXA XL agreed in August to take its stake in S-RM, a London-based cyber security consultancy, from around 49% to full ownership. Rogers does not see insurer ownership as a major issue, provided strict information barriers are in place. He said clients should understand who the vendor acts for and what it shares with the insurer, and brokers should be ready to push for a different DFIR firm if the client has material concerns. 

When the IT provider is the way in 

The leadership question is at its sharpest when the attack comes through the IT provider’s own environment. “It’s abundantly clear that you can’t then have that IT provider doing any of the investigation or any of the response whatsoever,” Rogers said. 

The provider will still need to share what it has collected and how the attackers got in, and it may already have started responding. Rogers would want it kept at arm’s length from that point, with an external DFIR firm brought in as quickly as possible to lead the forensics and check anything the provider has done or said. Insurers sometimes subrogate against the provider in these cases. 

For the broker, the job is to make sure client and insurer both understand the costs and vendor engagements. That includes reviewing scopes and statements of work with the client so that no effort is duplicated. 

Much of what shapes a cyber claim is settled before any incident occurs: the vendors, the rates and the notification steps a broker agrees with the client at inception. 

Related Stories
Free newsletter

We'll keep you up-to-date with the latest breaking news, cutting edge opinion, and expert analysis affecting both your business and the industry as whole.

Free newsletter

Our daily newsletter is FREE and keeps you up - to - date with the world of Insurance. Please complete the form below and click on subscribe for daily newsletters from IB UK.