OSFI B-13: what the technology and cyber risk guideline expects, domain by domain
Guideline B-13 is the Office of the Superintendent of Financial Institutions’ statement of what it expects Canadian banks, insurers and trust companies to do about technology and cyber risk. It has been in effect since January 2024, it is outcome-based, and OSFI examiners now test against it. This guide sets out the three domains and their expectations, the related incident-reporting and third-party rules, and how to run B-13 as one programme with ISO 27001 and, for groups with Australian operations, APRA CPS 234.
B-13 replaced a patchwork of advisories with a single guideline that reads like a control framework: each domain states the outcome OSFI wants and then lists what it expects to see, from a technology strategy approved by senior management to a documented patch process with defined timelines, a tested disaster recovery capability and a cyber programme that covers identify, defend, detect, respond, recover and learn. Institutions are expected to apply it proportionately to their size, nature and complexity, and to be able to show how.
Three other OSFI instruments travel with it. The incident reporting advisory sets the 24-hour notification. Guideline B-10 governs third-party arrangements, including cloud and critical vendors, and expects a programme proportionate to the criticality of each. Guideline E-21 adds operational risk management and operational resilience, with critical operations and tolerances in the same spirit as Australia’s CPS 230, taking full effect in 2026.
The three domains
Domain 1: Governance and risk management
Accountability and organisational structure for technology and cyber risk with clear senior-management ownership; a technology and cyber strategy aligned to the business; a technology and cyber risk management framework with appetite, identification, assessment, measurement, monitoring and reporting, and controls tested for effectiveness.
Domain 2: Technology operations and resilience
Technology architecture and standards; a complete, current asset inventory with ownership and classification; technology project management; a system development life cycle with security built in; change management; patch management with defined timelines and risk-based prioritisation; incident and problem management; technology resilience with disaster recovery objectives set, tested and met, and backups protected.
Domain 3: Cyber security
A cyber security programme and risk assessment; identify: threat intelligence, vulnerability and asset identification; defend: secure configuration, identity and access management, data protection, application and network security; detect: continuous monitoring and logging; respond, recover and learn: incident response and crisis management, forensics, recovery, lessons learned and testing including red teaming.
Who it applies to
All federally regulated financial institutions in Canada and, through B-10, their material third parties and cloud providers, who are asked for B-13-aligned assurance as a condition of doing business. Provincially regulated credit unions and insurers are not bound by it but are commonly measured against it by their own regulators and auditors. Foreign bank branches apply it to their Canadian operations.
From scope to evidence, in one system
Domains and expectations as controls
OSFI B-13 is a native framework in the GRCorb library: every expectation is a control with an owner, status, test plan and evidence, grouped by domain, so an examiner’s request for how a given expectation is met is answered from the record.
Asset inventory, patching and resilience from live data
Adapters for Microsoft 365, Entra ID, Intune, Defender, CrowdStrike, AWS, Azure, Kubernetes, Tenable or Qualys and Veeam collect the asset, configuration, vulnerability, patch and backup evidence Domain 2 expects, with patch timelines checked continuously rather than at year end.
Incident clocks and reporting record
Incidents carry the materiality assessment and the 24-hour OSFI notification record with updates, alongside the privacy breach assessment where personal information is involved.
B-10 third parties and E-21 critical operations
Third parties are tiered and monitored in the vendor module with B-10 contract and assurance requirements; critical operations, tolerances and continuity testing are recorded for E-21, reusing the structure built for APRA CPS 230.
Crosswalk to ISO 27001, NIST CSF and APRA CPS 234
B-13 expectations are mapped to ISO 27001 Annex A, NIST CSF 2.0 and APRA CPS 234, so an ISO-certified institution or a group with Australian operations reuses evidence rather than duplicating it, and board reporting presents one posture across regulators.
Frequently asked questions
Is B-13 a legal requirement?
OSFI guidelines set out the regulator’s expectations rather than statutory rules, but OSFI supervises against them and can impose supervisory measures. In practice institutions treat B-13 as mandatory, and auditors and boards expect evidence of compliance.
How does B-13 compare with APRA CPS 234?
They cover similar ground. CPS 234 is shorter and principles-based with a 72-hour incident notification; B-13 is more detailed, especially on technology operations, with a 24-hour notification under the advisory. Groups regulated by both run one programme and report to each.
What does OSFI consider a material incident?
One that has or could have a material impact on operations, customers or the institution’s reputation, including significant service disruption, data breaches and ransomware. The advisory gives examples; when in doubt, notify.
Where does E-21 fit?
E-21 is the operational risk and resilience guideline that sits above B-13: critical operations, tolerances for disruption, scenario testing and crisis management, taking full effect in 2026. B-13 supplies the technology and cyber controls that E-21 relies on, and the two share incident, third-party and continuity records.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.