← Security Watch

Security Watch · Canada · July 2026

OSFI sets sound practices for generative and agentic AI at banks and insurers

Limits on autonomy, human oversight for high-impact decisions, and tight control of AI-written code.

RegulationAI Agent Defence

What happened

OSFI's July 2026 Technology Risk Bulletin says generative and agentic AI amplify the speed, scale and automation of cyber and operational risk. It lists sound practices tied to Guidelines B-13, E-21 and B-10: define ownership and limits on autonomy, keep human oversight with audit trails for material decisions, restrict AI inputs to approved data, ban sensitive data in public or unapproved tools, treat AI output as input to a decision rather than the decision, and control AI-generated code before it reaches production. (Office of the Superintendent of Financial Institutions (OSFI), July 2026)

Note on figures: This bulletin is supervisory guidance, not a new binding guideline.

What it means for Canada

OSFI expects banks and insurers to set limits on AI autonomy, keep humans accountable for material decisions and control AI-written code. Their AI vendors will be asked to show the same.

Sectors
Banks · Insurers · Trust and loan companies · Fintech and AI vendors to them
Tools involved
Generative AI assistants · AI agents · AI coding tools
Canadian rules
OSFI B-13 (technology and cyber risk)
OSFI E-21 (operational resilience)
OSFI B-10 (third-party risk)
OSFI E-23 (model risk, in force May 2027)

Takeaways for Canadian businesses

  1. BusinessWrite down what each AI agent may do on its own and where it needs human approval; OSFI calls this defining limits on autonomy.
  2. BusinessLog prompts, outputs and agent actions so material decisions can be audited.
  3. BusinessBlock sensitive data from public or unapproved AI tools.
  4. BusinessPut AI-generated code through the same review and change control as human code before production.

For the Canadian AI sector

AI-agent vendors selling to Canadian financial institutions should expect questions on least-privilege access, logging, kill switches, data provenance and who approves high-impact actions.

Written by AgentsNorth from the source below. General information, not legal or security advice.

Related briefs

Canada Oct. 23, 2026 · Canadian Centre for Cyber Security, alert AL26-026

Cyber Centre alert: patch PHP now for the AI-assisted PHP2Shell remote code execution flaws

The Canadian Centre for Cyber Security issued alert AL26-026 on PHP2Shell, two critical PHP flaws that let an unauthenticated attacker run code, and updated it with a third unpatched bug.
What it means for Canada: The Cyber Centre directed this alert at Canadian IT teams. PHP runs a large share of web apps, so Canadian retailers on WordPress or WooCommerce, government and municipal sites,…
RegulationAI Agent Defence
Canada Oct. 13, 2026 · Innovation, Science and Economic Development Canada

Canada and the UK renew their AI security partnership

Focus areas: AI security standards, sharing on frontier-AI risks, and coordinated model evaluations.
What it means for Canada (our assessment): Canada and the UK will work on shared AI security standards and coordinated model evaluations. Canadian AI vendors may soon be asked to meet them.
RegulationAI Agent Defence
Canada May 1, 2026 · Canadian Centre for Cyber Security

Cyber Centre and Five Eyes partners publish guidance on adopting AI agents carefully

Start with low-risk tasks, never give agents broad access, and require human approval for high-impact actions.
What it means for Canada: Canada's Cyber Centre co-signed the reference guidance for securing AI agents. Canadian buyers will start using it as a checklist for agent vendors.
AI Agent DefenceRegulation

See Canadian AI use cases in Security & Fraud

Get new Canadian AI agent use cases each week

New use cases, one prompt to steal and one failure to avoid. Free. Unsubscribe anytime.