TL;DR: Third-party breaches in 2025 showed that one compromised supplier could affect many downstream organisations, with 136 verified events, 719 named victims and about 26,000 additional impacted companies, according to Black Kite. Identity governance has to account for delegated access and revocation timing before disclosure arrives.
Editorial analysis by NHI Mgmt Group, based on content published by Black Kite: “2026 Third-Party Breach Report: Managing Risk Concentration in the Era of Cascading Failures”.
By the numbers:
- 2025 saw 136 verified third-party breach events, with 5.28 downstream victims per vendor.
- Black Kite reported 719 publicly named victim companies and about 26,000 additional impacted companies that were never named.
- The median disclosure delay was 73 days, even though detection took 10 days in the events with timeline data.
Key questions
Q: Why does delayed disclosure make third-party breaches harder to contain?
A: Because containment depends on timely revocation, and delayed notice leaves attacker access active while customers still assume the vendor is safe.
Q: How should security teams prioritise third-party risk reviews?
A: Prioritise vendors by both exposure and connectivity.
Q: What breaks when a vendor with deep integration access is compromised?
A: The break is usually in the institution’s identity governance, not just the vendor’s security.
Practitioner guidance
- Inventory third-party trust paths Document every vendor connection that can authenticate, transfer data, or execute actions in your environment, including federated access and API-based integrations.
- Set containment triggers for vendor compromise Predefine when to revoke partner tokens, disable shared accounts, and isolate integrations if a supplier is disclosed or shows compromise indicators.
- Prioritise high-connectivity suppliers first Rank vendors by business criticality and downstream reach, then review the ones whose access can affect the most internal systems or records.
Bottom line: Third-party breach risk is increasingly driven by concentration, where one compromised supplier can affect many downstream organisations.
Glossary terms: Third-Party Breach Concentration, Disclosure Lag, Silent Window, Shadow Layer
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Third-party breach concentration is now an identity governance problem, not just a vendor risk problem. When a supplier can reach many customers, the control question becomes who or what can still authenticate, delegate, or remain trusted after that supplier is compromised. That shifts the centre of gravity from vendor questionnaires to access scope, token lifecycle, and offboarding discipline. Practitioners should treat third-party access as an identity control surface, not a procurement checkbox.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What signals show a vendor relationship is becoming a concentration risk?
A: Look for a vendor that is deeply embedded, hard to replace, and granted broad access to multiple environments or critical workflows. If one supplier can affect many systems, the relationship has become a concentration risk even if its headline cyber score looks acceptable.
👉 Read our full editorial: Third-party breach concentration outpaced disclosure in 2025