TruPoint
Book a discovery call
Book a discovery call
Compliance · cyber insurance

What does cyber insurance require from a small Canadian business?

TruPoint team
From the teamUpdated 8 min read

Most Canadian cyber-insurance applications now require five things: multi-factor authentication on every account, endpoint detection and response, backups that have been tested, centralised logging, and a written incident response plan. Missing any one of them typically means a higher premium, a lower limit, or a declined quote.

Key takeaways
01Multi-factor authentication is the single most common reason a quote is declined or repriced.
02Insurers treat partial MFA as no MFA, because an attacker only needs the account that was skipped.
03Antivirus is no longer accepted as endpoint protection; applications ask specifically for detection and response.
04A backup counts as tested only when a restore has been performed and the result recorded.
05An inaccurate answer on the application can reduce or void a claim later, which makes honesty the cheaper option.

Why did the questions get harder?

Insurers paid out heavily on ransomware claims between 2019 and 2023. The response was not simply higher premiums. It was underwriting that asks for specific technical controls and expects evidence they were in place.

For a business with a small IT function, this is a change in kind rather than degree. The application is no longer a formality signed by an office manager. It is a technical questionnaire with consequences attached to each answer.

What controls does an insurer actually ask for?

The wording varies by carrier and broker, but the substance is consistent. Below is what appears on almost every Canadian application we have reviewed.

The five recurring requirements
ControlWhat is being askedWhat usually fails
Multi-factor authenticationMFA on email, remote access, administrative accounts and any externally reachable systemA service account or an executive exemption left in place
Endpoint detection and responseEDR with monitoring and the ability to contain a compromised deviceTraditional antivirus with nobody watching the alerts
Tested backupsBackups held separately from production, with a restore performed and recordedBackups exist, but no restore has ever been attempted
Centralised loggingLogs collected off the device and retained, so an investigation is possibleLogs stay on the machine that was encrypted
Incident response planA written plan naming who does what, with contact detailsNo plan, or one written for a company that no longer exists

Sector-specific questions are added on top of these, particularly for firms holding financial or health information.

How much does non-compliance cost?

The direct cost is the premium. The larger cost is coverage that fails when you need it, because an answer on the application did not match reality.

5Controls that appear on nearly every Canadian application.
0Partial credit given for MFA on most accounts.
WeeksTypical time to close a gap list, once it is written down.
The practical risk

If a claim is investigated and a control you attested to was not in place, the insurer can reduce or deny it. This is the scenario businesses do not plan for, because the application is signed months before anything happens.

What does a realistic remediation look like?

For most environments the list is short. The work is usually configuration rather than purchase, and it is measured in weeks.

Scenario oneA 24-person insurance brokerage, renewal in six weeks
Starting pointMFA on email only. Antivirus on endpoints. Backups to a local drive, never restored. No written plan.
Gap listMFA on remote access and admin accounts. Replace antivirus with EDR. Add an offsite backup copy and perform a restore. Write and circulate an incident plan.
EffortAbout three weeks, mostly configuration in tools they already licensed.
OutcomeAll five questions answerable truthfully at renewal, with evidence attached.
Scenario twoA 9-person accounting practice applying for the first time
Starting pointMicrosoft 365 Business Premium licensed but largely unconfigured. No EDR. QuickBooks on a local server.
Gap listTurn on conditional access and MFA everywhere. Enable Defender properly. Move QuickBooks to hosted with tested backups. Document the plan.
EffortFour to five weeks, with no new licence purchases needed.
OutcomeInsurable, and materially harder to compromise as a side effect.

Is it worth getting help with the application?

If you can answer all five questions yes, with evidence, no. If you cannot, the useful move is to get the gap list written down before the application is submitted, because remediation before submission is cheaper than a repriced renewal afterwards.

A gap assessment produces that list. Ours maps each item to the question it answers, so the document is directly usable at renewal. We describe the process on the TruCompliance™ page.

Frequently asked questions

Does cyber insurance require SOC 2 or ISO 27001?

Generally no. Certification is usually a customer requirement rather than an insurance one. Insurers ask about specific controls, not frameworks.

Will MFA on email alone satisfy an insurer?

No. Applications ask about remote access and administrative accounts separately, and a gap in either is treated as a failure of the control.

What counts as a tested backup?

A restore that was actually performed, on a date, with the outcome recorded. An automated success message from the backup software is not the same thing.

How long is a gap assessment valid?

Practically, about a year, or until your environment changes materially. Continuous evidence collection avoids the question entirely.

Can we get covered while gaps remain open?

Sometimes, at a higher premium or a lower limit, and occasionally with a remediation deadline written into the policy. It is better to close the gaps first if the renewal date allows it.

Who should own the application inside a small business?

Whoever can verify the answers technically. In practice that means the IT provider prepares the evidence and the owner or partner signs it.

Keep reading