Operational Resilience

Canada OSFI B-13

OSFI B-13 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
OSFI B-13 — Technology and Cyber Risk Management Guideline
  • Classification
    Category
    Operational Resilience
    Domain
    Cybersecurity
    Framework Family
    Other
  • Regulatory Context
    Type
    Framework
    Legal Instrument
    Guideline
    Sector
    Financial Sector
    Industry
    Financial Services
  • Region / Publisher
    Region
    North America
    Region Detail
    Canada
    Publisher
    Office of the Superintendent of Financial Institutions (OSFI)
  • Versioning
    Version
    Guideline B-13 (July 2022), 17 principles in three domains
    Effective Date
    January 1, 2024
    Issue Date
    July 13, 2022 (final release)
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

Guideline B-13 is published free by the Office of the Superintendent of Financial Institutions and is included with the platform for reference.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
Canada OSFI B-13 Technology and Cyber Risk Management Guideline
Describes the risk management expectations for technology and cybersecurity in financial institutions.
Key takeaways
  • OSFI Guideline B-13 sets expectations for technology and cyber risk management at Canada's federally regulated financial institutions.
  • Released July 13, 2022 and effective since January 1, 2024, it applies to banks, insurers, and trust and loan companies.
  • Its 17 principles sit in three domains: governance and risk management, technology operations and resilience, and cyber security.
  • OSFI applies it in a risk-based way that reflects an institution's size, complexity, and risk profile.
  • SmartSuite holds the technology and cyber risk framework, asset inventory, disaster recovery test results, and incident records mapped to the 17 principles.

Overview

OSFI Guideline B-13, Technology and Cyber Risk Management, sets the Office of the Superintendent of Financial Institutions' expectations that every federally regulated financial institution (FRFI) govern technology and cyber risk through clear accountability, run stable and recoverable technology operations, and keep a secure technology posture. It was released on July 13, 2022 and has been effective since January 1, 2024.

OSFI, Canada's federal prudential regulator, publishes it for banks, foreign bank branches, foreign insurance branches, life, property and casualty insurers, and trust and loan companies. It is a guideline of supervisory expectations that OSFI applies in a risk-based way, with 17 principles in three domains: Governance and risk management, Technology operations and resilience, and Cyber security.

Institutions implement it by assigning senior officers to technology and cyber risk, building a risk management framework with a defined risk appetite, keeping asset inventories and disaster recovery that is tested against severe but plausible scenarios, and operating identify, defend, detect, and respond-and-recover cyber capabilities. OSFI also publishes a self-assessment tool and a separate incident reporting advisory.

Why does it matter?

B-13 tells a Canadian financial institution how OSFI will judge its technology and cyber resilience. It states that there is no one-size-fits-all approach and that the guideline is to be read and implemented from a risk-based perspective that reflects an institution's size, complexity and risk profile (section A).

Key benefits include:

  • Senior accountability

Senior Management is accountable for technology and cyber security operations and assigns named senior officers, such as the CIO, CTO or CISO (principle 1).

  • A defined risk appetite

The technology and cyber risk management framework sets a risk appetite with limits, thresholds and tolerance levels aligned to enterprise risk management (principle 3).

  • Tested recovery

Institutions run an Enterprise Disaster Recovery Program and test it against severe but plausible scenarios (principles 12 and 13).

  • Intelligence-led testing

Institutions set triggers and minimum frequencies for intelligence-led threat assessments, including penetration testing and red teaming (section 3.1.2).

  • Third-party incidents count

Response and recovery capabilities cover incidents that originate at third-party providers (principle 17).

How does it work?

The Guideline has three domains, each with a desired outcome. Domain 1, Governance and risk management, covers accountability and structure (principle 1), strategy (principle 2) and the risk management framework (principle 3). Domain 2, Technology operations and resilience, covers principles 4 to 13. Domain 3, Cyber security, covers principles 14 to 17.

Domain 2 principles are technology architecture, asset management, project management, the System Development Life Cycle, change and release management, patch management, incident and problem management, service measurement and monitoring, disaster recovery and disaster recovery scenario testing. Domain 3 follows an identify, defend, detect, and respond, recover and learn sequence.

OSFI expects the Guideline to be read with its Corporate Governance Guideline, E-21 on Operational Risk Management, B-10 on Outsourcing, its Cyber Security Self-Assessment Tool and its Technology and Cyber Security Incident Reporting Advisory (section A.4).

Key Elements

  • Governance and risk framework (principles 1 to 3)

Senior Management assigns responsibility to senior officers and ensures structure and resources. A documented, approved strategic technology and cyber plan has measurable goals, and the risk management framework sets out risk appetite, a risk taxonomy, control domains and reporting to Senior Management (sections 1.1 to 1.3).

  • Asset and change management (principles 5, 8 and 9)

FRFIs keep an updated inventory of all technology assets that supports business processes, classify assets by criticality, record configurations and monitor technology currency (section 2.2). Changes follow a controlled change and release process, and patching is controlled and timely.

  • Incident and problem management (principle 10)

Standards provide for timely identification and escalation, restoration and root cause investigation. Processes include classifying incidents by priority, periodic scenario exercises, and testing with third parties. Problem management uses post-incident reviews to improve processes (section 2.7).

  • Disaster recovery (principles 12 and 13)

