Back to Blog
Breach November 9, 2026 8 min read

Cyber Insurance in Canada: What Your Policy Quietly Requires You to Have

The application form is not paperwork. It is a set of representations, and the day you need the policy is the day someone checks whether they were true.

By Aparna Netheti

Cyber Insurance in Canada: What Your Policy Quietly Requires You to Have

Cyber insurance in Canada now comes with control requirements written into the application and, increasingly, into the policy conditions. The coverage is real and worth having. The risk is that the answers someone gave on the application eighteen months ago no longer describe your organization, and nobody has checked since.

This tends to surface at the worst moment: after an incident, when the insurer compares the application with what was really in place. The controls are rarely absent because anyone was careless; they drift, and drift is invisible without a review.

What do insurers actually ask about?

The list has converged over the last few years. Expect questions in these areas, with more precision than you might expect.

AreaWhat is typically asked
Multi-factor authenticationOn email, remote access, and privileged and administrative accounts
BackupsFrequency, whether they are offline or immutable, and when a restore was last tested
Endpoint protectionDetection and response coverage, and the percentage of devices covered
PatchingTimeframes for critical vulnerabilities
Access controlPrivileged account management and removal on departure
Email securityFiltering, and controls against payment redirection fraud
TrainingFrequency and whether phishing simulation occurs
Incident responseWhether a plan exists and whether it has been tested
Third partiesVendor due diligence and contractual protections

Two of these carry outsized weight. Multi-factor authentication on privileged accounts is close to a threshold requirement with many carriers now, and a tested restore is what separates an insurable backup posture from a hopeful one. "We have backups" and "we restored one in March and it worked" are answered by the same question and are not the same answer.

Where do claims actually get denied or reduced?

Not usually on obscure exclusions. On the basics.

A representation that was true and stopped being true. You attested that MFA was enforced on all administrative accounts. Six months later a service account was exempted to unblock an integration, and nobody recorded it. That exemption is the one the forensic report will find.

Late notice. Policies impose notification obligations with short windows, and the clock often starts at discovery rather than confirmation. Waiting until you understand the incident before telling the insurer is a natural instinct and a costly one.

Unauthorised response spend. Many policies require you to use panel counsel and panel forensics, or to get consent before incurring costs. Hiring your own firm on day one can put those costs outside coverage.

No evidence the control operated. Even where the control existed, you may need to show it was operating during the relevant period. This is the same evidence problem auditors create, and the same solution applies: dated artefacts produced as controls run, not assembled afterwards. What auditors actually ask for covers the artefacts.

How do you keep the application honest over time?

Treat it as a control set with an owner and a renewal review, because that is what it is.

Copy every attestation you made into your control register, verbatim, with the date you made it. Then, before each renewal, verify each one rather than re-signing last year's answers. Any control that has changed gets disclosed and either fixed before renewal or accurately restated. Insurers price honest answers; they decline dishonest ones after the fact, which is far worse.

Add one trigger between renewals: any change that would alter an answer gets recorded when it happens. The service account exemption above is a five-minute note at the time and an uninsured incident eighteen months later.

Does insurance change what you should build?

It sharpens the priorities rather than changing them, which is genuinely useful for a small company.

The controls insurers ask about are close to the controls that reduce actual loss, because carriers price from claims data. If you are deciding where to spend a limited security budget, the application form is a reasonable proxy for what causes expensive incidents in companies your size. That is a better guide than most frameworks, which are written for a wider range of organizations.

It does not replace the compliance programme. Insurance covers financial consequences; it does not discharge a reporting obligation to a regulator or to affected individuals, and it does not repair the relationship with a customer whose data you lost. Keep the two efforts connected but do not let the insurer's checklist become your entire programme.

For the incident decisions that run in parallel with the insurance notification, incident, breach, or neither sets out the triage.

This is general information, not legal advice, and not insurance advice. Read your own policy and talk to your broker.

Valdra holds the control attestations and their evidence alongside the rest of the programme, so the answers you give an insurer at renewal reflect the state of the controls rather than last year's form.

Frequently asked questions

What controls do Canadian cyber insurers ask about?+

Multi-factor authentication on email, remote access, and privileged accounts; backup frequency and whether a restore was recently tested; endpoint detection coverage; patching timeframes; privileged access management; email security controls; training and phishing simulation; a tested incident response plan; and vendor due diligence.

Why do cyber insurance claims get denied?+

Usually on basics rather than obscure exclusions: a control you attested to that stopped being true, notice given later than the policy requires, response costs incurred without required consent or outside panel providers, or no evidence that a control was actually operating during the period.

When does the notification clock start on a cyber policy?+

Often at discovery rather than confirmation. Waiting until you fully understand an incident before notifying the insurer is a common and expensive instinct, because the policy window may already be running.

How do I keep insurance attestations accurate?+

Copy each attestation into your control register verbatim with its date, verify each one before renewal rather than re-signing last year's answers, and record any change that would alter an answer at the moment it happens rather than at the next renewal.

Does cyber insurance replace a compliance program?+

No. It covers financial consequences but does not discharge reporting obligations to a regulator or to affected individuals, and it does not repair a customer relationship. It is a useful priority signal because carriers price from claims data, but it should not become the entire programme.

cyber insurance Canadacyber liability policyinsurance controls attestationbreach coverage Canadaclaim denial cyberMFA insurance requirement

AI governance and privacy compliance, simplified.

Valdra helps Canadian companies govern AI and meet PIPEDA and Law 25, with records stored in Canada.

Try Valdra

Our own compliance

We run our own compliance programme inside Valdra, the product we sell, aligned to SOC 2 (Security criteria), ISO 27001 and ISO 42001. We do not yet have a SOC 2 report or an ISO certificate, and we do not claim certifications we do not hold.

Our Trust Centre

Measured by Valdra from our own assessments, not audited by a third party. Click the mark to open its verify page and see what it covers.