Baker Tilly's Breach Notice Shows Why Your Accounting Firm Is Now Part of Your Attack Surface
Cybersecurity

Baker Tilly's Breach Notice Shows Why Your Accounting Firm Is Now Part of Your Attack Surface

The advisory giant disclosed that Social Security numbers and other client data sat exposed on an unnamed third-party platform for weeks before the review finished, a timeline that enterprise security teams should be asking their own professional services vendors to match or beat.

PublishedNovember 22, 2026
Read time5 min read
Share

A trusted advisor becomes a disclosure notice

Baker Tilly Advisory Group, one of the larger accounting and advisory firms serving enterprise clients, notified affected individuals that their personal data was exposed through a platform operated by a third-party service provider the firm uses for client services. The notice does not name the provider, which is common practice in early breach disclosures but leaves affected organizations unable to independently assess whether that same provider touches other parts of their own vendor ecosystem.

The exposed data, according to a filing with the Texas Attorney General, includes Social Security numbers, full names, addresses, and other personal information belonging to clients and their dependents. Baker Tilly's own notice is vaguer, describing the data types as a placeholder rather than an itemized list, which is a pattern regulators have increasingly pushed back on as firms are expected to be specific once their internal review is complete.

The seven-week gap between discovery and clarity

Baker Tilly learned of the incident on September 6, 2026, and did not finish reviewing the affected data until October 28, more than seven weeks later. That gap is common for breaches involving third-party platforms, where the affected organization has to request logs and data extracts from a vendor it does not directly control. It is still a meaningful amount of time during which affected individuals remained unaware their Social Security numbers might be circulating, and the delay itself is worth scrutinizing separately from the breach that caused it.

For any enterprise relying on an outside accounting, audit, or advisory firm, this timeline is worth benchmarking against your own vendor contracts. If your agreements with professional services firms do not specify a maximum notification window following discovery of a breach involving your data, Baker Tilly's seven weeks is a realistic worst case to plan around, not an outlier you can assume will not happen to your own engagement.

What the numbers actually tell you, and what they do not

The only concrete figure available comes from Texas Attorney General filings, which show 10,456 affected individuals in that state alone. Baker Tilly's own notice gives no national or global total, which means the real scope of this breach, across every state and jurisdiction where the firm has clients, remains unknown to anyone outside the company and whatever regulators receive similar state-level filings.

This pattern, where a single state's mandatory disclosure law surfaces a hard number that the responsible company itself declines to confirm more broadly, is common enough that enterprise risk teams should build a habit of checking state AG breach portals directly rather than relying solely on a vendor's own public statement, since the fuller picture is often scattered across multiple state filings rather than consolidated in one place.

Why Social Security numbers change the risk calculus

Unlike a password or even a credit card number, a Social Security number cannot be reset after exposure, which makes this category of breach fundamentally different from most corporate data incidents in its long-tail risk. Baker Tilly is offering 24 months of credit and identity monitoring through Experian, a standard remedy that is useful but finite, while the exposed data itself remains usable by a patient attacker well beyond that monitoring window's expiration.

Enterprises whose employees or executives had tax, payroll, or financial data flowing through Baker Tilly's affected systems should not treat a 24-month monitoring offer as closing the loop on their own risk. Internal fraud monitoring, particularly around new-account and credit-related alerts for affected individuals, should extend well past whatever window the responsible vendor's remedy covers, since Social Security number misuse frequently surfaces years after the original exposure.

The accounting-firm blind spot in vendor risk programs

Most enterprise third-party risk programs focus heavily on technology vendors: cloud providers, SaaS platforms, and software suppliers with direct system access. Professional services firms, accountants, auditors, and advisory shops often receive lighter scrutiny because the relationship feels more like a trusted human partnership than a technical integration, even though these firms routinely handle some of the most sensitive data an enterprise has, including payroll, tax filings, and merger diligence materials.

This breach is a direct argument for closing that gap. Ask your accounting and advisory firms the same third-party platform questions you would ask a software vendor: which external services touch our data, how is that access logged and monitored, and what is your contractual commitment on breach notification timing. If those questions have never been asked of your current advisory relationships, this disclosure is a reasonable prompt to ask them now rather than after your own data turns up in a similar notice.

What to do this week if you are a Baker Tilly client

If your organization or its executives and employees have any relationship with Baker Tilly, confirm directly with your engagement contact whether your specific data was among the affected records, rather than waiting for a mailed notice that may take additional weeks to arrive given the firm's own multi-week internal review timeline. Early confirmation lets you start your own internal monitoring sooner.

More broadly, use this disclosure as the occasion to audit which of your professional services relationships, beyond Baker Tilly specifically, have never been asked to disclose their own third-party platform dependencies. A breach notice from one firm is often the most effective prompt an enterprise security team gets all year to ask the same uncomfortable questions of every other vendor handling similarly sensitive data.

Tagged#news#security#cybersecurity#breach#cisa#ransomware#zero-day#supply-chain#ai-security#baker-tilly#accounting-firm-breach#social-security-numbers#professional-services#third-party-risk#vendor-risk