Concern 899 · Working draft · editorial review in progress
Fourth-party risk
Fourth-party risk comes from the organizations and components behind an AI supplier, which the customer may not directly choose or contract with.
Understanding the concern
An AI application can rely on a separate model provider, cloud host, data service and outside software. A change or failure in one of those layers can affect the customer even when the visible supplier has not changed. Data may also pass through organizations the customer did not initially expect.
Provider subprocessor lists show one part of this chain. They are useful disclosures, but they do not explain every technical dependency or establish that all uses are safe. Think of a restaurant's ingredient suppliers: you deal with the restaurant, yet upstream quality still matters. Contracts, updates and incident coordination need to account for those less visible relationships.
An example
A purchased AI service changes its underlying model provider, altering where data is processed and how results behave.
Illustrative unless identified as a documented case.
Words in plain English
- AI
- Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.
- Model
- The learned part of an AI system. It uses patterns found during training to produce an answer or prediction.
Evidence and its limits
The provider disclosure is a concrete example; NIST supply-chain guidance is broader. The entry does not claim that a listed subprocessor has failed or misused data.
Anthropic · Provider disclosure
Trust Center: security, compliance and subprocessors ↗ (opens in a new tab)Lists infrastructure subprocessors and updates. A visible example of a service dependency chain, not proof of a breach or complete visibility into every component.
NIST · SP 800-161 Rev. 1 · updated 2024 · Official guidance
Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations ↗ (opens in a new tab)Addresses technology supply-chain visibility, integrity and supplier risks across products and services.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
- NIST AI RMF (opens in a new tab)
framework
- ISO/IEC 42001 (opens in a new tab)
standard
A question to discuss
Which upstream dependencies matter to our use, and how will we learn about significant changes or incidents?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Trustworthiness
Trustworthiness means giving people good reasons to rely on you. It grows when promises, actions, and evidence line up. With AI, a friendly voice or a famous brand is not enough: people need to know what was checked and what could still go wrong.
In practice, keep promises small enough to test, record mistakes, and tell people when the tool's limits affect them. If a service promises human review, make sure a person really has time and authority to review it.
Ask together: What would give the people affected a sound reason to trust this use?
Stewardship
Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.
Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.
Ask together: What are we responsible for caring for over time?
Prudence
Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.
Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.
Ask together: What is a careful next step, and when should we stop or change course?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.