Closing the Blind Spot: Managing Artificial Intelligence (AI) in Third-Parties

When AI is not built in-house but embedded within vendor platforms, outsourced services, or third-parties, organisations face a hidden layer of risk. These risks can include compliance gaps, operational surprises, privacy breaches, and diminished control over AI decisions. Yet many boards and executives assume vendor assurances are sufficient and fail to probe deeper.


The 30-second take

Organisations increasingly depend on AI embedded within third-party services, but governance is lagging behind.

Blind trust in vendor assurances exposes businesses to risks that remain their responsibility. To manage these risks, boards and leaders must clarify AI use cases, demand specific evidence addressing local legal and operational realities, and embed clear ownership and control mechanisms.

Effective risk management means treating third-party AI supply chains as integral—not external—parts of your ecosystem.

Try our quick AI readiness snapshot to see where you stand today.

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.

Third-party AI is a growing source of hidden risk

Many AI deployments rely on components developed or hosted by vendors, cloud providers, suppliers, or outsourced service partners. Examples include sentiment analysis tools baked into call centre platforms, credit scoring algorithms embedded in loan origination systems, or AI-driven chatbots provided by third parties.

While these arrangements can speed adoption and reduce development costs, they introduce complexity:

  • Organisations often do not have full visibility into the AI models, training data, or update cycles used by vendors.
  • Vendor risk assessments may be generic, omit jurisdiction-specific privacy laws, or overlook operational dependencies.
  • Changes by vendors—such as model updates, data sourcing changes, or shifts in hosting location—can alter risk profiles without the organisation’s immediate knowledge.

These factors create blind spots that can lead to compliance breaches, unexpected operational disruptions, or reputational damage.

Why vendor assurances need independent scrutiny

Vendors understandably want to reassure customers that their AI technology is safe, compliant and tested. They often provide privacy impact assessments, security certifications, or model governance documentation.

However, accepting these assurances at face value is risky because:

  • Vendor assessments are rarely tailored to the customer’s specific use case, data flows, or jurisdictional requirements.
  • Third-party evidence quality varies widely and may lack detail on controls, monitoring, or incident response capabilities.
  • Vendors typically do not assume liability for downstream risks arising from the AI’s business impact or regulatory obligations.

Business and risk leaders must treat vendor evidence as one input, not the entire assurance picture.

Embedding ownership and accountability within your organisation

Effective management of third-party AI requires clear ownership.

The business area using or procuring the AI-enabled service must own the risk and benefits. Control teams—including risk, privacy, cyber, and legal—play advisory and challenge roles but should not be the primary owners.

Clear ownership means:

  • Defining the AI use case purpose, customer impact, and operational dependencies upfront.
  • Understanding the data flows and privacy implications specific to your organisation and jurisdiction.
  • Owning risk triage decisions and escalation pathways.
  • Driving timely engagement with vendors to clarify evidence and trigger reassessment when changes occur.

Practical evidence demands and monitoring

To gain meaningful assurance, organisations should require vendors to provide tailored evidence aligned with their risk profile and obligations. This can include:

  • Detailed privacy assessments covering all applicable laws, including state-level regulations.
  • Cybersecurity documentation detailing access controls, incident response, logging, and data protection measures.
  • Information about AI model training data, update frequency, bias mitigation, and validation results.
  • Subcontractor disclosures and governance arrangements for model supply chains.
  • Formal change management and notification processes for model, data, or service modifications.

Beyond initial evidence, ongoing monitoring is critical.

Organisations should establish indicators for AI performance, drift, incidents, and compliance triggers. This helps identify emerging risks and supports continuous improvement.

Innovation of Risk thinking: Know Your AI

Just like anti-money laundering requires you to Know Your Customer (KYC), using AI means you must Know Your AI (KYA).

Our work at the Innovation of Risk has highlighted the need to view AI embedded within vendors and third parties as part of your own risk ecosystem. It challenges you to ask:

  • Is AI embedded in the vendor service or technology stack?
  • What assurance has the vendor provided and what has the organisation independently checked?
  • Are local legal, privacy and regulatory obligations addressed clearly by the vendor with evidence?
  • What happens if the vendor changes the model, data, location or service design?

The model encourages risk owners to move beyond accepting vendor claims and instead develop tailored, evidence-based controls that reflect their unique operational environment and regulatory context.

“Blind trust in vendor assurances is a risk blind spot. Leaders must demand tailored evidence and clear ownership to manage embedded AI risks effectively.”

The Wrap: Questions to test your AI supply chain risk maturity

  • Do you have a standard approach (assessment) to know your AI (KYA) across your organisation?
  • Have you identified and documented all AI use cases embedded in third-party services across your organisation?
  • Do your vendor contracts specify detailed AI risk, privacy, and security evidence requirements aligned with your jurisdiction?
  • Is there a formal process to review and challenge vendor evidence rather than accept generic assurances?
  • Do you have clear accountability for AI risk owned by the business area using the embedded AI?
  • Are change management and incident notification processes established with vendors for AI components?
  • Is ongoing monitoring in place to detect AI model drift, performance changes, or compliance issues in third-party AI?

Closing the third-party AI risk gap is not about blocking innovation.

It is about enabling smarter, safer AI adoption that respects your organisation’s responsibilities.

Leaders who embed ownership, demand tailored evidence, and monitor continuously will turn vendor dependency from a blind spot into a managed advantage.


More from the Reading Room

Using AI Risk Management to Accelerate Innovation

New Diligent Institute / Governance Institute of Australia data shows 61% of Australian boards restrict employee AI use while only 13% have an AI-literate director — proof that restriction and real governance are pulling apart. NIST's expanding AI Risk Management Framework and the EU AI Act's 2 August 2026 third-party accountability deadline show how structured, evidence-based workflows are what actually let AI adoption move faster, safely.

The Qantas privacy finding: a positive lesson in third-party oversight

A serious data breach does not automatically mean governance failed. The more important question is whether an organisation can demonstrate that it understood the risks,...

APRA’s CPS 230 Tweaks: Small Amendment, Big Governance Signal

APRA has released final targeted amendments to CPS 230 Operational Risk Management. The item is current and sits within APRA’s prudential framework, so boards and risk teams should treat it as a live governance and…

AI Agents and Non-Human Identity Risk

When a single ungoverned AI tool gave attackers a path from a Vercel employee’s device into Vercel’s internal systems, and a poisoned VS Code extension let attackers pull roughly 3,800 repositories out of GitHub, the common thread wasn’t a coding flaw — it was an unmanaged non-human identity. With AI agents now driving machine identities to roughly 109 per human inside the average enterprise (CyberArk, 2026), most governance frameworks still treat identity as a human-only problem.