A vendor of yours was breached: how does it show up when you sell your CPA, advisory or IT services firm?
Quick answer, Nov 12, 2026As of 12 November 2026, a vendor's breach reaches your sale three ways. State notice law can make the vendor's incident yours to report. If you prepare taxes or advise on money, the FTC Safeguards Rule asks how you chose and checked that vendor. And a buyer's agreement asks you to vouch for your vendors.
A breach at your tax software provider, file-sharing service or outsourced IT firm feels like someone else's problem until a buyer asks about it. Buyers of CPA, advisory and IT services firms ask about your vendors as well as your own systems, and your answer ends up in the purchase agreement. The rules below, and one filed agreement for the sale of an IT managed services business, show where a vendor's incident lands.
Where a vendor's breach lands on you
| What the buyer will ask | What the rule or contract says | Source |
|---|---|---|
| Was the vendor's breach yours to report? | In Florida a vendor holding personal information for you must tell you "no later than 10 days" after it determines a breach. You then owe the notices, and "an agent's failure to provide proper notice shall be deemed a violation of this section against the covered entity" | Fla. Stat. § 501.171(6)(a) and (b) |
| How fast? | Individuals "no later than 30 days after the determination of a breach"; the Department of Legal Affairs too, within the same 30 days, if 500 or more people in Florida are affected | Fla. Stat. § 501.171(4)(a), (3)(a) |
| Does the FTC rule cover my firm? | Its scope names "tax preparation firms", "credit counselors and other financial advisors" and "investment advisors that are not required to register with the Securities and Exchange Commission" | 16 CFR § 314.1(b) |
| Did you choose and check the vendor? | Select providers "capable of maintaining appropriate safeguards", require safeguards "by contract", and periodically assess providers "based on the risk they present" | 16 CFR § 314.4(f)(1) to (3) |
| Did you tell the FTC? | Notice "no later than 30 days after discovery" if the event involves "at least 500 consumers"; the event is "acquisition of unencrypted customer information without the authorization of the individual" | 16 CFR § 314.4(j)(1); § 314.2(m) |
| What will you promise at signing? | That for three years the seller and, "to the Knowledge of the Company or Newtek, each of its Data Partners" has not "experienced any Security Breach impacting the Company". Data Partners include "vendors, processors, or other third parties" | Agreement and Plan of Merger, 11 August 2024, § 4.21(m)(ii) and Exhibit A, "Data Partner" |
| What if the promise turns out wrong? | Representations "survive the Closing through and including the 18-month anniversary", and the buyer recovers first "under the R&W Insurance Policy", a representation and warranty insurance policy | same agreement, § 10.3(e)(i) and § 10.3(d) |
The agreement is Paltalk's purchase of Newtek Technology Solutions from NewtekOne, a business the agreement defines as "information technology managed services, secure private cloud hosting, backup and disaster recovery". Florida is one state's statute, read here because it spells out the vendor's duty; your own states' notice rules are UNKNOWN on this page. Every source was read on 12 November 2026.
Which situation you are in
The vendor told you, and you sent notices. This is the simplest case. Give the buyer the vendor's notice to you, your own notices and what you changed afterwards, and list the incident in the disclosure schedule against the three-year promise rather than leaving the buyer to find it.
The vendor told you, and nobody decided whether notice was owed. Settle it with counsel before a buyer reads the file. The Safeguards Rule treats an event as known once it is "known to any person, other than the person committing the breach, who is your employee, officer, or other agent" (§ 314.4(j)(2)), so a vendor email one staff member read counts.
You never heard from the vendor. The filed promise covers vendors only to the seller's knowledge, defined as knowledge "after due inquiry" of directors and officers, while excusing "scans, penetration tests or other third party investigations with respect to IT Systems" (Exhibit A, "Knowledge"). You can make that inquiry before any buyer arrives: ask each vendor holding client data, in writing, whether it has had an incident in the last three years.
You are the vendor. An IT services firm holding client data is the "third-party agent" in the Florida statute, "an entity that has been contracted to maintain, store, or process personal information on behalf of a covered entity" (§ 501.171(1)(h)). A buyer then reads your incident history twice: as your own breach, and as the start of your clients' notice clocks. For those firms, see how to sell an MSP and selling an MSSP or GRC firm.
What to have ready
- A list of every vendor that holds client data, ranked by what it holds. NIST's framework states the outcome as "Suppliers are known and prioritized by criticality" (NIST CSF 2.0, GV.SC-04).
- The clause in each contract that requires safeguards (§ 314.4(f)(2); GV.SC-05), and dated records of each periodic review (§ 314.4(f)(3); GV.SC-07).
- Three years of incident records, including every notice a vendor sent you.
- For a tax practice, the written security plan. The IRS, citing the FTC Safeguards Rule, states that "tax return preparers must create and enact security plans to protect client data" (Publication 4557, Rev. 6-2024, "Introduction - Safeguarding Taxpayer Data"), and after a theft asks preparers to "report client data theft to your local IRS stakeholder liaison" (IRS, "Data theft information for tax professionals", "Contacting the IRS and law enforcement").
Where Frontier Desk fits
In the Cybernetic Age more of a services firm's client work runs through outside software, so the vendor list is part of what a buyer is buying. Frontier Desk is the owner's advisor on who would buy or lend, what each checks first, and what is missing before any of them look. The exit roadmap takes two to four weeks and ends with a 90-day plan and a re-check at day 90. Start with a free first look, or see who is buying on markets.
Questions
Does a small firm escape the vendor rules? No. Firms holding information on "fewer than five thousand consumers" are excused from § 314.4(b)(1), (d)(2), (h) and (i) (16 CFR § 314.6). Vendor oversight in § 314.4(f) and the FTC notice in § 314.4(j) still apply.
Will a vendor breach lower my price? UNKNOWN. No public source read today ties a vendor incident to a sale price. The filed agreement shows where the risk went instead: to the insurance policy first, with the seller's own liability for this kind of promise capped at $75,000 (§ 10.3(c)), plus a separate indemnity for "the items set forth on Section 10.1(f) of the Company Disclosure Schedule", whose contents are not public.
Does this apply to an SEC-registered investment adviser? Not the FTC rule. Its scope lists only "investment advisors that are not required to register with the Securities and Exchange Commission" (§ 314.1(b)). A registered adviser's own rules are outside this page.