OSFI Guideline B-10: Third-Party Risk Management
OSFI Guideline B-10 sets the rules for third-party risk management at Canadian banks, insurers and trust companies. This note explains its six outcomes and principles, risk-based inventories and due diligence, contract provisions and subcontracting, cloud concentration and exit plans, and links to B-13, E-21 and E-23.

Key takeaways
- B-10 applies to banks, foreign branches, insurers and trust and loan companies.
- The FRFI remains ultimately accountable for risks from all third-party arrangements.
- Oversight is proportionate to risk and criticality, starting with a complete inventory.
- Annex 2 lists contract provisions for high-risk and critical arrangements.
- OSFI expects FRFIs to understand both institution-specific and systemic concentration risk.
What OSFI Guideline B-10 requires
OSFI Guideline B-10, Third-Party Risk Management, is OSFI's statement of how federally regulated financial institutions (FRFIs) should approach third-party risk management: how they identify, assess and control the risks of relying on outside providers, from cloud platforms and software vendors to outsourced call centres, fintech partners and affiliates. The guideline is dated April 2023 and applies to banks, foreign bank branches, foreign insurance branches, life and fraternal insurers, property and casualty insurers, and trust and loan companies.
After consultation, OSFI set a one-year transition period, explaining in its response to consultation feedback that a year was reasonable given the scope of the new requirements. B-10 replaced the earlier outsourcing guideline and broadened the focus from "material outsourcing" to all third-party arrangements, managed on a risk-based basis. Institutions that had built programs around the old materiality test therefore had to widen their inventories and rethink how they rate and monitor smaller but still important relationships.

