← Return to the book

FUTURECENTRAL PRESS · APPLIED EXERCISE SAMPLE

Compliance, Risk, and AI Governance

A Guide for Compliance Professionals in Financial Services

Chapter 29: Third-Party and Vendor Risk Architecture for AI: Foundation Model Dependencies, Concentration Risk, and the Contractual Architecture

Foundation model dependency mapping, concentration risk on AI providers, the contractual architecture for exit, audit, liability and indemnity, cloud-AI and RegTech vendor risk, and the third-party ecosystem the working DGM must govern.

AI Vendor Risk Exercise Sample

This sample shows the applied work in Compliance, Risk, and AI Governance: A Guide for Compliance Professionals in Financial Services. Examine the five-layer AI Vendor Risk Architecture, work through the five-step maturity audit and consider eight reflection questions. The deliverable is a one-page audit identifying two commitments to bring to the next Vendor Risk Committee.

Framework overview

The chapter's architectural commitment, made operational, is a five-layer AI Vendor Risk Architecture the working DGM operates as a single institutional discipline. Each layer is an institutional commitment, not a workstream; the layers operate concurrently, with the Friday Vendor Risk Committee meeting as the institutional venue at which the layers are reconciled.

Layer 1: AI Vendor Categorisation Architecture. The institutional discipline of distinguishing the four categories (foundation model provider, AI platform provider, AI tool provider, AI service provider) and applying the appropriate risk treatment to each. The categorisation governs due diligence depth, contractual provisions, monitoring intensity, continuity expectations, and exit planning. Failure mode: the institution treats all AI vendor relationships as a single category and applies a generic risk treatment that is too deep for some relationships and too shallow for others.

Layer 2: Due Diligence and Onboarding Architecture. The conventional due diligence (financial stability, operational maturity, control environment, regulatory standing, business continuity) extended with AI-specific elaboration: training data provenance, model behaviour stability history, safety evaluation, data use practices, version change discipline, jurisdictional exposure. Due diligence depth is calibrated to vendor category and proposed materiality. Onboarding addresses access controls, data flow architecture, integration discipline, monitoring instrumentation, and the institutional documentation regime that supports the relationship through its life.

Layer 3: Contractual Architecture. The ten contractual provisions of §29.3 (data flow, model behaviour and version stability, liability, indemnification, continuity and exit, supervisory access and audit, incident response, information security, regulatory compliance, change management) operated through a documented institutional playbook. Every gap between the playbook and the as-negotiated contract is a named institutional risk acceptance approved at appropriate seniority. The playbook is updated as the regulatory perimeter and the institutional risk position evolve.

Layer 4: Concentration Risk and Continuity Architecture. The foundation model dependency map, the substitutability assessment for each material dependency, the institutional concentration posture the board has affirmed, the fallback architecture for each material deployment, the exit plan for each material relationship, the periodic exit drill discipline. The continuity architecture is exercised, not declared. The supervisor reads the drill log as the test of whether the continuity architecture is real or fictional.

AI vendor risk integrates with operational risk (Chapter 28), regulatory reporting (Chapter 27), cyber risk (Chapter 30), data protection, model risk (Chapter 21), and supervisory engagement. Vendor-related loss events feed the operational risk taxonomy; vendor data quality affects reported figures; and the vendor cyber surface affects the institution’s cyber posture. Integration operates at six points: policy, governance, data, reporting, people, and training.

The Architecture's use, for the working DGM. The five layers are not a maturity ladder the institution climbs sequentially; they are concentric architectural commitments the institution operates simultaneously, with the Vendor Risk Committee as the institutional rhythm at which the layers are reconciled, the Risk Management Committee of the Board as the senior governance machinery at which the architecture is affirmed, and the supervisor's examination as the external test of the architecture's adequacy.

Applied exercise

For this chapter, the deliverable is a one-page maturity audit of the AI vendor risk function at the working DGM's own institution, measured against the five-layer AI Vendor Risk Architecture this chapter develops. The audit takes approximately ninety minutes to complete and produces a paper the DGM can take to the next Vendor Risk Committee with the institutional posture the function should hold and the two architectural commitments the function should make in the next ninety days.

