Guide · Canadian mutual insurers

Meeting OSFI B-13 with a lean IT team

What OSFI's Guideline B-13 and FSRA's IT risk guidance expect of a mutual insurer, which one applies to you, how fast you must report an incident, and how a small team can meet it. Then a 28-point checklist for management and the Board.

Go to the checklist Take the free IT Maturity Assessment

The short answer: which rules apply to your mutual

It depends on who licenses you. B-13 binds federally regulated insurers. Mutuals incorporated in Ontario answer to FSRA, whose IT risk guidance FSRA itself describes as aligned with B-13. Privacy law applies to everyone.

Federally regulated

OSFI B-13

B-13 sets OSFI's expectations for technology and cyber risk, in effect since January 1, 2024. Technology and cyber incidents go to OSFI within 24 hours. Third-party arrangements fall under Guideline B-10.

Ontario-incorporated

FSRA GR0016INT

FSRA's IT Risk Management Guidance (in effect since April 1, 2024) is its interpretation of the Insurance Act: insurers must achieve its outcomes and notify FSRA of a material IT incident within 72 hours.

Every mutual

Privacy law

Under PIPEDA, a breach that creates a real risk of significant harm must be reported to the Privacy Commissioner and to the people affected, and every breach must be recorded for 24 months.

Outside Ontario, FSRA points to similar guidance from other regulators, such as the BC Financial Services Authority's Information Security Guideline and the AMF's guideline on information and communications technology risk in Québec. This guide is general information, not legal or regulatory advice.

Source 1 · OSFI

B-13 in plain language

OSFI published B-13 on July 31, 2022, and it took effect on January 1, 2024. It is short and outcome-based: three domains, each with an expected outcome, and 17 principles. OSFI says there is no one-size-fits-all approach, and that the guideline should be applied from a risk-based perspective.

1. Governance and risk management

Clear accountability, structures, strategy and a risk framework.

  • Senior management assigns accountability and resources (P1)
  • A technology and cyber strategy aligned with the business (P2)
  • A risk management framework, continuously improved (P3)

2. Technology operations and resilience

A stable, scalable, resilient environment, kept current.

  • Architecture (P4) and an up-to-date asset inventory (P5)
  • Project governance (P6), secure development and acquisition (P7)
  • Change control (P8) and timely patching (P9)
  • Incident and problem management (P10), service monitoring (P11)
  • Disaster recovery, tested against scenarios (P12, P13)

3. Cyber security

Protect the confidentiality, integrity and availability of technology assets.

  • Identify exploitable weaknesses (P14)
  • Layered preventive controls (P15)
  • Continuous detection and logging (P16)
  • Respond, recover and learn, including from third-party incidents (P17)

The principles above are summarized; read the full guideline for OSFI's wording. B-13 works alongside OSFI's incident reporting advisory and Guideline B-10 on third-party risk.

Source 2 · FSRA

FSRA's seven practices for Ontario-incorporated insurers

For insurers incorporated in Ontario, FSRA's IT Risk Management Guidance is an interpretation of the Insurance Act, not just advice: insurers must achieve the desired outcomes of each practice, and FSRA says insurers that cannot demonstrate compliance may face supervisory or enforcement action. Accountability for IT risk rests with the Board.

  1. Governance. A Board-approved IT strategy and risk approach, enough resources, and a clear, Board-approved definition of a material IT incident.
  2. Risk management. A Board-approved IT risk appetite with tolerances and limits; policies to identify, mitigate, monitor and respond; regular reporting to the Board; enterprise-wide awareness training.
  3. Data management. Data classified with clear owners; access controlled through multi-factor authentication, segregation of duties and least privilege; data controls tested; PIPEDA compliance.
  4. Outsourcing. The Board keeps accountability. Assess providers before contracting, rate their criticality, include audit and information rights, require incident notice, test their compliance, and plan an exit.
  5. Incident preparedness. A documented incident process with defined roles, periodic table-top exercises that include third parties, independent review, escalation to the Board, and root-cause analysis.
  6. Continuity and resilience. An inventory of IT assets with criticality, replacement before end of support, service level agreements, change management, and a tested disaster recovery plan aligned with the business continuity plan.
  7. Notification of material IT risk incidents. Clear thresholds, an assigned owner, and notice to FSRA no later than 72 hours after determining an IT risk incident has occurred.

FSRA's Operational Risk and Resilience guidance (effective June 8, 2026) adds four principles (governance, operational risk identification and assessment, operational risk management, and resilience) and uses them, with the IT guidance, to assess how insurers manage IT and cyber risk.

Incident reporting

Three clocks that can start with one incident

The practical lesson: decide in advance who makes the call, what "material" means for your mutual, and who drafts each notice. The first hours of an incident are the wrong time to work out which regulator you answer to.

ABISOL practice

How a lean mutual can meet it

