Executive Dashboard · Third-Party Risk Mapping · Free Tool

AI Supply Chain Risk Dashboard™: How Much of Your AI Risk Comes From Third Parties?

Most enterprise AI systems are built almost entirely from components you don't control — foundation models, vector databases, MCP servers, plugins, and open-source packages. Each one is a potential attack vector. This dashboard maps the full dependency chain and scores exactly where your unreviewed exposure sits.

AI Supply Chain Risk Dashboard™ — Map Your Stack

Enter your AI dependencies across 5 categories. Get a risk score, dependency map, unreviewed surface area, and board-ready PDF export.

The Most Underestimated AI Risk Category

Few organisations build their own foundation models. Most deploy AI through a supply chain of third-party models, inference APIs, vector databases, orchestration frameworks, MCP connectors, and open-source dependencies. Each one is an external dependency with its own security posture, data handling terms, and vulnerability exposure — yet most enterprise AI vendor assessments evaluate SLAs, pricing, and general data handling, not model security, inference-time attack resilience, or supply chain transparency.

The result is a structural blind spot: the component making the most consequential decisions in your AI system — the foundation model itself — often receives the least security scrutiny in procurement. The AI Supply Chain Risk Dashboard™ exists to surface that blind spot before an incident does.

The Five Dependency Categories Mapped

Foundation Models

OpenAI, Anthropic, Google, and open-weight models you've deployed — each with distinct data handling terms and training data governance

️ Vector Databases

Pinecone, Weaviate, pgvector, and other retrieval infrastructure storing your embedded enterprise knowledge

MCP Servers

Model Context Protocol connectors giving AI systems tool access — one of the fastest-growing and least-reviewed dependency categories

External APIs

Third-party services your AI systems call directly — each call is a potential data exposure or manipulation point

Plugins & Extensions

Integrations extending your AI applications' capabilities, each with its own permission scope and security posture

Open-Source Packages

The dependency tree beneath your AI pipeline — orchestration frameworks, tokenizers, and supporting libraries, often numbering in the hundreds

How the Risk Score Is Calculated

The dashboard's scoring methodology is transparent by design — every score is traceable to a specific calculation, which is what makes the output defensible in a board or procurement conversation rather than a black-box number.

FactorMethodWhat It Captures
Vendor ScoringWeighted criteriaData residency, SLA terms, audit transparency, incident history, certifications
Open-Source Scalinglog2(n+1) × 8, capped at 60Risk grows with package count but logarithmically — the 50th package matters less than the 5th
Dependency Multiplierscore × (1 + active × 0.05)Each additional active third-party connection compounds total exposure
Supply Chain Depth1 + (depth × 0.03)Multi-tier dependencies (a vendor's vendor) increase risk further
Industry MultiplierFinance 1.1× · Healthcare 1.2× · Tech 1.0×Regulatory and data sensitivity context scales the base score

Reading the Dependency Map and Unreviewed Surface

Beyond the headline risk score, the dashboard visualises your full dependency map — every foundation model, vector database, MCP server, API, plugin, and package category represented as a node, sized by criticality. The "unreviewed surface" metric specifically flags dependencies that have never been through a formal security or vendor risk assessment — typically the highest-leverage finding in the entire dashboard, since it identifies exactly where your blind spots are without requiring you to manually audit every vendor relationship first.

Why MCP Servers Deserve Specific Attention

Model Context Protocol servers are singled out in the dependency categories because they represent a newer and structurally different risk than traditional API dependencies. An MCP server doesn't just exchange data with your AI system — it can grant the AI system tool access, meaning a compromised or malicious MCP connector can translate directly into unauthorised actions, not just data exposure. Most organisations are adopting MCP servers faster than they're developing MCP-specific vendor review criteria, which is precisely the kind of growing-adoption-outpacing-governance pattern the broader AI Security Benchmark 2026 report identifies as the defining risk dynamic of the year.

Who Should Use This Dashboard

CIOs & CISOs

Get a single defensible risk score for the entire AI vendor ecosystem, with the underlying methodology fully transparent for board questions

Supply Chain & Procurement

Identify which AI vendor relationships need security review before renewal, and which new vendor evaluations need AI-specific criteria added

AI Governance Leads

Build the AI vendor inventory required by NIST AI RMF and EU AI Act risk management obligations, with risk scoring already attached

️

Risk Committees

Receive a board-ready PDF translating dependency sprawl into a single comparable risk metric, trackable quarter over quarter

See How Supply Chain Fits Your Overall Posture

Supply chain is one of six domains in the full Coverage & Maturity Dashboard. Benchmark your complete AI security posture against industry peers.

Frequently Asked Questions

What is the AI Supply Chain Risk Dashboard?
A free executive tool that maps and scores third-party risk across your AI stack — foundation models, vector databases, MCP servers, external APIs, plugins, and open-source packages. It produces a risk score, dependency map, and identifies your largest unreviewed attack surface.
How is the risk score calculated?
Using a transparent weighted methodology: vendor criticality scoring (data residency, SLA terms, audit transparency, incident history, certifications), logarithmic scaling for open-source package count, a dependency multiplier for active third-party connections, a supply chain depth multiplier for multi-tier dependencies, and an industry-specific multiplier (Finance 1.1×, Healthcare 1.2×, Technology 1.0×).
Why does open-source package risk scale logarithmically, not linearly?
Going from 5 to 10 open-source dependencies meaningfully increases your attack surface. Going from 200 to 205 does not increase risk by the same proportional amount — the marginal risk of each additional package declines. The log2(n+1) scaling reflects this: it captures the real risk increase at low dependency counts while preventing organisations with naturally large, well-managed dependency trees from being penalised disproportionately.
Can I export this for a board or procurement presentation?
Yes — the Export Report function generates a report including your full dependency breakdown, risk score, unreviewed surface area, and the complete scoring methodology, formatted for executive presentation and procurement documentation.

Related Executive Tools