The core message is accountability. Principle 1 states that the FRFI is ultimately accountable for managing the risks arising from all types of third-party arrangements. It can outsource activities, but not responsibility. For vendors, that principle translates into longer due diligence questionnaires, tougher contract terms and ongoing monitoring by their FRFI clients.
B-10 is also deliberately broad in what it treats as a third-party arrangement. It is not limited to classic outsourcing contracts. It can extend to arrangements with affiliates, joint ventures, partners that distribute an FRFI's products, data and technology providers, and other relationships where the FRFI relies on an outside party, whether or not there is a formal written contract. The breadth is balanced by proportionality: the intensity of oversight should match the risk and criticality of each arrangement, so a low-risk office supplies contract does not need the same treatment as a core banking platform.
The six outcomes and the principles
B-10 identifies six expected outcomes of effective third-party risk management:
- governance and accountability structures are clear, with comprehensive risk management strategies and frameworks;
- risks posed by third parties are identified and assessed;
- those risks are managed and mitigated within the FRFI's risk appetite framework;
- third-party performance is monitored and assessed, and risks and incidents are proactively addressed;
- the FRFI's program allows it to identify and manage a range of third-party relationships on an ongoing basis; and
- technology and cyber operations carried out by third parties are transparent, reliable and secure.
The principles cover the full life cycle: accountability (Principle 1); a third-party risk management framework, or TPRMF, with clear accountabilities and processes (Principle 2); risk assessment before entering and periodically during an arrangement, proportionate to criticality (Principle 3); due diligence (Principle 4); subcontracting (Principle 5); written agreements (Principle 6); data security and controls (Principle 7); access to information and audit rights (Principle 8); business continuity and contingency (Principle 9); ongoing monitoring (Principle 10); and incident management (Principle 11). A further section addresses technology and cyber risk in third-party arrangements.
| Life cycle stage | What OSFI expects | Practical deliverable |
|---|---|---|
| Governance | Board-approved framework, clear roles, risk appetite | TPRMF policy and inventory of all third-party arrangements |
| Risk assessment | Assess inherent risk and criticality before contracting and periodically | Risk rating and criticality classification for each arrangement |
| Due diligence | Proportionate diligence before contracting and on an ongoing basis | Questionnaires, financial review, control testing, site visits for critical vendors |
| Contracting | Written agreement setting out rights and responsibilities | Annex 2 provisions for high-risk and critical arrangements |
| Monitoring | Ongoing oversight of performance and risk | KPIs, service reviews, audit reports, issue tracking |
| Exit | Contingency and exit plans for critical arrangements | Documented exit strategy, data return, transition assistance |
Third-party risk management starts with inventories and due diligence
Third-party risk management under B-10 starts with knowing what you have. FRFIs are expected to maintain an inventory of third-party arrangements and to classify each by risk and criticality. B-10 is explicitly proportionate: OSFI notes that an exit or contingency plan may not be needed for a low-risk arrangement, subcontracting risk will not be significant in every arrangement, and a legal review may not be necessary for a low-risk, short-term arrangement. What matters is identifying the type and level of risk so that each arrangement is managed with the appropriate intensity.
Due diligence under Principle 4 must occur before contracting and on an ongoing basis. Annex 1 lists examples of considerations, including the third party's financial condition, skills and experience, reputation, risk management and controls, information security, business continuity, reliance on subcontractors, and the geographic and legal risks of operating outside Canada. For arrangements with a presence outside Canada, B-10 expects FRFIs to review the legal requirements of relevant jurisdictions and the political, legal, security, economic, environmental and social risks that may impede service.
Contract provisions and subcontracting
Principle 6 requires written arrangements setting out each party's rights and responsibilities. For high-risk and critical arrangements, Annex 2 provides a non-exhaustive list of provisions FRFIs should include. In practice these cover:
- nature and scope of services, service levels and performance measures;
- pricing and fees;
- data ownership, confidentiality, security, location and return or destruction;
- audit and access rights for the FRFI, its auditors and OSFI;
- incident notification and cooperation;
- business continuity and disaster recovery obligations and testing;
- subcontracting restrictions, notice and flow-down of obligations;
- default, termination rights and exit assistance; and
- dispute resolution and governing law.
Principle 5 makes the FRFI responsible for identifying, monitoring and managing risks arising from subcontracting by its third parties. Vendors should expect to disclose material subcontractors, notify changes and flow down key obligations, particularly for cloud hosting, data processing and offshore support.
Vendors selling to Canadian banks and insurers should prepare a "B-10 pack" in advance: standard responses to due diligence questionnaires, a list of subcontractors, SOC reports or equivalent assurance, business continuity test summaries, and contract language aligned with Annex 2. It shortens procurement and reduces the risk of last-minute negotiation over audit and exit rights.
Cloud, concentration risk and exit plans
B-10 defines two forms of concentration risk. Institution-specific concentration risk arises from overreliance on a single third party, subcontractor or geography for multiple activities. Systemic concentration risk arises where one third party or geography provides services to multiple FRFIs; OSFI expects FRFIs to understand this risk to the greatest extent possible. Major cloud providers are the obvious example, but payment processors, core banking vendors and market data providers can create similar dependencies.
For critical arrangements, Principle 9 requires the ability to deliver operations through disruption, including maintaining, testing and activating business continuity and disaster recovery plans, and contingency plans. Exit planning should consider portability (B-10 refers to the NIST concept of moving data and applications between cloud systems at acceptable cost), the time needed to transition, data return formats and the availability of alternative providers. A realistic exit plan is often harder to build than the contract itself, and it should be refreshed whenever the service, the provider or the FRFI's dependence on it changes materially.
Building a third-party risk management program that works
Several practical lessons follow from the structure of the guideline. A credible third-party risk management program is less about long policies than about evidence that the FRFI knows its critical dependencies and can act on them.
Governance and ownership
The board approves the framework and risk appetite, and senior management owns its implementation. Each arrangement should have a named business owner responsible for the relationship and a second-line function that challenges risk ratings and monitors aggregate exposure. Procurement, legal, information security, privacy, business continuity and compliance all contribute, so a clear RACI chart avoids gaps.
Criticality methodology
Criticality should be assessed by asking what would happen if the service failed or the vendor disappeared: the impact on critical operations, customers, financial results, regulatory compliance and reputation. Arrangements supporting critical operations under E-21 should be classified as critical for B-10 purposes too. Intragroup arrangements are third-party arrangements and should be rated like any other, although the diligence can reflect the group's shared controls.
Ongoing monitoring and reporting
Monitoring should combine service performance metrics with risk indicators: financial health, control failures, incidents, subcontractor changes, regulatory actions against the vendor and concentration trends. Boards should receive periodic reporting on the most critical arrangements, material incidents, overdue remediation and concentration risk, rather than a list of every vendor.
Testing exit and contingency
For critical arrangements, exit and contingency plans should be tested at least on paper, with assumptions about time, cost and alternative providers challenged. Some FRFIs run tabletop exercises simulating a vendor's insolvency or a prolonged cloud outage, which often reveals data access, licensing and staffing problems that contracts do not solve.
Fintech partners of FRFIs face the same expectations through contract. A fintech that provides a customer-facing service on behalf of a bank should expect the bank to treat the arrangement as high-risk, require detailed reporting, and insist on audit, incident and exit rights. Building those capabilities early is a commercial advantage in selling to Canadian institutions, and third-party risk management questions are now a routine part of partnership negotiations.
Links to B-13, E-21 and E-23
B-10 should be read with other OSFI guidance. It refers expressly to Guideline E-21 on operational risk management and Guideline B-13 on technology and cyber risk management, and to OSFI's corporate governance expectations. B-13 sets expectations for technology and cyber controls, including those operated by third parties, while E-21 covers operational resilience and the ability to deliver critical operations through disruption. Where a third party provides models, including AI models, OSFI's revised Guideline E-23 on model risk management, effective 1 May 2027, will also apply. A coherent program maps each critical third-party arrangement to the relevant expectations under all of these guidelines rather than treating them separately.
Illustration (hypothetical): a mid-sized Canadian insurer moves claims processing to a cloud-based platform provided by a US software company, which relies on a hyperscale cloud provider and an offshore support team. The insurer rates the arrangement as critical, performs due diligence including the subcontractors and data location, negotiates Annex 2 provisions including audit rights and exit assistance, tests a contingency plan, and reports the arrangement and its concentration risk to its board.
How TRW & Co helps with third-party risk management
We advise FRFIs and their vendors on third-party risk management under OSFI Guideline B-10. That includes framework and policy design, inventory and criticality methodologies, due diligence programs, negotiating Annex 2 contract provisions, cloud and outsourcing agreements, exit planning, and responding to OSFI supervisory findings. Where an opinion or filing requires a Canadian-licensed lawyer, we work with licensed counsel. Our financial services regulatory and cybersecurity work covers related issues; see also our notes on OSFI Guideline E-23 and bank investments in fintechs. To discuss your program or contracts, contact us. This note is general information, not legal advice.
Frequently asked questions
Who does OSFI Guideline B-10 apply to?
Federally regulated financial institutions: banks, foreign bank branches, foreign insurance branches, life and fraternal insurers, property and casualty insurers, and trust and loan companies. It applies to all their third-party arrangements, including with affiliates, managed on a risk-based basis.
When did B-10 take effect?
The final guideline is dated April 2023. In its response to consultation feedback, OSFI provided a one-year transition period, so institutions were expected to comply from 2024. Supervisors now assess compliance as part of their ongoing review of operational risk.
What contract terms does B-10 expect?
A written agreement setting out rights and responsibilities for every arrangement and, for high-risk and critical arrangements, the provisions in Annex 2, typically covering scope and service levels, data security and location, audit and access rights, incident notification, business continuity, subcontracting, termination and exit assistance.
How does B-10 treat cloud providers?
Cloud arrangements are third-party arrangements subject to B-10 and to B-13's technology and cyber expectations. FRFIs must assess institution-specific and systemic concentration risk, maintain business continuity and contingency plans, and plan for portability and exit.
Do vendors have direct obligations under B-10?
No. B-10 is addressed to FRFIs, which remain accountable. In practice, vendors carry the obligations through contracts: due diligence responses, audit and access rights, incident notification, subcontracting disclosure and exit assistance. Vendors that prepare for these requests in advance shorten procurement.
Sources
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


