JournalArta
Thursday, November 19, 2026 · JakartaS&P 7,323.63 ▼0.23%USD/IDR 18,256 ▲0.16%
JournalArta
Global Edition
beyond headlines
Advertisement

OSFI B-10 Cloud Outsourcing Controls for Canadian Banks

Canadian banks assessing cloud outsourcing need to review provider contracts, statutory records, concentration and exit plans under OSFI B-10.

By matthew jonathan
November 19, 20265 min read
Cloud infrastructure for Canadian bank operations
OSFI B-10 Cloud Outsourcing Controls for Canadian Banks

Under OSFI’s B-10 guideline, federally regulated Canadian banks remain accountable for outsourced operations and should be able to keep critical services running through a provider disruption or exit. An OSFI B-10 cloud outsourcing review of AWS Canada financial services cloud offerings should therefore examine contract rights, service dependencies and recovery evidence before signing.

  • OSFI expects due diligence before signing, at renewal and during the arrangement, with the depth of review tied to risk and criticality.
  • The Bank Act’s Canadian location rule applies to specified statutory records, subject to exceptions. Assess other data and foreign service dependencies under the requirements that apply to them.
  • Map exposure by supplier, subcontractor and geography across the bank. Two regions with one provider can address a regional outage while leaving shared dependencies in place.
  • For high-risk or critical arrangements, document how the bank would leave through both a planned migration and an emergency exit.
Advertisement

Cloud contract terms that support oversight

For a new cloud procurement, classify the business function before scoring providers. A platform that supports customer account access and a development environment with synthetic data call for different evidence. Determine what a disruption would stop, which teams would need to respond and whether another service could take over. Repeat the review when a change materially alters the service or its criticality.

For high-risk or critical arrangements, use Annex 2 to review the order form, service terms and any negotiated addendum together. Ask legal and engineering to check four items against the actual service design:

Advertisement
  • Information and audit rights. Identify the reports that cover the services in use, who can obtain them and how the bank and OSFI can evaluate the controls or commission an independent review.
  • Incident communications. Specify who alerts the bank about a material provider or subcontractor event, what information the alert must contain and how the bank can obtain updates for its own reporting.
  • Subcontractor changes. Identify which functions are subcontracted and how the bank receives notice and assesses changes. Evaluate whether the risk warrants refusal or subcontractor audit rights.
  • Recovery and termination. Check who tests recovery, who receives the results, how deficiencies are fixed and when the provider must return records and other assets.
Advertisement

If standard terms leave a gap, record the proposed mitigation and who owns the residual risk. A bank might retain an independently accessible copy of essential records to reduce recovery exposure. A gap in statutory access calls for a different response. Teams sourcing services across jurisdictions can compare their review with the UK critical third parties regime.

Canadian records, cloud regions and foreign dependencies

Start with the records described in section 238 of the Bank Act. Section 239 generally puts those records at the bank’s head office or another Canadian location chosen by its directors. OSFI says complete electronic copies must be on servers physically located at the places required by the applicable statute. Section 239 provides exceptions, including for certain foreign-owned banks subject to section 245. Confirm which provisions apply to the institution and what access OSFI needs before approving storage abroad. and

Advertisement

For the wider workload, ask the provider to identify where it stores primary data, backups and logs and from where staff or subcontractors can access them. Check whether support and recovery follow the same geographic boundaries as production. Where a provider or subcontractor operates abroad, assess local legal requirements and other jurisdictional risks that could impair service. Keep that assessment tied to the actual data flows and operating model.

Azure Canada cloud regions illustrate why buyers should verify the exact service and location. Microsoft lists three availability zones in Canada Central and lists zone support as unavailable in Canada East. Microsoft also cautions that individual services may lack zone support even in regions that offer it. Its CCCS Medium documentation describes a Government of Canada security assessment. Use the assessment for evidence about services within its scope and check the bank’s B-10 contract and operating controls against the guideline.

Advertisement

Provider concentration, portability and exit decisions

Map dependencies across legal entities and business units before approving another workload on an existing provider. Ask whether the primary and recovery environments share identity, key management, network connectivity or a subcontractor. Run the same check on a proposed second provider. Third-party risk management software can help procurement link each arrangement to the affected business services and flag shared dependencies for review. For an international comparison, see Australia’s CPS 230 cloud vendor controls.

Match the architecture to the failure the bank needs to survive. If the scenario is a regional outage, evaluate a second Canadian region such as AWS Canada West in Calgary, then verify service availability and test the application’s failover. If loss of the provider itself would put a critical operation outside the bank’s risk appetite, assess whether portable components, another provider or an interim operating process can keep the service running. For a Google Cloud OSFI compliance review, compare the vendor’s mapping of the 2023 guideline with the signed terms and deployed controls. AWS directs customers to AWS Artifact for its audit reports.

Advertisement

Before signing a critical arrangement, rehearse an export and restore. In a planned exit, check whether the transition period covers migration and parallel operation. In a stressed exit, test whether the bank can recover essential records and operate while the provider is unavailable. Measure recovery time, check that the records are usable, and budget for transfer, replacement services and temporary staffing. Approve the arrangement when the bank can show who owns each control and how it would sustain the critical operation if the provider failed.

Advertisement
Take the quizWhat Kind of Holiday Spender Are You? Take the Black Friday QuizStart →
Advertisement
Most Read
  1. 1Gold Silver Price November: Futures Rise Near Yearly Lows
  2. 2Michael Clarke Says Sandpapergate Scars Drew Steve Smith to New York
  3. 3U.S. Emergency Alert Test Nov. 17 Is Not a Power Outage
  4. 4Brent Crude Slides 4.05% as Rising US Stockpiles Weigh on Oil
  5. 52027 NFL Mock Draft Puts Ohio State’s Jeremiah Smith at No. 1
Advertisement
Don't Miss

Latest News

All stories →
  1. WorldSpanberger Calls Viral NextEra Photo ‘Gross’ Amid $67 Billion Dominion DealNov 19
  2. Markets · Forex & CommoditiesGold XAU/USD Holds Near Low as Silver Prices Edge UpNov 19
  3. Business · Macro & PolicyBritain’s Inflation Wait Could Last Until 2028, Bank SaysNov 19
  4. Business · Macro & PolicyEPFO Considers Monthly Withdrawals for RetireesNov 19
  5. Advertisement
  6. Business · CompaniesHyundai Wins Best EV Auto Brand Award for 2027Nov 19
  7. Business · EnergyDonald Van der Vaart Resigns After Duke Energy Rate DecisionNov 19
  8. Business · EnergyEDF to Add 1.3 Million Accounts in Utilita DealNov 19
  9. Markets · StocksStock Market Today: Nasdaq and S&P 500 Futures Rise Ahead of Anthropic DebutNov 19