
UK and Canada Renew AI Security Pact—Joint Evaluations Are Still Exploratory

In the UK’s 13 October 2026 statement, the UK and Canada renewed their AI security partnership during a visit to London by Canadian minister Evan Solomon. They set three priorities: interoperable security standards, stronger information sharing and expanded technical cooperation between the Canadian AI Safety Institute and the UK AI Security Institute. The agreement establishes work for the institutes, while leaving coordinated evaluations as an option to explore.
Canada’s joint statement draws a distinction within the technical work: the governments will establish regular exchanges on AI capabilities, risks and evaluation methods, and will explore staff exchanges and coordinated evaluation activities. Those proposed activities have no published timetable or test plan. The difference matters because sharing evaluation methods is an agreed activity; organising evaluations together would require a further decision.
Standards work aims to make security practices compatible

The standards commitment has two parts. The governments will collaborate on developing interoperable AI security standards, with the stated aim of helping appropriate practices gain recognition and wider adoption. They will also identify priority areas for future cooperation on common international standards. Identifying those priorities is part of the work ahead, rather than a completed list of standards.
Interoperability is the practical point of this workstream. If approaches developed in each country can be recognised across borders, organisations dealing with both jurisdictions could face clearer expectations about AI security practices. The agreement expresses that aim but gives no mechanism for recognition, named standard or certification scheme. It therefore signals a direction for cooperation between governments and institutes, not a newly published requirement for AI developers.
The distinction between developing standards and adopting them is consequential. The two governments can agree to work toward compatible approaches before settling their scope or how they would be used. Their next standards decisions would have to identify the areas they intend to address and the form any common approach will take.
Information sharing includes sensitive channels and resilience lessons
The information-sharing commitment concerns how the countries cooperate on AI security challenges. They will enhance their arrangements and use appropriate Five Eyes channels for sensitive reporting where relevant. The reference to those channels gives the workstream a route for material that needs careful handling, although the agreement does not specify what reports will pass through it or establish a public reporting procedure.
The governments also agreed to share lessons from building domestic resilience. That widens the exchange beyond technical findings about AI systems to experience in preparing societies and economies for emerging risks. The statement describes the intended subject of that learning, while leaving each country’s domestic measures and the details of their exchange to subsequent work.
These are distinct forms of cooperation. Sensitive reporting depends on suitable information-sharing arrangements; resilience lessons concern what officials learn from measures taken at home. Both are agreed areas of work, but the published text does not describe a standing feed of evaluation results or promise that sensitive findings will become public.
Regular technical exchanges are agreed; coordinated evaluations are an option

The institutes will establish regular exchanges covering frontier AI capabilities, emerging risks, evaluation methodologies and best practice. That is the firm technical commitment in the renewal. It gives the Canadian and UK institutes a recurring way to compare what they are studying and how they assess advanced systems, linking technical research to the wider standards and information-sharing agenda.
Staff exchanges and coordinated evaluation activities sit one step further out. The governments describe both as possibilities they will explore to strengthen institutional links and knowledge sharing. A staff exchange would involve people working across the institutions; a coordinated evaluation would involve organising assessment activity together. Neither is presented as an operational programme in the agreement.
That wording limits what can be inferred about shared testing. The statements name no participating evaluation teams, models, common test protocol or start date for coordinated activity. The institutes can begin the promised discussions of methods without having agreed to run the same evaluation. A later announcement would be needed to establish the scope and timing of any joint exercise.
The renewal builds on an existing institute relationship
The agreement develops a science-of-AI-safety partnership between the countries and sits alongside their broader growth and innovation relationship. It brings the institutes’ cooperation into a more defined security agenda, combining Canada’s research strengths with the UK’s experience in AI testing and evaluation. The three workstreams describe where that relationship is meant to deepen, rather than replacing the institutes’ existing contact.
Solomon’s London visit provided ministerial contact around the renewal. In Canada’s 15 October account of the visit, officials reported that he met UK AI minister Kanishka Narayan and engaged with the UK AI Security Institute on research and evaluations. Narayan described the countries’ “strong and deep national security relationship” in remarks accompanying that account.
The next concrete signs of progress would be named priorities for standards work and details of how the regular institute exchanges will operate. Coordinated evaluations would mark a separate decision: they remain under consideration until the governments set out an activity they have agreed to conduct together.
Also read:
Related articles


Anthropic Says Distillation Harvesting Fell 90–99%—Proof Is Internal

OpenAI API vs Gemini API: Cheap Tokens Do Not Buy the Same Capability

OpenAI Fired Three Safety Researchers—and Neither Side Proved Its Full Case

Zapier vs Make: The Same Workflow Can Consume Very Different Quotas

LMCache RCE Has No Fix—Routable Port 5555 Can Run Code as Root
Subscribe to our newsletter
Get the latest Web3, AI, and crypto news delivered straight to your inbox.