Step 1, the vendor categorisation and dependency map audit (twenty minutes). Pull the institution's AI vendor inventory across all four categories: foundation model provider, AI platform provider, AI tool provider, AI service provider. Map each material deployment to the foundation model provider it depends on. Identify the bank's top three concentration positions on foundation model providers. Note whether the concentration profile has been examined by the Risk Management Committee of the Board within the past twelve months. Concentration positions the senior governance machinery has not examined deliberately are the first finding the audit surfaces.

Step 2, the substitutability and contractual playbook audit (twenty minutes). For the bank's top three foundation model dependencies, pull the substitutability assessment. Read for currency (within the last twelve months), for credibility (a migration window the institution could actually operate), and for completeness (alternative provider, operational cost, migration timeline, residual capability gap). Compare the as-negotiated contracts with the institutional contractual playbook on the ten provisions of §29.3 and identify the gaps. Gaps documented as institutional risk acceptances at named seniority are acceptable findings; gaps undocumented are the second finding.

Step 3, the continuity and exit drill audit (twenty minutes). For each of the bank's top three material AI vendor relationships, name whether the institution has a documented exit plan, whether the exit plan has been reviewed within the last twelve months, whether the fallback architecture has been exercised in tabletop drill within the last twelve months, and whether the substitutability assessment is operationally credible against the exit plan. Unexercised continuity arrangements, stale exit plans, and operationally non-credible substitutability assessments are the third finding.

Step 4, the regulatory perimeter reconciliation audit (twenty minutes). Confirm whether the institution's third-party risk discipline reconciles with the RBI Master Direction on Outsourcing of IT Services (10 April 2023) and the RBI Master Direction on Outsourcing of Financial Services on the foundational expectations; with the SEBI June 2025 AI/ML consultation paper and the RBI FREE-AI Report (13 August 2025) on AI-specific expectations; with the IRDAI Information and Cyber Security Guidelines (2023, revised 2026) for insurance-touchpoint operations; with the DPDP Act 2023 and DPDP Rules 2025 on data fiduciary obligations; with the CERT-In Direction (No. 20(3)/2022-CERT-In, 28 April 2022, effective 27 June 2022) on cyber incident reporting; with the EU DORA (Regulation (EU) 2022/2554, applicable 17 January 2025) for EU touchpoint operations; with the Federal Reserve SR 23-4 (June 2023) for US touchpoint operations. The fourth finding is reconciliation gaps.

Step 5, the personal positioning (ten minutes). From the four prior steps, name the two architectural recommendations the working DGM would take to the Vendor Risk Committee within ninety days. The recommendations should each be a specific architectural commitment the institution is, after the audit, prepared to defend: a deepening of the foundation model dependency map, an institutional refresh of the contractual playbook against the supervisory perimeter, a continuity drill cycle the function will execute, a substitutability assessment refresh on the top three foundation model dependencies, a reconciliation discipline across the multi-layer regulatory perimeter. Vague recommendations are themselves a finding the audit has surfaced) the function's architectural commitments are not yet at the altitude the senior governance machinery expects.

Reflection questions

One. At your institution, how is the boundary drawn between AI vendor risk and conventional vendor risk, and is the boundary producing operational clarity or operational confusion in the institutional vendor risk function?

Two. When your institution evaluates an alternative foundation model provider, what is the institutional process, who is involved, and is the process producing the institutional intelligence the substitutability assessment requires?

Three. What is your institution's contractual playbook on foundation model provider relationships, and on which of the ten provisions of §29.3 does the playbook fall short of the institutional risk position the institution actually holds?

Four. How does your institution's exit planning for foundation model provider relationships compare to the operational reality of conducting the exit, and where is the credibility gap?

Five. What is your institution's senior governance posture on foundation model concentration, and is the posture one the Risk Management Committee of the Board has owned deliberately or one that has accumulated by default through individually defensible procurement decisions?

Six. How does your institution's data protection position (DPDP Data Fiduciary discipline) interact with the foundation model providers' standard data use practices, and where is the institutional position weak in contractual or operational terms?

Seven. At what point does the commercial pressure on AI vendor renewal terms exceed the institutional risk position, and how does the institution's governance architecture resist the pressure?

Eight. What would your institutional regulator find in a deep supervisory examination of the AI vendor risk discipline today, and what is the institutional defence the working DGM would mount?