The annual vendor questionnaire asks whether a supplier has a security policy. The third-party data breach vendor risk management problem landing this year asks a different question: how many of your customers’ records sit in a SaaS tool someone signed up for with a corporate card. New case data from Kroll makes that gap hard to ignore.
What Kroll Actually Measured
On October 22, 2026, Kroll published its Data Breach Outlook 2026: The Third-Party Domino Effect. The firm analyzed data breach incidents handled by its Cyber and Data Resilience practice between June 2025 and June 2026, and ran a companion survey of 250 risk and compliance leaders, C-suite executives, and board members. These are Kroll’s own cases and survey respondents, not a census of every breach worldwide. Treat the figures as vendor data from that caseload.
Two numbers drive the headline. First, 69% of affected individuals in those incidents “were breached due to a third-party breach,” as Kroll’s publication page puts it. Second, of that third-party group, 79% “were from the technology sector,” compared with finance (9%), insurance (6%), and healthcare (5%). Kroll’s press release says the same thing another way: 79% of those third-party-affected individuals “were affected by a breach from the technology sector.” Technology firms also accounted for 60% of all affected individuals in the caseload, including direct and supply-chain incidents.
That is why I changed the sheet title. “Most third-party breach victims were hit through a tech vendor” is directionally right, but Kroll’s wording is “technology sector” or “technology firms,” and the precise claim is 79% of third-party-affected individuals in its June 2025–June 2026 cases. Kroll does not publish a product taxonomy that separates SaaS from on-prem software or MSPs. Denyl Green, Kroll’s global head of breach notification, describes the link as “a vendor, software supplier or service provider.”
Organizations Breached Versus People Affected
Count companies instead of people and the picture flips. Finance was the most breached industry by organization count, at 20% of Kroll-handled breaches in the period. Professional services also accounted for 20%. Technology ranked only seventh by number of organizations breached, about 6% of incidents in press coverage of the report, yet first by total individuals affected. Insurance ranked ninth by organizations breached and second by people affected.
Kroll’s point is the domino effect. “One vendor compromise can generate breach notifications for dozens or hundreds of downstream organizations that never touched the vulnerable system directly.” Green puts it in operational terms: when a supplier is breached, every client still has to decide whose data was affected and whether customers and regulators need notice. The survey side of the report adds that 54% of IT and technology leaders named vendor and third-party breaches as their biggest compliance risk, versus 40% of C-suite executives and 30% of risk and compliance leaders, and that dependence on vendors was among the top four breach-response challenges, cited by 41% of respondents.
My Recommendations: Rebuild Reviews Around Who Holds the Data
Everything in this section is my opinion, not Kroll guidance and not legal advice. If blast radius tracks the firms that hold many customers’ data, the review should start there, not with the longest questionnaire.
- Inventory who actually holds or can reach personal data. List every SaaS product, file-transfer tool, MSP, backup provider, HR or CRM platform, and support vendor that stores, processes, or can export your customer or employee records. Include shadow IT someone bought with a card. If you cannot name the data classes each holds, you cannot tier them.
- Tier by blast radius, not by spend. A low-cost CRM that holds your full customer file outranks an expensive consultancy that only sees sanitized decks. Put high-blast vendors on continuous review: current SOC 2 Type II or ISO/IEC 27001 scoped to the service you use, MFA and logging requirements, and a named security contact.
- Rewrite notification and audit clauses for shared incidents. Require the vendor to tell you within a fixed number of hours, not “promptly,” and to share enough detail for your own regulator and customer notices. Add a right to receive evidence that your tenant was or was not in scope.
- Cut standing access. Prefer customer-controlled encryption keys where the product allows it, time-bound support access, and least-privilege API scopes. A vendor breach is less useful to an attacker if the vendor cannot reach everything by default.
- Run a joint tabletop on a supplier compromise. Decide in advance who owns regulator notice, customer notice, and insurer notice when the first alert comes from a vendor, not from your SOC.
Picture this hypothetical. Your marketing team adopts a new email platform. Six months later that platform discloses a breach affecting multiple customers. If your inventory already shows it holds email addresses and purchase history, notification planning starts the same day. If the tool never made the vendor list, you spend the first week discovering you are in scope. That scenario is my illustration, not a Kroll case.
The Bottom Line
In Kroll’s June 2025–June 2026 cases, most people affected by a breach were affected through a third party, and most of those people were tied to technology-sector compromises. Finance still led in how many organizations were breached. The practical takeaway, in my view, is to rebuild vendor risk around who holds your data and how wide the blast radius is, not around who filled out the longest security questionnaire.
