The short answer: First, confirm the breach notice is real. Then ask the vendor whether your business was affected, what information was exposed, when it happened, and whether any passwords or connected systems need attention. Keep a written record of every answer, and loop in your IT provider, insurer, or legal advisor as needed.

It's a regular Tuesday. You open your inbox and there it is: a data breach notice from one of your software vendors.

Maybe it's your payroll company. Maybe it's your accounting software, your CRM, or the cloud storage your whole team lives in every day.

The email says all the expected things. We recently discovered a security incident. We've launched an investigation. The issue has been contained. We take your security very seriously. Then it gives you a support address and promises more updates "soon."

And you're left staring at the screen thinking: Okay... but what does this mean for MY business?

Here's the thing. That first notice usually goes out before the vendor knows the whole story. Their security team may still be digging through records and figuring out what was touched. That takes time. But you might need to reset accounts, check transactions, warn your staff, or call your insurer before their investigation wraps up.

The good news: you don't have to sit and wait for their final report. You're allowed to ask questions now. Here at Justice IT Consulting, we think every business owner should have this list handy before they ever need it.

First things first: make sure the notice is real

Before you click anything, confirm the email actually came from the vendor.

Scammers love a public breach announcement. They know customers are already on edge, so they send fake "reset your password here" emails or pose as the vendor's support team. Because the breach is real, the fake message is a lot more believable.

So don't click links or call phone numbers in an unexpected notice until you've checked it out. Instead:

  • Type the vendor's web address into your browser yourself
  • Log in through the customer portal you normally use
  • Contact a rep whose details you already have on file

The UK National Cyber Security Centre recommends contacting an organization using the details on its official website whenever you're unsure if a message is legit.

Once it checks out, save the original email and any attachments. You'll likely need them when talking to your IT provider, insurer, or legal advisor.

The questions to ask your vendor

1. "Were we actually affected?"

A breach at a software company doesn't always hit every customer. It might involve one product, one database, one office, or one group of accounts.

If the vendor can't give you a clear yes or no yet, ask which bucket you're in:

  • Confirmed affected
  • Possibly affected
  • Confirmed not affected
  • Still under investigation

That wording matters. "Still under investigation" does not mean you're in the clear. It means they haven't finished checking. Ask when you can expect a clearer answer, and whether they recommend any precautions in the meantime.

2. "When did this start, and what could they do?"

The day the vendor announced the breach is just one point on the timeline. Ask when the unauthorized activity began, when the vendor spotted it, and when it was shut down. An estimated date range is fine if that's all they have.

Those dates tell your IT provider how far back to look in your own records, like logins, file transfers, invoices, payment instructions, or emails sent during that window.

Also ask what the intruder was able to do. Could they view information, copy it, change it, or delete it? Did they create new accounts, lock up files, or use the vendor's systems to contact customers? Someone peeking at a customer list is a very different situation from someone grabbing login credentials or getting into a system connected to your network.

3. "Exactly what information of ours was involved?"

"Customer information may have been affected" is far too vague to act on.

Ask specifically which information tied to your business was involved. Depending on the software, that could mean employee or customer contact details, payroll info, payment records, ID documents, contracts, files, messages, support tickets, usernames, or the behind-the-scenes digital keys that let systems talk to each other.

Then ask if every customer had the same information exposed. Two businesses can use the same software in completely different ways. One might only store names and emails. Another might have uploaded contracts, IDs, invoices, and payment details. Same vendor, very different risk.