Both regulators allow for size. FSRA describes outcomes rather than methods, to be achieved in a way that suits the size and nature of the business, and says smaller insurers can keep oversight independent through separation of duties and independent review. Here is the order we would work in. This is our practice, not a regulatory requirement.

  • Name the accountable executive, then give the Board one page. A short framework, a few appetite statements, and a definition of a material incident the Board approves.
  • Build the asset inventory and the end-of-life list first. Patching, recovery, vendor oversight and Board reporting all depend on knowing what you run and what is no longer supported.
  • Bring the MSP and core-system vendor inside the framework. Audit rights, incident notice and an exit plan in the contracts, and a seat at your exercises.
  • Run a table-top exercise that ends with the regulator notice drafted. 24 hours for OSFI or 72 for FSRA is short when nobody has done it before.
  • Report to the Board on a small, steady set of measures. Open high risks, end-of-life systems, patch currency, recovery test results, incidents and provider issues.

This is the work ABISOL does as a fractional CISO or fractional CIO for mutuals: ABISOL builds the framework with your team, reports to your Board and oversees your providers, while accountability stays where the regulators expect it. See how ABISOL works with mutual insurers.

The checklist

28 points for management and the Board

Each point names its source. OSFI B-13 and OSFI apply to federally regulated insurers, FSRA to Ontario-incorporated insurers, and PIPEDA to everyone. Your ticks are saved in this browser only.

0 of 28 in place
Governance and the Board
  • OSFI B-13FSRA
  • OSFI B-13FSRA
  • FSRA
  • OSFI B-13FSRA
  • FSRA
  • FSRA
  • FSRA
Technology operations and resilience
  • OSFI B-13FSRA
  • FSRA
  • OSFI B-13FSRA
  • OSFI B-13
  • OSFI B-13
  • OSFI B-13FSRA
  • OSFI B-13FSRA
  • OSFI B-13FSRA
Cyber security and data
  • OSFI B-13
  • OSFI B-13FSRA
  • FSRA
  • OSFI B-13
Third parties (MSP, core-system vendor, cloud)
  • FSRAOSFI
  • FSRA
  • FSRA
  • FSRA
Incidents and reporting
  • OSFI B-13FSRA
  • FSRA
  • FSRAOSFI
  • FSRAOSFI B-13
  • PIPEDA

Want an outside view of where you stand?

The free IT Maturity & Cloud Migration Assessment covers governance, operations, vendors and resilience in about 30 minutes. For a Board-ready view, book the complimentary Technology & Cyber Health Check with ABISOL.

Book an Executive Consultation

Questions mutual insurers ask

Does OSFI B-13 apply to our mutual?

It depends on who regulates you. B-13 applies to federally regulated financial institutions, including federally regulated property and casualty insurers. A mutual incorporated in Ontario and licensed by FSRA answers to FSRA, whose IT Risk Management Guidance applies instead. FSRA states that its practices are aligned with OSFI's guideline, so B-13 is a sound benchmark either way. Mutuals in other provinces should check their own regulator's guidance.

How fast do we have to report a cyber incident?

Federally regulated: to OSFI within 24 hours, or sooner if possible. Ontario-incorporated: to FSRA as soon as reasonable, and no later than 72 hours after determining that an IT risk incident has occurred, if it is material. For privacy breaches under PIPEDA: to the Privacy Commissioner as soon as feasible when there is a real risk of significant harm. One incident can trigger all of these, and a cyber insurance claim is itself on both OSFI's and FSRA's lists of indicators.

We are a small mutual with one or two IT staff. Is this realistic?

Yes, if it is sized to you. OSFI says there is no one-size-fits-all approach to technology and cyber risk. FSRA's guidance describes outcomes, not methods, so they can be met in a way suited to the size and nature of the business, and its resilience guidance says smaller insurers can achieve independence through separation of duties and independent review.

Our MSP and core-system vendor run most of our technology. Is that enough?

No. Outsourcing moves the work, not the accountability. FSRA expects the Board to retain accountability for outsourced functions, and OSFI's Guideline B-10 says the institution retains accountability for services outsourced to a third party. You need contracts with audit rights, incident notice and exit plans, and a way to check the provider's controls.

Do we need a full-time CISO?

None of these documents requires one. FSRA expects responsibility for IT risk to sit with people of sufficient seniority and expertise, and the Board to remain accountable. One practical model for a lean mutual is an internal accountable executive supported by an experienced fractional CIO or CISO who builds the framework, reports to the Board and oversees the MSP. That is ABISOL's model, not a regulatory requirement.

What does FSRA's newer operational resilience guidance add?

FSRA's Operational Risk and Resilience guidance for Ontario-incorporated insurers took effect on June 8, 2026. It is approach guidance built on four principles: governance, operational risk identification and assessment, operational risk management, and resilience. FSRA uses it, together with its IT Risk Management Guidance, to assess how insurers manage IT and cyber risk. Its practices are not mandatory, but FSRA says they can reflect whether an insurer has met its obligations.