TL;DR: Supply chain risk now extends through vendors, vendors’ vendors, and shadow AI, with SecurityScorecard’s CEO warning that a small cluster of providers supports a large share of the global attack surface. Compliance alone no longer maps to resilience, and continuous monitoring plus objective cyber KPIs are becoming central to systemic risk management.
At a glance
What this is: SecurityScorecard argues that cyber exposure now extends well beyond direct suppliers into vendors’ vendors and shadow AI use, making systemic risk harder to see and govern.
Why it matters: IAM, NHI, and security teams need to treat third-party access, delegated trust, and unmanaged AI tools as one exposure chain because the failure point may sit several layers beyond the original relationship.
Context
Cyber exposure increasingly follows business relationships rather than network boundaries. When vendors, subcontractors, and service providers are all connected into the same operating model, a weakness in one layer can become an entry point into many others. That is especially relevant to IAM and NHI governance, because delegated access, tokens, and integrations often persist beyond the organisation that originally approved them.
The article frames a familiar control problem in a wider way: compliance checks can exist even when actual resilience is weak. For identity and security teams, the important question is no longer just whether access was approved, but whether third-party, fourth-party, and shadow AI dependencies are continuously inventoried, monitored, and bounded in practice.
Key questions
Q: What breaks when third-party access is not mapped end to end?
A: When third-party access is not mapped end to end, organisations lose sight of who can still reach internal systems after the original business purpose changes. That creates dormant access, weak accountability, and blind spots in incident response. The failure is usually not one supplier alone, but the accumulation of direct and fourth-party pathways that nobody owns cleanly.
Q: Why do vendors' vendors create a larger security problem than simple supplier risk?
A: Because the same upstream failure can affect many organisations at once. A direct vendor compromise is serious, but a widely shared fourth- or fifth-party dependency can scale that compromise across entire ecosystems. The risk grows when organisations cannot see or govern the access those deeper dependencies already have.
Q: How can security teams know whether third-party risk management is working?
A: Look for evidence that inventory, review, monitoring, and revocation are all connected. A working programme produces up-to-date vendor ownership, current access maps, timely reassessments, and documented offboarding. If any of those signals are missing, the programme is probably managing paperwork rather than exposure.
Q: What should organisations do when shadow AI tools connect to business systems?
A: Treat the connection as delegated access and review the tokens, credentials, and permissions involved. If the tool can read, write, or move sensitive data, it belongs in identity governance and NHI oversight, not just application inventory. The practical test is whether the access can be approved, monitored, and revoked like any other service relationship.
Technical breakdown
Why third-party dependence becomes systemic risk
Third-party risk becomes systemic when many organisations rely on the same small set of suppliers, platforms, and managed service layers. At that point, compromise is no longer a local event. It becomes a propagation path through business relationships, integrations, and shared trust. In identity terms, this is not only about access granted to a vendor but also about the downstream identities, tokens, and workflows that vendor can influence. The control challenge is visibility across the full trust chain, not just contract approval.
Practical implication: map direct and indirect supplier access paths, including NHI and API trust points, before you can govern them.
Shadow AI creates an ungoverned data and identity layer
Shadow AI is not just an application governance problem. It is also an identity and data governance problem because users may paste sensitive material into tools that sit outside approved access controls, logging, and retention rules. That creates a parallel trust layer the organisation does not formally manage. If the tool connects to enterprise accounts, services, or documents, the exposure expands from user behaviour into machine-to-machine and delegated access risks. Governance fails when the organisation cannot inventory the tool, the data it touches, or the identities it uses.
Practical implication: bring unapproved AI tools into inventory and assess which identities, tokens, and datasets they can touch.
Compliance can exist without resilience
Compliance is evidence of control design, not proof of operational resilience. An organisation can satisfy audit requirements while still lacking continuous monitoring of supplier exposure, real-time risk signals, or meaningful prioritisation of the highest-consequence dependencies. That gap matters because cyber risk is not evenly distributed. A concentrated provider ecosystem means one weak link can have outsized impact, even when every internal checklist appears complete. Continuous assurance therefore has to sit alongside compliance, especially where third-party access and machine identities intersect.
Practical implication: supplement compliance reporting with continuous supplier risk monitoring and identity-aware control verification.
Threat narrative
Attacker objective: The objective is to pivot through trusted third-party relationships and reach multiple downstream organisations with one compromise.
- Entry begins when attackers compromise a vendor or a downstream supplier that already sits inside the organisation's trust chain.
- Credential or access abuse then spreads through delegated relationships, integrations, or shared accounts that were never fully scoped to the blast radius.
- Impact follows when the same trusted relationship is reused across many customers, turning one compromise into broad exposure across the supply chain.
Breaches seen in the wild
- Vercel Context.ai OAuth Supply Chain Breach: Shadow AI app Context.ai OAuth integration exposes Vercel customer data via unmanaged third-party token.
- Klue OAuth Supply Chain Breach: OAuth tokens compromised in Klue integration breach affecting 700+ organisations via Salesforce data access chain.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Third-party risk has become a governance chain, not a vendor list. The article is right to frame exposure across third, fourth, and fifth parties, because the real control problem is cascading trust. A supplier map that stops at direct contracts misses the identities, tokens, and hosted dependencies that actually carry access. Practitioners should treat the full trust chain as part of the attack surface, not an adjacent procurement record.
Shadow AI is an identity problem as much as a data problem. When employees use unapproved AI tools, they often create unmanaged flows of data, authentication, and delegation outside the security team’s view. That is exactly why shadow AI belongs in the same governance conversation as NHIs and third-party access. The practical conclusion is to inventory tools and the identities behind them together, not as separate controls.
Concentrated attack surface is the right named concept for this risk pattern. A small set of providers now sits behind a disproportionate share of organisational exposure, which means resilience depends on knowing which dependencies can amplify failure across many customers. This is a structural market condition, not a temporary hygiene issue. Practitioners should prioritise the suppliers whose compromise would create the widest downstream blast radius.
Compliance-first thinking is no longer sufficient for systemic exposure. The article’s central warning is that passing audits does not eliminate concentration risk or hidden supplier paths. That matters for boards and CISOs because governance has to measure operational dependency, not just documented process. The practitioner takeaway is to align cyber reporting with real-world dependency concentration and continuous verification.
Third-party access is now inseparable from NHI governance. Vendor accounts, service tokens, and API credentials often outlive the review cycle that approved them, especially in complex ecosystems. If those identities are not continuously scoped and observed, a supplier issue becomes an identity security problem. The practical conclusion is to govern external machine identities as part of third-party risk, not as a separate exception process.
From our research library:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- Read next: Third-Party, B2B and Contractor Access Guide
What this signals
Concentrated supplier ecosystems are pushing cyber risk toward systemic failure modes. When a small set of providers supports many downstream organisations, the right control question shifts from whether a vendor is approved to whether the organisation can absorb a shared-provider failure. That is where third-party inventory, continuous monitoring, and access scoping become board-level resilience controls.
Shadow AI will keep widening the identity perimeter unless teams govern the tools and the credentials together. The practical issue is not only unapproved software but unapproved delegation. If an AI tool can touch enterprise accounts or data, it should be assessed as part of the same access boundary as other third-party services.
Compliance reporting cannot be the last stop for supplier risk. Teams need operational evidence that they can see, score, and contain fourth- and fifth-party exposure before a supplier event becomes a multi-customer incident. The programme implication is clear: dependency concentration must become a recurring control metric, not a one-time review item.
For practitioners
- Inventory the full supplier trust chain Extend inventory beyond direct vendors to fourth- and fifth-party dependencies, hosted services, integrations, and delegated access paths that can inherit exposure.
- Treat shadow AI as an access-control issue List unapproved AI tools, identify what data users share with them, and determine whether enterprise accounts, tokens, or connectors are involved.
- Measure supplier exposure with objective KPIs Track concentration risk, active access paths, and response time for high-impact suppliers rather than relying only on audit status or compliance checklists.
- Govern third-party NHIs as first-class assets Apply lifecycle controls to vendor service accounts, API keys, and tokens so external machine identities are monitored, reviewed, and offboarded on a defined schedule.
Key takeaways
- Third-party risk now extends into nested suppliers, shared platforms, and shadow AI tools that can expand one compromise into many downstream exposures.
- The critical governance gap is visibility, because organisations often know their direct vendors but cannot trace the identities, integrations, and data paths that sit behind them.
- Teams need continuous monitoring and identity-aware supplier controls if they want resilience to match their compliance posture.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST CSF 2.0 and CSA Cloud Controls Matrix set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-03 — Vulnerable Third-Party NHI | Third- and fourth-party exposure in the article maps directly to externally controlled NHI risk. |
| NHI-10 — Human Use of NHI | Shadow AI and unapproved tool use often create unmanaged delegation and access paths. | |
| Recommendation — Inventory and govern third-party NHIs that can propagate supplier compromise into your environment. Restrict human use of unmanaged AI-connected credentials and review any delegated access paths. | ||
| NIST CSF 2.0 | GV.SC-01 — Supply Chain Risk Management Policy | The article is fundamentally about supply-chain exposure and organisational dependency governance. |
| ID.AM-02 — Software, Services and Systems are Inventoried | You cannot govern third-, fourth-, and fifth-party exposure without complete dependency inventory. | |
| Recommendation — Define and enforce supply-chain risk policy across direct and downstream service dependencies. Maintain an inventory of vendors, downstream providers, and AI services that can access your data. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | Supplier compromise often leads to credential abuse and expansion through trusted relationships. |
| Recommendation — Map supplier compromise scenarios to credential access and lateral movement detection paths. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Cloud supplier ecosystems rely on identities, delegated access, and external trust relationships. |
| Recommendation — Apply cloud IAM governance to vendor accounts, service identities, and delegated access. | ||
Key terms
- Third Party Risk: Third party risk is the chance that an outside organization, supplier, contractor, or service provider will create harm for your business. It includes security, privacy, operational, legal, and compliance exposure caused by access to data, systems, or processes. In identity terms, it often arises from shared credentials, integrations, and delegated trust.
- Fourth-party risk: Fourth-party risk is the exposure created by a vendor’s own vendors, sub-processors, and downstream service dependencies. It matters because direct contractual control usually stops at the first tier, while operational and data-risk propagation often continues much further through the chain.
- Shadow AI: AI agents, copilots, or connected tools operating without full visibility or governance from security teams. Shadow AI becomes an identity problem when those systems authenticate with unmanaged tokens, service accounts, or OAuth apps that can reach production resources.
- Systemic Cyber Risk: Systemic cyber risk is the possibility that weaknesses in one organisation spread impact across many others through shared infrastructure, supply chains, or jurisdictional links. It is not confined to a single breach. The concern is cascade effect, where local compromise becomes regional, sector-wide, or national disruption.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and secrets management. It helps practitioners connect delegated access, lifecycle control, and third-party identity risk to their wider security programme.
Published by the NHIMG editorial team on July 12, 2026.
Updated on October 13, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org