If the vendor says the data was encrypted (scrambled so it can't be read), ask whether the keys to unscramble it were also exposed. Encryption is great, but only if the bad guys didn't get the key too.

4. "How do you know it wasn't copied?"

If the vendor says there's "no evidence" your data was copied or misused, ask what records back that up, and whether those records cover the entire time period in question.

Here's a helpful translation: "No evidence of misuse" means they haven't found any. It doesn't always mean they can prove nothing happened. For example, their records might not go back far enough, or they might not track every action an intruder could take.

That doesn't mean your data was stolen. It just means you should understand how confident they really are before deciding there's nothing more to do.

5. "Do any passwords or connections need to be reset?"

A password reset might be part of the plan. But modern software often connects to your other systems without anyone typing a password, using things like single sign-on, digital access keys, and integrations with your email, accounting, payment, file storage, or backup tools.

Ask whether any of those connections were affected, and which ones need to be reset, cancelled, or replaced.

Let your IT provider handle these changes when possible. Swapping the wrong key or disconnecting an integration without checking what depends on it can break things or stop information from syncing.

And if anyone on your team used the same password for that vendor and another account? Change it everywhere it was reused. Criminals who get one password will happily try it on email, banking, and cloud storage.

6. "What have you fixed, and what's still in progress?"

When a vendor says the breach is "contained," that usually means they've stopped the activity they know about. The investigation and repair work may still be ongoing.

Ask what they've done to secure things. Did they disable compromised accounts, kick out active sessions, patch a weakness, rebuild affected servers, or replace exposed access keys? Has an independent security firm reviewed the incident? Do they currently consider the service safe to use?

Also ask what work remains. Some early fixes are temporary bandages, so find out when the permanent repairs will be done.

NIST's incident response guidance points out that responding to an incident often involves several parties, each with their own job. The vendor handles its systems. Your business may still need to protect its own accounts, review activity, contact affected people, or meet contract and legal requirements.

7. "What do you need us to do?"

Ask for customer-specific instructions in writing.

You might need to install an update, reset certain accounts, review activity, remove an integration, check recent transactions, or warn employees about related scam emails. If an update is required, ask which versions are affected, which version you should be on, and whether there's a deadline.

Also ask whether the stolen information could be used to create convincing scams. Names, invoice details, support history, or the names of vendor employees can make a fake email look very real. If the vendor has already seen scam emails, fake websites, or bogus support calls, ask for examples you can share with your team.

8. "Was another company involved?"

Software companies rely on other companies too, for hosting, payment processing, sending emails, storing backups, or running support. These behind-the-scenes partners are sometimes called subprocessors.

If the breach actually happened at one of them, ask who it was, what they did for the vendor, what information they held, whether they had direct access to your data, and whether the vendor still uses them.

You may never have heard of this company, but your vendor chose them, and your vendor should be able to explain how it affects you.

9. "Who's our point person, and when's the next update?"

When an investigation drags on for days or weeks, bouncing between different people in a general support inbox gets old fast.

Ask for a named contact or incident response team. Confirm where official updates will be posted and how often. Even if they have nothing new to share, they should be able to tell you when the next update is coming.

When everything's wrapped up, ask for a final report covering what happened, what information was involved, how it happened, and what's changed since.

Then, once things settle down, pull out your contract. The NCSC's supplier security guidance recommends spelling out incident reporting timelines, contacts, and responsibilities in vendor agreements. If yours doesn't, now's a great time to fix that.

Keep a paper trail

Create a folder for the incident. Save the original notice, every update, your questions, and the vendor's answers.

Also note what your business did, when you did it, who approved key decisions, and what advice you got from your IT provider, insurer, or legal advisor.

Having everything in one place keeps everyone working from the same facts. It also shows how your business handled the situation if questions come up later. Depending on where you operate and what information was involved, privacy laws may require you to document the breach and your response.

Bring in the right people

A vendor's breach can create responsibilities for your business too. Depending on what happened, you may need help from:

  • Your IT provider
  • A legal or privacy advisor
  • Your cyber insurance broker or carrier
  • Your leadership team
  • Whoever handles communications with customers or employees

If you have cyber insurance, check your policy and notify your broker or carrier as required. Some policies require prompt notice, or require you to use their approved legal, forensic, or incident response firms. Calling the wrong people first can create headaches later.

If personal information was involved, get privacy or legal advice early. Notification requirements vary based on where you and the affected people are located, the type of information, your contract with the vendor, and whether your business controls the information or handles it for someone else.

A quick note for defense contractors

If your business works on Department of Defense contracts, a vendor breach deserves extra attention. If that vendor stores or processes covered defense information or Controlled Unclassified Information (CUI) for you, DFARS 252.204-7012 reporting requirements may come into play, including a 72-hour window to report qualifying cyber incidents to the DoD. The same clause also expects cloud providers handling that information to report incidents to you.

Translation: don't wait for the vendor's final report before getting your compliance team involved. This is exactly where Justice IT Consulting helps defense contractors sort out what applies and what doesn't.

Frequently Asked Questions

What if the vendor says there's no evidence our information was misused?

Ask what records support that statement, whether those records cover the full time period, and whether the investigation is finished. The answer may be reassuring, but you need enough detail to understand how the vendor reached that conclusion.

Should everyone change their password right away?

Follow the vendor's instructions and ask your IT provider which accounts are affected. If a password used with that vendor was reused anywhere else, change it on every account and stop reusing it. Your IT provider should also check whether any active sessions or connections need to be cut off.

Does a vendor breach mean we have to notify our customers?

Not always. It depends on whether your business was affected, what information was involved, where the affected people are located, your contracts, and which laws apply. Get privacy or legal advice before deciding.

Should we stop using the vendor?

A breach alone doesn't automatically mean you should leave. Look at what happened, how much was exposed, how the vendor responded, and whether the problem is fixed. If they keep dodging reasonable questions or can't explain how they've secured things, it may be time to reconsider.

Not sure what a vendor breach means for your business?

If a software vendor has reported a breach and you're not sure where that leaves you, talk to your IT provider. If you don't have one, Justice IT Consulting is here to help businesses across Dallas-Fort Worth and beyond work through it. Book a discovery call with our team and we'll help you figure out your next move.

Sources and Further Reading