Your Software Vendor Had a Data Breach. Here's What to Ask and What to Do Next

The email arrives without warning. Your payroll provider, CRM or file-sharing service has "identified a security incident" and is "investigating with leading experts." It doesn't say whether your data was involved, or what you should do about it.
A vendor data breach is now one of the most common ways small businesses get caught up in a cyber incident they didn't cause. Verizon's 2026 Data Breach Investigations Report found that breaches involving a third party jumped 60% and now make up 48% of all breaches (Verizon).
Short answer: First confirm the notice is real by going to the vendor directly, not through the email. Then get specific answers about your account, your data and any connected logins, and start protecting your side right away. Don't wait for the vendor's final report.
This guide covers how to spot a fake breach notice, the 10 questions to ask your vendor, what to do in the first 72 hours, and when the breach may become your legal responsibility too.
Step one: make sure the notice is real
A real breach is the perfect cover for a fake email. Criminals know customers are expecting messages about password resets and "account verification," so they send their own.
Don't click links or call numbers in the notice. Type the vendor's web address yourself, sign in through the portal you normally use, or call a contact you already have.
Look for the announcement on the vendor's own site or status page.
Save the original email and any attachments. Your insurer, lawyer or IT provider may need them.
Vendor data breach: the 10 questions to ask
Early notices are written for every customer at once. These questions get you answers about your business. Ask in writing, and keep every reply.

Why connected apps matter: the Salesloft Drift breach
In August 2025, attackers used stolen OAuth tokens connected to Salesloft's Drift chat tool to pull data from Salesforce accounts between August 8 and 18. Google's threat intelligence team then warned all Drift customers to treat any token stored in or connected to the platform as potentially compromised, after the attackers also used them to read some Google Workspace email (The Hacker News).
The lesson for small businesses: a breach at one vendor can reach every system you've connected it to. Nobody needed a password. When a connected vendor reports a breach, assume its tokens and integrations need to be revoked and reconnected, not just its password changed.
What to do on your side in the first 72 hours
You don't need the vendor's final report to start protecting yourself.
Change the password for the affected service, and anywhere else employees reused it.
Revoke and reconnect integrations. Disconnect API keys, tokens and app connections tied to the vendor, then set them up fresh once the vendor says it's safe. Have your IT provider do this so nothing else breaks.
Check for unusual activity during the vendor's breach window: logins, data exports, new users, changed payment details and email forwarding rules.
Warn your team about follow-up scams. Expect fake invoices, "updated bank details" requests and password-reset emails that mention the breach.
Call your cyber insurer early. Policies often set notice requirements and may require you to use the insurer's approved responders, so check yours before hiring help.
Write it all down. Keep a simple log of what you learned, when, from whom, and what you did about it.
When a vendor's breach becomes your responsibility
Even if the vendor caused the breach, the data may legally be yours to protect. Depending on what you do and the data involved, you may have your own deadlines.
If you are... | Your duty may include | Deadline |
Any business holding personal information | Notifying affected people under state law. All 50 states have breach notification laws (NCSL). | Varies by state |
A business associate under HIPAA | Notifying the covered entity, such as a medical practice, of a breach (45 CFR 164.410) | No later than 60 days after discovery |
A financial institution under the FTC Safeguards Rule (including many tax preparers, lenders and auto dealers) | Notifying the FTC of an event involving 500 or more consumers (16 CFR 314.4) | No later than 30 days after discovery |
A defense contractor under DFARS 252.204-7012 | Reporting cyber incidents affecting covered defense information to the Department of Defense (DFARS) | Within 72 hours of discovery |
This isn't legal advice. If customer, patient or employee data was involved, bring in a lawyer who handles data breaches before you notify anyone.
Choose vendors with the next breach in mind
You can't prevent a vendor's breach, but you can limit the damage before it happens:
Ask about breach notification before you sign. How quickly will they tell you, and who will they contact?
Share only the data the service needs, and delete old records you no longer use.
Review connected apps every quarter, and remove anything nobody uses.
Keep a list of every vendor that holds your data, with a contact for security issues.
Know how to leave. If you ever need to switch providers, our guide to what happens to your data when you cancel a cloud service covers the exit.
Get help from NexFixIT when a vendor notice lands
A vendor breach notice shouldn't leave you guessing. NexFixIT can verify the notice, get the right answers from your vendor, revoke and reconnect affected integrations, and check your systems for signs of misuse. We'll also help you build a vendor list so the next notice is easier to handle.
Vendor Data Breach FAQs
What should I do when a software vendor reports a data breach?
Confirm the notice is real by going to the vendor directly. Then ask whether your account and data were affected, change passwords, revoke connected integrations, check for unusual activity, and call your cyber insurer.
How do I know if a breach notification email is fake?
You often can't tell from the email alone. Don't click its links or call its numbers. Visit the vendor's website or customer portal yourself, or call a contact you already have.
Am I responsible if my vendor's breach exposed my customers' data?
You may be. Every U.S. state has a breach notification law, and rules like HIPAA, the FTC Safeguards Rule and DFARS can set their own deadlines. Talk to a lawyer before notifying anyone.
Do I need to change passwords after a vendor breach?
Yes, for the affected service and anywhere employees reused the same password. Also revoke and reconnect any API keys, tokens or app integrations tied to that vendor.
Should we stop using a vendor after a breach?
Not automatically. Judge how openly they communicated, how fast they contained it, and what they changed. A vendor that's honest and fixes the root cause may be safer than one that has never been tested.




Comments