TL;DR: Third-party dependencies now account for over 35% of data breaches and more than 40% of ransomware starts, according to SecurityScorecard, while AI and shadow AI are lowering attacker effort and widening exposure across enterprise workflows. The governance challenge is no longer internal control alone, but visibility and accountability across the extended digital supply chain.
At a glance
What this is: SecurityScorecard argues that third-party exposure and shadow AI are expanding the CISO remit beyond internal controls to ecosystem oversight and AI governance.
Why it matters: For IAM and security teams, this is a reminder that vendor access, delegated trust, and unmanaged AI use create governance gaps that traditional internal controls do not cover.
By the numbers:
- Over 35% of data breaches now stem from third parties, according to SecurityScorecard research.
- Over 40% of ransomware originates with a third party, according to SecurityScorecard research.
Context
Third-party risk is a governance problem, not just a supplier management problem. Once vendors, partners, contractors, and integrations can open paths into the enterprise, security oversight must extend beyond internally owned systems and credentials.
Shadow AI adds a second layer of exposure because employees can move sensitive data into tools and workflows that were never approved, inventoried, or governed. That creates an identity and access problem as much as a data-handling problem, because the organisation loses control over who can use what service, with which data, and under whose authority.
Key questions
Q: What breaks when third-party access is treated as a one-time procurement issue?
A: Lifecycle control breaks. Vendor and partner accounts, tokens, and integrations outlive their intended use when ownership, review, and revocation are not built into governance. That creates standing trust in external identities, which attackers can exploit through stale access, overbroad permissions, or compromised partner workflows.
Q: Why does shadow AI create such a high breach risk?
A: Shadow AI creates high breach risk because it can access sensitive data outside normal oversight, then process or reproduce that data in places security teams do not control. Once the tool can read privileged information, the organisation may lose visibility into retention, logging, and downstream exposure.
Q: What are the warning signs that AI governance is becoming a control gap?
A: The warning signs are fragmented inventories, undocumented OAuth grants, unclear ownership of AI tools, and inconsistent evidence for what each system can access. If business teams can deploy AI faster than security can enumerate and review it, governance is already lagging. That is the point where the programme needs cross-platform controls, not more isolated approvals.
Q: Who should own third party risk management across security, legal, and procurement?
A: One accountable owner should coordinate the end-to-end vendor lifecycle, even if multiple functions perform different checks. Security can validate technical controls, procurement can manage commercial terms, and legal can govern contract language, but a single owner is needed to ensure findings become action.
Technical breakdown
Why third-party access expands the attack surface
Third-party relationships create a trust boundary that is often broader than the controls applied to internal users. Vendors may authenticate through API keys, tokens, delegated access, or federated sessions, and each path can become an entry point if lifecycle governance is weak. The security issue is not simply that a partner exists, but that the organisation has extended operational trust without always extending equivalent monitoring, revocation, and ownership. That is why third-party exposure behaves like an identity problem as much as a supply chain problem.
Practical implication: treat vendor access paths as governed identities, not as informal integrations.
How shadow AI changes identity and data governance
Shadow AI is the unmanaged use of AI tools or services outside approved governance. From an identity standpoint, the risk is not only data leakage. It is also that employees may authenticate to tools with personal accounts, browser sessions, or opaque delegated permissions that security teams cannot reliably inventory or revoke. From a data standpoint, sensitive material can leave controlled environments without classification or policy enforcement. The control gap is lifecycle visibility: if the organisation cannot see the tool, the account, and the data path, it cannot govern the transaction.
Practical implication: inventory AI tool usage as part of access governance, not just application security.
Why board communication now matters to cyber resilience
When risk extends across suppliers and AI-enabled workflows, CISOs need board-level sponsorship to enforce funding, accountability, and cross-functional action. The article points to a familiar but often underused governance mechanism: security leaders need a direct line into audit and risk forums so that exposure across the extended ecosystem is visible in business terms. That matters because vendor concentration, delegated trust, and AI adoption all change the organisation's risk profile faster than annual review cycles can absorb.
Practical implication: report third-party and AI exposure in governance language that the board can tie to business decisions.
Threat narrative
Attacker objective: Use trusted external relationships and unmanaged AI usage to bypass internal controls and reach sensitive data or systems.
- Entry begins through a trusted third-party relationship, such as a vendor integration, delegated access path, or compromised partner workflow.
- Attackers then exploit that trusted path to scale access, blend in with legitimate business traffic, or redirect employees into unsafe AI and social engineering workflows.
- The objective is to reach data, credentials, or internal systems through the extended digital supply chain rather than through direct perimeter attack.
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.
- BeyondTrust breach 2024: A stolen BeyondTrust Remote Support API key let a China state-sponsored actor reset accounts and reach US Treasury workstations in 2024.
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 access is now an identity governance problem, not only a supplier risk problem. When vendors, partners, and contractors can authenticate into the environment, the control question shifts from procurement to lifecycle governance. Organisations need ownership, review, and revocation for every delegated access path, because the security boundary now includes external identities as well as internal ones.
Shadow AI creates a control plane outside conventional IAM visibility. Employees do not need admin privileges to create risk if they can move sensitive data into unsanctioned AI tools using ordinary accounts or browser sessions. That means access governance must expand from entitlement review to tool governance, data path visibility, and approved-use policy enforcement.
Deepfake and AI-assisted social engineering lower the cost of trust exploitation. The article's warning is not simply that attackers use AI, but that they can manufacture convincing trust signals at scale. This pressures identity controls that assume human review will catch deception, which is why verification and approval workflows need stronger evidence than voice, email, or appearance alone.
Trust amplification is the right concept for this risk pattern. The more an organisation relies on delegated trust, partner access, and AI-assisted interaction, the more quickly small governance gaps become enterprise-wide exposure. Security leaders should treat trust amplification as a board-level risk indicator, because it measures how far a local failure can spread across the ecosystem.
The CISO mandate is becoming a governance translation function. Technical controls still matter, but the decisive task is now to explain how third-party exposure, AI adoption, and identity trust affect business resilience. That means security teams need evidence, metrics, and accountability structures that the board can act on.
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
Trust amplification: the real problem is not only that third parties exist, but that delegated trust can multiply risk faster than internal review cycles can reduce it. Security teams should therefore track third-party access, OAuth grants, and approved AI usage as part of the same governance conversation.
Shadow AI pushes identity governance into the workflow layer. If employees can move confidential data into AI tools without a sanctioned account, the organisation has an access problem as much as a data problem, and that gap will show up first in policy exceptions and shadow usage patterns.
For practitioners
- Map all third-party access paths Inventory vendor, partner, and contractor accounts, tokens, API keys, and federated connections, then assign an owner and expiry rule to each path.
- Govern shadow AI as an access problem Track approved and unapproved AI tools, identify which identities can use them, and block sensitive-data transfer where policy or legal review is absent.
- Separate board reporting from operational reporting Present third-party concentration, AI usage exposure, and trust-boundary exceptions in board language that ties risk to business dependencies.
- Test for delegated trust failure modes Review integrations, OAuth grants, and support channels for overbroad permissions, weak offboarding, and lack of monitoring on external identities.
Key takeaways
- Third-party access and shadow AI are now governance issues that sit alongside traditional internal security controls.
- The article's central evidence is that over 35% of data breaches and over 40% of ransomware starts now involve third parties, which raises the stakes for supplier oversight.
- CISOs need to report ecosystem risk in board terms, with ownership, visibility, and revocation built into the operating model.
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 | The article centres on third-party access paths and delegated external trust, which map directly to third-party NHI exposure. |
| NHI-10 — Human Use of NHI | Shadow AI and unmanaged tool use reflect employees using external systems outside approved identity governance. | |
| Recommendation — Inventory and govern third-party identities with the same lifecycle controls you apply to internal privileged access. Block unsanctioned use of AI tools by tying approved access to managed identities and policy enforcement. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The article emphasises permissions and accountability across vendors, partners, and AI workflows. |
| Recommendation — Review external entitlements continuously and revoke access paths that lack a clear business owner. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | The breach pattern described relies on trusted access and movement through third-party paths. |
| Recommendation — Map third-party compromise paths to credential access and lateral movement techniques in detection content. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Cloud ecosystems depend on governed identities for vendors, partners, and integrations. |
| Recommendation — Apply cloud IAM controls to every external identity and integration that can reach production data. | ||
Key terms
- Third-Party Identity: An identity issued to a partner, vendor, contractor, or external service that can access internal systems. These identities often sit outside normal employee governance and can become persistent trust paths if they are not reviewed, expired, and revoked on schedule.
- 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.
- Delegated trust: Delegated trust is the decision to let another system or organization issue, validate, or transmit access on your behalf. It is common in cloud and SaaS environments, but it becomes risky when scope, duration, and revocation are not tightly controlled. In NHI governance, delegated trust must be explicit and continuously reviewable.
- Trust Amplification: A condition where a small identity or policy exception expands into a much larger attack path after compromise. In Microsoft 365, broad allow lists, unmanaged device enrollment, and default external access settings can multiply the effect of one stolen credential or one trusted sender.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, human identity, and secrets management in the context of modern access risk. It helps practitioners translate identity control into programme-level decisions across security, IAM, and governance teams.
Published by the NHIMG editorial team on July 11, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org