The Enterprise Disaster Recovery Program sets accountability, identifies key dependencies, defines recovery plans within an acceptable timeframe and includes data backup and recovery controls. Scenario testing covers backup and recovery, and critical third-party technologies and integration points (sections 2.9.1 to 2.9.3).

  • Cyber identify and defend (principles 14 and 15)

Identification includes threat assessments, vulnerability assessments with defined frequency, data classification and awareness testing. Defense calls for layered controls, secure-by-design practices, strong cryptography, identity and access management, configuration baselines and application scanning (sections 3.1 and 3.2).

  • Detect, respond, recover and learn (principles 16 and 17)

Continuous detection supports monitoring, alerting and forensic investigations. FRFIs define a cyber incident taxonomy, maintain playbooks, establish an incident response team available continuously, and conduct forensic and root cause analysis for high-severity incidents (sections 3.3 and 3.4).

What does it cover?

Guideline B-13 applies to all federally regulated financial institutions, including foreign bank branches and foreign insurance company branches to the extent consistent with their legal obligations in Canada. Branch expectations are set out in Guideline E-4. It covers information technology and information security, defined broadly as technology risk including cyber risk (section A.1).

What are its objectives?

The Guideline aims to support institutions in developing resilience to technology and cyber risks. Each domain has a desired outcome.

Govern technology and cyber risks through clear accountabilities, structures, strategies and frameworks.

Maintain a technology environment that is stable, scalable and resilient with sustainable operating and recovery processes.

Maintain a secure technology posture that protects the confidentiality, integrity and availability of technology assets.

Read and apply the Guideline in a risk-based way that fits the institution's size and complexity.

Align technology and cyber practices with OSFI's guidance on governance, operational risk and outsourcing.

Framework in Context

B-13 sits within OSFI's Sound Business and Financial Practices guidance. It points institutions to recognized frameworks and standards for technology operations and information security, and OSFI's incident reporting advisory, updated on August 13, 2021, asks FRFIs to report technology and cyber incidents to OSFI's Technology Risk Division and Lead Supervisor within 24 hours, or sooner if possible. It is a Canadian supervisory guideline rather than an international standard.

Common Framework Mappings

Organizations commonly map OSFI B-13 to international and industry frameworks to harmonize controls, demonstrate regulatory alignment, and simplify risk and operational resilience management.

Mapped frameworks include:

Digital Operational Resilience Act (DORA)

ISO/IEC 27001

ISO/IEC 27002

ISO/IEC 27017

ISO/IEC 27018

NIST Cybersecurity Framework

NIST SP 800-53

SOC 2

SMARTSUITE

How SmartSuite Supports OSFI B-13

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Cyber & IT Risk and Operational Resilience & Business Continuity records to hold the technology and cyber risk framework, the asset inventory, disaster recovery test results and incident records that map to the 17 principles.

Principles Library and Ownership

Load the 17 principles in three domains as controls, each with a named senior-officer owner and review date (principle 1).

Technology and Cyber Risk Framework

Track risk appetite measures, the risk taxonomy and risk assessments with treatment plans and approvals (principle 3).

Asset Inventory and Technology Currency

Keep records of technology assets with criticality, configuration baseline and end-of-support dates (principle 5).

Disaster Recovery and Scenario Testing

Schedule disaster recovery tests against severe but plausible scenarios, capture results and track remediation to closure (principles 12 and 13).

Incident Response and OSFI Reporting

Record incidents with classification, severity and timeline, including the 24-hour notice under the OSFI advisory and post-incident reviews (principles 10 and 17).

Third-Party and Supervisory Reporting

Show posture by domain, open gaps and third-party dependencies on a dashboard for Senior Management and for supervisory discussions.

Related frameworks

EU DORA

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO 27017

ISO/IEC 27017:2026 gives cloud security control guidance for customers and providers, built on ISO/IEC 27002:2022, with four cloud-specific controls; it replaced the 2015 edition.

ISO 27018

ISO/IEC 27018:2025 gives guidelines for protecting PII in public clouds acting as PII processors, built on ISO/IEC 27002:2022 with an extended control set.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

SOC 2

SOC 2 is the AICPA examination, under AT-C 105 and 205, of a service organization's controls against the 2017 Trust Services Criteria, issued as a type 1 or type 2 attestation report.

FAQ

Frequently Asked Questions For Canada OSFI B-13 (Technology and Cyber Risk Management Guideline)

All federally regulated financial institutions: banks, foreign bank branches, foreign insurance company branches, life, property and casualty insurers, and trust and loan companies. Branch expectations are set out in Guideline E-4 (section A).

No. It is an OSFI guideline that sets supervisory expectations, to be applied in a risk-based way that reflects an institution's size, complexity and risk profile. There is no certification; OSFI assesses institutions against it through supervision.

It has 17 principles in three domains: Governance and risk management (principles 1 to 3), Technology operations and resilience (principles 4 to 13), and Cyber security (principles 14 to 17). Each domain states a desired outcome.

OSFI's Technology and Cyber Security Incident Reporting Advisory, updated August 13, 2021, asks federally regulated financial institutions to report to OSFI's Technology Risk Division and their Lead Supervisor within 24 hours, or sooner if possible. B-13 refers institutions to this advisory.

OSFI released the final Guideline on July 13, 2022 and set an effective date of January 1, 2024 to give institutions time to self-assess and prepare. OSFI also publishes a self-assessment tool for the Guideline.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.