OSFI Guideline B-13 is the Canadian federal prudential regulator's statement of expectations for technology and cyber risk management. It applies to federally regulated financial institutions and is used by OSFI supervisors as a benchmark when they assess how well an institution governs and controls its technology. This article explains what the guideline is, what it asks for, and how to build a defensible alignment program.
What it is
The Office of the Superintendent of Financial Institutions (OSFI) issues Guideline B-13, Technology and Cyber Risk Management. It was finalized in 2022 and took effect on January 1, 2024. It superseded OSFI's earlier, more narrowly framed cyber security self-assessment guidance, setting out technology and cyber expectations in a single guideline.
B-13 is a guideline, not a statute or a certification scheme. It does not create a formal audit-and-certificate process. It sets out supervisory expectations, and OSFI uses it in its supervisory work. Its legal weight comes indirectly: institutions are expected to manage risk soundly, and B-13 describes what OSFI regards as sound practice for technology and cyber risk.
The guideline is outcome-oriented and is meant to be applied proportionately. It states desired outcomes and supporting principles rather than prescribing specific tools or configurations. OSFI expects institutions to apply it proportionately, reflecting their size, nature, complexity and risk profile.
Who it applies to
B-13 is addressed to federally regulated financial institutions (FRFIs) in Canada. That group includes banks, federally regulated insurers, trust and loan companies, and certain other institutions under OSFI's mandate, as well as branches of foreign banks and insurers operating in Canada. Provincially regulated entities are outside OSFI's remit, although provincial regulators and counterparties may point to similar expectations.
There is no minimum size threshold, but proportionality matters. A large systemically important bank will be expected to demonstrate more mature and extensive practices than a small insurer. Vendors and service providers are not directly regulated by the guideline. They feel its effect through contracts and due diligence requests from their FRFI customers.
Key requirements and control areas
The guideline is organized around governance and risk management, followed by a set of technology and cyber domains. Each has a stated outcome and supporting principles. Exact numbering is best checked against the current text, but the main areas are as follows.
Governance and risk management
- Accountability for technology and cyber risk at senior management and board level, including clear roles and reporting lines.
- A technology and cyber strategy that is aligned with business strategy.
- A risk management framework with defined risk appetite, identification, assessment, monitoring and reporting for technology and cyber risks.
Technology operations and resilience
- Technology architecture and asset management: maintaining an accurate inventory of technology assets and a sound architecture.
- Technology project and change management: controlled development, acquisition and change, including secure development practices.
- Technology service management: incident and problem management, capacity, and patching and vulnerability handling.
- Technology resilience: recovery capabilities, including disaster recovery planning and testing, aligned to business criticality.
Cyber security
- Identify: understanding assets, threats and vulnerabilities, including threat intelligence and testing.
- Defend: preventive controls such as access management, data security, network security and secure configuration.
- Detect: continuous monitoring and logging that surface anomalous activity.
- Respond, recover and learn: incident response, recovery and post-incident review.
Third-party and cloud considerations
B-13 addresses technology risk arising from third parties and cloud services, and works alongside OSFI's separate guidance on third-party risk management (Guideline B-10, which has been updated in recent years). Institutions remain accountable for outsourced technology. The practical consequence is that contracts, due diligence, concentration risk and exit planning need to be tied to the technology risk framework.
Assessment, audit and enforcement
OSFI supervises FRFIs through its ongoing supervisory process. This includes reviews, information requests, and discussions with management and, where relevant, the board. There is no B-13 certificate to obtain. Instead, supervisors assess whether the institution's practices achieve the stated outcomes and whether gaps are understood and being remediated.
Institutions typically rely on all three lines of defence. First-line teams operate controls. Second-line risk and compliance functions challenge and monitor. Internal audit provides independent assurance against the guideline. Many institutions also commission external assessments or penetration and red-team testing to support their evidence.
OSFI also has a technology and cyber incident reporting advisory, under which institutions are expected to report certain incidents to the regulator within a short timeframe. Check the current advisory for the definition and timing. OSFI's supervisory tools escalate from feedback and required remediation plans to stronger interventions where risks are not addressed. This article does not describe specific penalties, because the consequences depend on the supervisory context rather than a fixed schedule tied to B-13.
A practical path to meeting B-13
- Confirm scope and proportionality. Identify the legal entities and business lines in scope and document how you interpret proportionality for your risk profile.
- Run a gap assessment. Break the guideline's outcomes and principles into specific control statements and compare each against current practice. Record the result, owner and target date for every gap.
- Establish governance. Confirm board and senior management accountability, reporting cadence, risk appetite metrics, and the technology and cyber strategy.
- Build the asset and architecture baseline. Maintain an inventory covering systems, data, cloud workloads and third-party dependencies, tied to business criticality.
- Strengthen core cyber controls. Prioritize access management, vulnerability and patch management, logging and monitoring, and secure configuration based on the gaps found.
- Embed security in change and development. Add threat modeling, secure code review and testing gates to project and change processes.
- Align third-party management. Update contracts, due diligence and ongoing monitoring for critical technology providers, including exit and concentration planning.
- Test resilience. Exercise disaster recovery, incident response and cyber scenarios, and feed lessons into remediation.
- Prepare for incident reporting. Define internal triggers and escalation paths so that regulator notifications can be made within the required timeframe.
- Monitor and evidence continuously. Keep evidence current rather than assembling it before supervisory reviews, and report status to senior management and the board.
How it maps to other frameworks
The overlaps below are real but partial. None of these frameworks substitutes for B-13, and OSFI does not treat certification against them as proof of alignment.
- NIST Cybersecurity Framework: B-13's cyber domains follow a similar lifecycle logic (identify, defend, detect, respond, recover), and OSFI has acknowledged recognized industry frameworks as useful references. NIST CSF is often the easiest crosswalk.
- ISO/IEC 27001 and 27002: Overlap on risk management, asset management, access control, operations security, supplier relationships and incident management. B-13 additionally stresses board accountability, resilience and regulator-specific expectations.
- SOC 2: Useful as evidence about a service provider's controls, particularly in third-party due diligence. It is an attestation scoped to the provider's system and does not cover the FRFI's governance obligations.
- Related regulatory regimes: Institutions with EU operations may also deal with DORA, and OSFI's B-10 and operational resilience expectations sit adjacent to B-13. They share themes such as third-party risk, testing and incident handling, but with different details.
FAQs
Is B-13 legally binding?
It is a regulatory guideline, not legislation. It is not enforced like a statute, but OSFI uses it as a supervisory benchmark, and FRFIs are expected to be able to explain any departure from it.
Do we need a certification to show compliance?
No. OSFI does not issue B-13 certificates or accredit assessors. You demonstrate alignment through your governance records, control evidence, testing results and internal audit work.
Does B-13 apply to our vendors?
Not directly. The FRFI remains accountable for risks from vendors and cloud providers, so expectations reach vendors through contracts, due diligence and ongoing monitoring.
Can smaller institutions apply it more lightly?
Yes, within limits. The guideline is intended to be applied proportionately, but smaller institutions still need to meet the outcomes, in a manner suited to their risk and complexity, and document their reasoning.
Is B-13 the same as OSFI's incident reporting requirement?
No. Incident reporting is covered by a separate OSFI advisory. B-13 covers incident management capability more broadly, so the two should be aligned in your procedures.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For B-13 work, it helps you keep control evidence current and organized by framework requirements, so supervisory conversations rest on evidence rather than on a last-minute scramble. You can explore the compliance frameworks it covers.
- Automated evidence collection from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
- Real-time control monitoring with alerts when controls drift out of compliance, so you can remediate early.
- Cross-framework mapping that links each piece of evidence to the relevant controls across the frameworks you track, giving you a single evidence base.
- Automated threat modeling from code, IaC and architecture diagrams, plus vendor control mapping to support third-party risk work.