Third-Party AI Dependency Requires Rigorous Risk Management

Your organisation doesn’t build the model. It doesn’t hold the training data. It doesn’t control the update schedule. But when the AI embedded in a vendor’s platform gets something wrong, the accountability lands on you — not the vendor, and not the model provider three layers upstream.

That gap between who controls the risk and who owns the consequence is widening fast, and three developments from the past few months show exactly how.


The 30-second take

Regulators are starting to formally treat AI and cloud vendors as systemic dependencies, not just suppliers.

Courts are ruling that a chatbot’s bad answer is the deploying company’s legal problem, full stop. And the vendor assurance letter that used to satisfy a board pack is no longer enough evidence of control.

If your third-party AI governance still consists of a signed data processing agreement and a security questionnaire from onboarding, it hasn’t caught up with where liability is actually landing.


HM Treasury moves to designate AI providers as critical third parties

In the UK, HM Treasury is expected to formally designate major AI and cloud providers as Critical Third Parties (CTPs) under the joint FCA/PRA/Bank of England oversight regime during 2026.

The trigger is a finding the Financial Policy Committee has been building toward since its 2025 report on AI in the financial system: firms across UK financial services are concentrated on a small number of US technology providers for the AI and cloud infrastructure that now sits inside core financial decision-making.

Designation brings direct regulatory scrutiny of the vendor’s own resilience — not just the firm’s contract with them.

It is a formal admission that “the vendor’s risk register” and “our risk register” are the same document once dependency reaches a certain scale.

German court makes the chatbot’s words the company’s words

On 12 May 2026, the Higher Regional Court (OLG) of Hamm ruled that a company can be held liable for what its AI chatbot tells customers.

The chatbot had described doctors on the platform as “specialists in plastic and aesthetic surgery,” a title those doctors did not actually hold and were not professionally permitted to use. The court’s reasoning didn’t hinge on whether the company intended the claim or even knew the model would generate it — the chatbot spoke for the business, so the business owns the statement.

That’s a materially harder standard than “we relied on the vendor’s model card.”

Character.AI and Google settle, and product liability sticks

In January 2026, Character.AI and Google reached a settlement in the Garcia wrongful-death case and related suits, agreeing to new safety features for minors. Before the settlement, the presiding US District Judge had already ruled that the Character.AI app qualifies as a “product” for product liability purposes — meaning strict liability, negligence, and wrongful-death claims all survived, and the First Amendment defence that the company leaned on was dismissed.

Once an AI system is treated as a product rather than a protected expression, the standard playbook for deflecting harm shifts substantially, and the vendor relationship becomes a supply-chain liability question, not a free-speech one.

What this means if you didn’t build the model

None of these three examples come from the same jurisdiction, the same regulator, or the same legal theory.

That’s the point — the pressure is converging from prudential oversight, tort law, and product liability at the same time, which means a single-lens governance response (just a data processing agreement, just a security review) will keep missing two of the three angles.

Independent validation of vendor claims, not acceptance of them, is what each of these cases would have rewarded.

Questions to take back to your organisation

  • Do we know which of our AI-embedded vendors would qualify as a critical or concentrated dependency if a regulator asked us to map it?
  • Who in our organisation independently tests or challenges a vendor’s claims about model accuracy, bias, or safety — or do we take the vendor’s word as the evidence?
  • If our customer-facing chatbot or AI tool gives a wrong or misleading answer tomorrow, who is legally accountable, and have we actually tested that assumption with legal counsel?
  • Are our AI vendor contracts written for a world where the vendor is a minor supplier, or updated for a world where the vendor is a systemic dependency?
  • Do we have a current inventory of every third-party AI capability embedded in our customer-facing products, not just the ones we procured directly?
  • When did our board last see evidence — not assurance, evidence — of third-party AI risk exposure?

The organisations named above didn’t fail because they used vendor AI. They were tested because the gap between vendor assurance and independent verification was visible enough for a court or regulator to walk through it.

Want to see how exposed that gap is in your own organisation? Try our AI readiness snapshot.


Free 3–5 minute AI diagnostic

Know where your AI governance stands in five minutes.

Use a short diagnostic to test practical AI governance, oversight and risk controls. Get an immediate visual result and suggested next focus areas.

Practical tools for boards, executives, auditors and risk professionals.

10 questions Visual result Local browser storage
Learn more Visit reading room
Privacy note: your individual results are not stored by Innovation of Risk. Results stay in your browser; we only track aggregate usage such as page views and average score once you leave our page.

More from the Reading Room

Why AI Operational Resilience Must Be a Boardroom Priority Now

AI failures can disrupt critical operations and damage customer trust. Boards and executives must treat AI operational resilience as a core governance responsibility—not just a technical issue—to safeguard business continuity and reputation.

How to Master AI Risk Control Testing for Real-World Assurance

NIST’s August 2026 TEVV-Athlon draft makes real-world AI evaluation a current governance issue. Businesses should connect every test to pre-agreed acceptance thresholds, a named decision owner and clear retest triggers.

Why Clear Third-Party AI Evidence Requirements Are Non-Negotiable for Risk Management Success

ASD’s Australian Cyber Security Centre and the UK National Cyber Security Centre show why AI supplier assurance must cover the full lifecycle and extended supply chain. Moffatt v Air Canada demonstrates that business accountability remains with the organisation using the automated service.

Turning AI Risk Assessments into Business Accelerators: A Practical Path Beyond Bottlenecks

AI risk assessments often stall innovation when unclear ownership and inconsistent evidence requirements create bottlenecks. Business leaders must own AI risk decisions, supported by clear triage and third-party evidence standards to speed value delivery without compromising controls.