Join our Newsletter — 33% off our NHI Course

Did 136 third-party incidents reach beyond the 719 named victims?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Third-party breach propagation extended far beyond named victims, with 27 incidents affecting roughly 26,000 more organisations only in aggregate, according to Black Kite. Delegated access paths and shared platforms need tighter review because disclosure lag can hide how far one incident has spread.

Editorial analysis by NHI Mgmt Group, based on content published by Black Kite: “2025 Incidents”.

By the numbers:

  • 136 verified third-party breach events were publicly disclosed in 2025, breaking the previous pattern of more stable yearly volumes.
  • 719 publicly impacted companies were named across those incidents, which captures only the disclosed portion of the downstream blast radius.
  • 27 separate incidents disclosed downstream impact only in aggregate, hiding approximately 26,000 additional affected companies.

Key questions

Q: Why does disclosure delay make supply chain breaches worse?

A: Disclosure delay extends the period in which stolen or misused credentials remain active.

Q: How should security teams reduce the blast radius of edge compromise?

A: Treat internet-facing gateways as entry points into identity risk, not isolated infrastructure assets.

Q: What breaks when third-party access is not reviewed continuously?

A: The break is that access stays active long after the business relationship, vendor task, or application purpose has changed.

Practitioner guidance

  • Map all delegated vendor access paths Inventory OAuth grants, API keys, service accounts, and connected apps that allow vendors or SaaS tools to act inside your environment, then rank them by blast radius and business criticality.
  • Pre-stage emergency revocation for third-party credentials Define who can disable tokens, connected apps, and service accounts when a supplier is suspected of compromise, and make that authority available before vendor confirmation arrives.
  • Treat disclosure lag as a control gap Assume a vendor may know about an incident long before customers are notified, and test whether your monitoring can detect misuse of shared integrations during that window.

Bottom line: Third-party breaches are increasingly measured by how far they propagate, not just by how many vendors are named.

Glossary terms: Third-Party Risk Propagation, Disclosure Lag, Delegated access path, Shared Failure Domain

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Third-party risk has become a trust orchestration problem, not a vendor list problem. The article shows that the material risk is no longer limited to direct supplier failure, but to the web of integrations, credentials, and delegated access that make one compromise reusable across many organisations. That shifts governance from static due diligence toward continuous trust mapping across identity-bearing relationships. Practitioners should treat every shared integration as a live control surface.

A few things that frame the scale:

  • Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.

A question worth separating out:

Q: What is the difference between third-party risk management and SaaS app governance?

A: Third-party risk management looks at the full supplier relationship, including contract, due diligence, and ongoing monitoring. SaaS app governance focuses on the actual permissions, tokens, and connected applications that move data or actions between systems. Organisations need both because a supplier can be low risk on paper while its connected app still exposes highly privileged access.

👉 Read our full editorial: Third-party breach cascades now outpace disclosure and naming


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.