Topic starter
11/07/2026 8:25 pm
TL;DR: AI risk is outpacing static third-party reviews because vendors can add models, features, and data flows without clear signalling, while systems also drift over time, according to OneTrust. Governance now has to be continuous, cross-functional, and explicit about acceptable use, data boundaries, and human review.
Editorial analysis by NHI Mgmt Group, based on content published by OneTrust: “Uniting AI Governance, Risk Management to Accelerate Responsible Growth”.
Key questions
Q: How can organisations govern third-party AI systems without losing accountability?
A: They need explicit ownership, control evidence, and review cadence for every external AI dependency.
Q: Why do static vendor reviews fail for AI governance?
A: Because AI systems are dynamic and can change through retraining, feature updates, and new data flows long after the original assessment.
Q: What are the signs that AI governance controls are not keeping pace with adoption?
A: Common warning signs include unclear ownership for AI use cases, inconsistent approval processes, limited visibility into where sensitive data enters models, and weak evidence for audits or assessments.
Practitioner guidance
- Define AI reassessment triggers Reassess third-party AI systems when vendors add features, change model behaviour, alter data handling, or expand human-review scope.
- Inventory embedded AI features Scan existing applications and vendor contracts for AI functionality that is not obvious from product branding or sales language.
- Map AI use cases to identities and permissions Document which service accounts, tokens, integrations, or delegated identities an AI system uses to access data or trigger actions.
Bottom line: AI governance fails when organisations treat third-party AI as a one-time procurement risk instead of a continuously changing control surface.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/07/2026 8:55 pm
Static third-party risk is the wrong control model for AI. AI features can emerge inside existing products, change behaviour after deployment, and alter the risk profile without a new procurement event. That means the governance failure is not just incomplete due diligence, but the assumption that vendor approval remains valid after launch. Practitioners should move to continuous control validation rather than periodic re-review.
A few things that frame the scale:
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should marketing, privacy, and security teams share accountability for AI use?
A: Marketing should own the use case, privacy should define the permission boundary, and security should enforce the control path in the systems that activate data. The shared rule is simple: no AI workflow should use customer data unless the purpose, lineage, and revocation path are all clear.
👉 Read our full editorial: AI governance must evolve beyond static third-party risk reviews