It arrives as an ordinary email: a vendor data breach notice from your payroll provider, accounting platform, or customer database. The vendor has found a security incident and opened an investigation. It promises updates and gives you a support address.
What it often does not say is what any of this means for your business.
Early notices usually go out before the vendor knows the full picture. Its team may still be combing through logs. Meanwhile, you may need to reset accounts, check payments, warn staff, or call your insurer. You do not have to wait for the final report to start asking questions.
First, confirm the vendor data breach notice is real
Scammers love public breach news. They send fake password reset emails or offers of support, knowing that the real vendor's customers will likely believe them.
So do not click links or call numbers in a surprise notice. Instead, type the vendor's web address yourself, sign in through the portal you normally use, or call a contact you already have. The NCSC gives the same advice for any message you are unsure about.
Once you have checked it, save the original email and any attachments. Your IT provider, insurer, or attorney may ask for them.
Was our business actually affected?
A breach at a vendor does not always touch every customer. It may involve one product, one database, or one group of accounts.
Ask directly whether the breach reached your account, company data, or users. If the vendor is not sure yet, ask it to put you in one of four groups: confirmed affected, possibly affected, confirmed not affected, or still under review.
That wording matters. Still under review does not mean you are safe. It only means the work is not done yet. So ask when you will get a firmer answer, and whether you should take any steps in the meantime.
When did it start, and what could the attacker do?
The announcement date is only part of the story. Ask when the activity began, when the vendor spotted it, and when it shut the activity down. A rough range is better than nothing.
Those dates tell your IT provider how far back to review your own logins, file transfers, account changes, invoices, and payment details.
Next, ask what the attacker could do. Could they only read data, or could they also copy, alter, or erase it? Did they add accounts, lock up files, or send messages to customers through the vendor's platform? Someone reading a contact list is a very different risk from someone holding login details.
Exactly what information was involved?
A vague line about customer information gives you nothing to act on. Ask which of your data the breach touched. Depending on the software, that might include contact details, payroll data, payment records, ID documents, contracts, files, support tickets, usernames, password hashes, API keys, or security tokens.
Also ask whether every customer had the same data exposed. Two companies can use the same software in very different ways. One stores names and emails, while another uploads contracts and payment details. As a result, the same breach can carry very different risk.
If the vendor says the data was encrypted, ask whether the attacker also got the keys to unlock it. Encryption only helps if the attacker did not get what they needed to read the data.
Was data copied, or just sitting on an affected system?
This is where the vendor's logs matter. If it says there is no evidence of misuse, ask what records back that up and whether they cover the whole period.
No evidence means the review has not found any. It does not always mean the vendor can prove nothing happened. For example, logs may not go back far enough, or may not capture every action. That does not mean data was stolen. Still, you should know how much the vendor can actually confirm.
Which passwords, keys, and connections need attention?
Resetting passwords may help. However, modern software often connects to other systems without anyone typing a password. Think of single sign-on, API keys, access tokens, certificates, and links to your email, accounting, payment, or backup tools.
Ask which of these the breach reached, and which ones you need to reset, revoke, or replace. Then let your IT provider make the changes. Swapping the wrong key or cutting a connection blindly can break systems your team relies on.
Also, if anyone reused the vendor password on another account, change it everywhere. Criminals routinely test stolen passwords against email, banking, and cloud services.
What has the vendor done, and what is left?
Contained usually means the vendor stopped the activity it knows about. The review and repairs may still be underway, so ask:
- Did it disable hacked accounts, end sessions, patch the flaw, rebuild servers, or replace exposed keys?
- Has an outside security firm reviewed the incident?
- Does the vendor consider the service safe to use right now?
- Which fixes are temporary, and when will the permanent ones be done?
NIST's incident response guidance makes the point that a response involves several parties, each with its own job. The vendor fixes its systems. Your business may still need to secure accounts, review activity, notify people, and meet contract or legal duties.
What does our business need to do?
Request written steps tailored to your account. Expect things like installing an update, resetting accounts, review logs, remove a connection, check recent payments, or warn staff about related phishing.
If you need an update, confirm which versions have the flaw, which one you should run, and whether there is a deadline.
Then ask whether the stolen data could fuel convincing scams. Names, invoice details, and support history make fake messages look real. If the vendor has seen related phishing emails, fake sites, or bogus support calls, ask for examples to share with your team.
The breach itself may be over. The scams built from its data are often just getting started.
Was another company involved?
Software vendors lean on other providers for hosting, payments, email, backups, and support. You may see them called subprocessors. When the breach began at one of these partners, ask who it was, what it did, what data it held, and whether the vendor still uses it.
You may never have dealt with that company directly. Even so, your vendor chose it and should be able to explain the impact.
How will we get updates?
Long reviews through a general support inbox get frustrating fast. Ask for a named contact or incident team, where the vendor will post official updates, and how often to expect them. Even when there is nothing new, the vendor should tell you when the next update is coming.
When the review wraps up, ask for a final report covering what happened, what data it touched, how it occurred, and what the vendor changed. Afterward, check whether your contract spells out breach reporting timelines and contacts. The NCSC's supplier assurance questions make a useful checklist for that review.
Keep a record, and bring in the right people
Create one folder for the incident. Save the first notice, every update, and each question you asked along with the reply. Add a log of what your business did, when, and who approved it. That record keeps everyone working from the same facts, and it shows how you handled things if questions come up later.
Depending on what happened, you may need your IT provider, an attorney or privacy advisor, your cyber insurer, and your leadership team. If you carry cyber insurance, read your policy and tell your broker or carrier within the required window. Certain policies call for prompt notice or for approved response firms.
If personal information was involved, get legal advice early. Notification duties vary by location, by the type of data, and by your contracts. A vendor breach does not automatically mean you must notify customers, but you need a qualified answer before you decide.
This is exactly the kind of moment a virtual CISO helps with. And if you want to know which vendors hold your most sensitive data before the next notice arrives, start with a cybersecurity assessment.
Frequently asked questions
The vendor says it found no sign of misuse. Is that enough?
Ask what logs support that, whether they cover the full period, and whether the review is finished. That may be good news. Still, get enough detail to judge it for yourself.
Should everyone change their password right away?
Follow the vendor's steps and ask your IT provider which accounts need attention. If anyone used the vendor password anywhere else, change it there too. Your IT provider should also check sessions, API keys, and tokens.
Does a vendor data breach mean we have to notify our customers?
Not always. It depends on whether the breach reached you, what data it touched, where the people live, what your contracts say, and which laws cover you. Talk to a legal or privacy advisor first.
Should we stop using the vendor?
A breach alone is not a reason to leave. Look at what happened, how much data left, how well the vendor handled it, and whether the root cause is fixed. If it keeps dodging fair questions, that tells you something too.
Free Coffee Break
Got a breach notice and not sure what it means?
Book a free Coffee Break. We will help you sort out what to ask, what to check, and what can wait.
Book your free Coffee Break →It arrives as an ordinary email: a vendor data breach notice from your payroll provider, accounting platform, or customer database. The vendor has found a security incident and opened an investigation. It promises updates and gives you a support address.
What it often does not say is what any of this means for your business.
Early notices usually go out before the vendor knows the full picture. Its team may still be combing through logs. Meanwhile, you may need to reset accounts, check payments, warn staff, or call your insurer. You do not have to wait for the final report to start asking questions.
First, confirm the vendor data breach notice is real
Scammers love public breach news. They send fake password reset emails or offers of support, knowing that the real vendor’s customers will likely believe them.
So do not click links or call numbers in a surprise notice. Instead, type the vendor’s web address yourself, sign in through the portal you normally use, or call a contact you already have. The NCSC gives the same advice for any message you are unsure about.
Once you have checked it, save the original email and any attachments. Your IT provider, insurer, or attorney may ask for them.
Was our business actually affected?
A breach at a vendor does not always touch every customer. It may involve one product, one database, or one group of accounts.
Ask directly whether the breach reached your account, company data, or users. If the vendor is not sure yet, ask it to put you in one of four groups: confirmed affected, possibly affected, confirmed not affected, or still under review.
That wording matters. Still under review does not mean you are safe. It only means the work is not done yet. So ask when you will get a firmer answer, and whether you should take any steps in the meantime.
When did it start, and what could the attacker do?
The announcement date is only part of the story. Ask when the activity began, when the vendor spotted it, and when it shut the activity down. A rough range is better than nothing.
Those dates tell your IT provider how far back to review your own logins, file transfers, account changes, invoices, and payment details.
Next, ask what the attacker could do. Could they only read data, or could they also copy, alter, or erase it? Did they add accounts, lock up files, or send messages to customers through the vendor’s platform? Someone reading a contact list is a very different risk from someone holding login details.
Exactly what information was involved?
A vague line about customer information gives you nothing to act on. Ask which of your data the breach touched. Depending on the software, that might include contact details, payroll data, payment records, ID documents, contracts, files, support tickets, usernames, password hashes, API keys, or security tokens.
Also ask whether every customer had the same data exposed. Two companies can use the same software in very different ways. One stores names and emails, while another uploads contracts and payment details. As a result, the same breach can carry very different risk.
If the vendor says the data was encrypted, ask whether the attacker also got the keys to unlock it. Encryption only helps if the attacker did not get what they needed to read the data.
Was data copied, or just sitting on an affected system?
This is where the vendor’s logs matter. If it says there is no evidence of misuse, ask what records back that up and whether they cover the whole period.
No evidence means the review has not found any. It does not always mean the vendor can prove nothing happened. For example, logs may not go back far enough, or may not capture every action. That does not mean data was stolen. Still, you should know how much the vendor can actually confirm.
Which passwords, keys, and connections need attention?
Resetting passwords may help. However, modern software often connects to other systems without anyone typing a password. Think of single sign-on, API keys, access tokens, certificates, and links to your email, accounting, payment, or backup tools.
Ask which of these the breach reached, and which ones you need to reset, revoke, or replace. Then let your IT provider make the changes. Swapping the wrong key or cutting a connection blindly can break systems your team relies on.
Also, if anyone reused the vendor password on another account, change it everywhere. Criminals routinely test stolen passwords against email, banking, and cloud services.
What has the vendor done, and what is left?
Contained usually means the vendor stopped the activity it knows about. The review and repairs may still be underway, so ask:
- Did it disable hacked accounts, end sessions, patch the flaw, rebuild servers, or replace exposed keys?
- Has an outside security firm reviewed the incident?
- Does the vendor consider the service safe to use right now?
- Which fixes are temporary, and when will the permanent ones be done?
NIST’s incident response guidance makes the point that a response involves several parties, each with its own job. The vendor fixes its systems. Your business may still need to secure accounts, review activity, notify people, and meet contract or legal duties.
What does our business need to do?
Request written steps tailored to your account. Expect things like installing an update, resetting accounts, review logs, remove a connection, check recent payments, or warn staff about related phishing.
If you need an update, confirm which versions have the flaw, which one you should run, and whether there is a deadline.
Then ask whether the stolen data could fuel convincing scams. Names, invoice details, and support history make fake messages look real. If the vendor has seen related phishing emails, fake sites, or bogus support calls, ask for examples to share with your team.
The breach itself may be over. The scams built from its data are often just getting started.
Was another company involved?
Software vendors lean on other providers for hosting, payments, email, backups, and support. You may see them called subprocessors. When the breach began at one of these partners, ask who it was, what it did, what data it held, and whether the vendor still uses it.
You may never have dealt with that company directly. Even so, your vendor chose it and should be able to explain the impact.
How will we get updates?
Long reviews through a general support inbox get frustrating fast. Ask for a named contact or incident team, where the vendor will post official updates, and how often to expect them. Even when there is nothing new, the vendor should tell you when the next update is coming.
When the review wraps up, ask for a final report covering what happened, what data it touched, how it occurred, and what the vendor changed. Afterward, check whether your contract spells out breach reporting timelines and contacts. The NCSC’s supplier assurance questions make a useful checklist for that review.
Keep a record, and bring in the right people
Create one folder for the incident. Save the first notice, every update, and each question you asked along with the reply. Add a log of what your business did, when, and who approved it. That record keeps everyone working from the same facts, and it shows how you handled things if questions come up later.
Depending on what happened, you may need your IT provider, an attorney or privacy advisor, your cyber insurer, and your leadership team. If you carry cyber insurance, read your policy and tell your broker or carrier within the required window. Certain policies call for prompt notice or for approved response firms.
If personal information was involved, get legal advice early. Notification duties vary by location, by the type of data, and by your contracts. A vendor breach does not automatically mean you must notify customers, but you need a qualified answer before you decide.
This is exactly the kind of moment a virtual CISO helps with. And if you want to know which vendors hold your most sensitive data before the next notice arrives, start with a cybersecurity assessment.
Frequently asked questions
The vendor says it found no sign of misuse. Is that enough?
Ask what logs support that, whether they cover the full period, and whether the review is finished. That may be good news. Still, get enough detail to judge it for yourself.
Should everyone change their password right away?
Follow the vendor’s steps and ask your IT provider which accounts need attention. If anyone used the vendor password anywhere else, change it there too. Your IT provider should also check sessions, API keys, and tokens.
Does a vendor data breach mean we have to notify our customers?
Not always. It depends on whether the breach reached you, what data it touched, where the people live, what your contracts say, and which laws cover you. Talk to a legal or privacy advisor first.
Should we stop using the vendor?
A breach alone is not a reason to leave. Look at what happened, how much data left, how well the vendor handled it, and whether the root cause is fixed. If it keeps dodging fair questions, that tells you something too.
Free Coffee Break
Got a breach notice and not sure what it means?
Book a free Coffee Break. We will help you sort out what to ask, what to check, and what can wait.
Book your free Coffee Break →

