Guide

The 2026 Cyber-Insurance Checklist: Do You Qualify?

Gone are the days when you could just fill out a form and buy Cyber Insurance. In 2026, insurers are bleeding money from ransomware claims, and they have tightened their standards dramatically.

By SecureBusinessHub Editorial, International cybersecurity desk — 2025-08-20 · 8 min read

Filing a simple form and getting cyber insurance is over. Insurers have lost too much money on ransomware claims in the SMB sector and have tightened their requirements significantly.

If these controls aren't in place, they'll deny your application or deny your claim after a breach.

1. MFA everywhere

No MFA on email and remote access means you're uninsurable. Full stop.

2. Offline backups

Insurers want evidence that if your network gets encrypted, you can recover without paying. That means offline or immutable backups not reachable by an attacker with admin access.

3. Patch management logs

Can you prove you applied critical patches within 30 days of release? If not, underwriters will call it negligence and decline the claim.

4. Employee training records

Did the employee who clicked the malicious link complete phishing awareness training in the last 12 months? You need records.

The forensics requirement

A clause that trips up many SMBs is the forensic mandate. After a breach, your insurer will likely require you to use one of their pre-approved forensic firms. If you start fixing servers before investigators arrive, you may inadvertently void your policy, leaving you to cover data recovery costs and legal fees out of pocket.

Software warranties vs. cyber insurance

Your EDR vendor's "$1M Ransomware Warranty" is not the same as cyber insurance. These warranties are hard to claim against and typically only cover the cost of the software itself. They don't cover business interruption, regulatory fines, or the PR fallout after a major leak.

Learn how to build a compliant infrastructure in our SMBs Security Checklist.

Cyber insurance is a contract that says they'll pay if you did your homework. Make sure you did.

NIS2 requirements: the second regime to know about

Data protection law is not the only European regime a business gets asked about. The NIS2 directive sets baseline cybersecurity and incident-reporting obligations for organisations in a defined list of sectors, and it is the source of most of the security questions that now arrive attached to contracts. The two regimes cover different ground: data protection law governs personal data and what people can ask you to do with it, while the NIS2 requirements govern the security and resilience of network and information systems, whether or not personal data is involved. A single incident can engage both, on separate clocks, to separate authorities.

The directive applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet above ten million euros. That size rule puts most small businesses outside its direct scope, and the honest answer for a ten-person company is usually that the directive does not regulate it. What the size rule does not do is keep the requirements away, because one of them is supply chain security: organisations inside scope are expected to consider the security practices of their direct suppliers, and the way that expectation shows up in the world is as a questionnaire in your inbox.

The measures the directive names are a reasonable checklist for any business, which is why they are worth knowing even when they do not apply to you directly. They cover risk analysis and written security policies, incident handling, business continuity and backups, supply chain security, secure development and vulnerability handling, basic cyber hygiene and training including for management, encryption and access control policies, and multi-factor authentication. Reporting is staged and fast for the organisations it covers: an early warning within twenty-four hours of becoming aware of a significant incident, a fuller notification within seventy-two hours, and a final report within one month.

Because the directive is national law in each member state rather than a single rulebook, the details of scope, thresholds and reporting differ by country. For a fuller explanation of the instrument itself, see our guide to what the NIS2 directive is, and for the supplier side of the supply chain obligation, our walkthrough of vendor risk assessment. The reporting clocks that run alongside data protection deadlines are covered in data breach notification requirements.

Frequently asked questions

Does NIS2 apply to a small business?

NIS2 generally applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet total above ten million euros. Most smaller businesses fall outside its direct scope, unless a member state has specifically designated them or they sit in one of the size-independent categories such as DNS service providers or trust service providers. Being outside scope does not stop the directive reaching you through customers who are inside it.

What is the difference between GDPR and NIS2?

GDPR governs personal data: what you may collect, why you may hold it, and what rights people have over it. NIS2 governs the security and resilience of network and information systems in specific sectors, whether or not personal data is involved. One incident can engage both regimes at once, on separate reporting clocks and to separate authorities.

How long do you have to report a data breach?

Under the European model, a personal data breach is reported to the supervisory authority without undue delay and, where feasible, within seventy-two hours of becoming aware of it, and affected individuals are told without undue delay where the risk to them is high. Organisations in scope of NIS2 carry a separate obligation: an early warning within twenty-four hours, a fuller notification within seventy-two hours, and a final report within one month.

Does a small business need a data protection officer?

Under GDPR a data protection officer is required where the organisation is a public authority, where its core activities involve regular and systematic monitoring of people on a large scale, or where its core activities involve large-scale processing of special category or criminal offence data. Most small businesses meet none of those tests and are not required to appoint one, though naming someone internally as the contact for privacy questions is worth doing regardless.

What should a small business do when a client's security questionnaire asks about NIS2?

Answer what you actually do rather than what you think the client wants to hear. The questions usually cover written security policies, incident handling and how fast you would notify them, multi-factor authentication, access control when staff join and leave, backup and recovery arrangements, and which of your own subprocessors touch their data. Gaps are common, and disclosing one with a date for closing it lands far better than an answer that does not survive the follow-up question.

Do these rules reach a business based outside the EU?

They can. GDPR reaches organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour, and other regions have their own regimes with their own triggers. NIS2 obligations follow the sectors and the member states that transpose it, but its supply chain expectations travel through contracts, which is how they reach suppliers anywhere in the world.