Youโve just found yourself on the receiving end of a data breach notice from one of your software vendors.
Maybe itโs the company that handles your payroll. It could be your accounting platform, CRM, cloud storage provider, or another service your team uses every day. The email says the vendor discovered a security incident and has started an investigation. It may say that certain systems were accessed, or that the incident has been contained. Then it gives you a support address and promises further updates.
But youโre left with the question the notice rarely answers: what does this actually mean for your business?
The first notice often arrives before the vendor knows the full extent of the breach. Its security team may still be reviewing logs, identifying affected systems, and confirming what information was accessed. That takes time, but you may need to reset accounts, check transactions, warn staff, or contact your insurer well before the investigation is finished.
You donโt have to wait for the final report before asking questions. Confirm that the notice is genuine, save a copy, and start gathering the information your business needs. A good Managed IT or IT Support provider can help you work through every step below.
First, Make Sure the Notice Is Genuine
Before you respond, confirm that the email really came from the vendor.

IMAGE SOURCE: https://www.pexels.com/photo/woman-using-laptop-while-talking-on-the-phone-7971729/
Criminals sometimes take advantage of public breach announcements by sending fake password-reset emails or pretending to offer support. Someone who already uses the affected software is more likely to believe the message, because the breach itself is real.
Avoid clicking links or calling numbers in an unexpected notice until youโve checked it. Visit the vendorโs website by entering the address yourself, sign in through the customer portal you normally use, or contact a representative whose details you already have.
The UK National Cyber Security Centre recommends contacting an organisation through details found on its official website when youโre unsure whether a message is genuine.
Once youโve confirmed the notice, save the original message and any attachments. You may need them when speaking with your IT provider, insurer, legal adviser, or privacy contact.
Ask Whether Your Business Was Affected
A breach at a software company doesnโt always affect every customer. The incident may have involved one product, database, office, or group of accounts.
Ask the vendor directly:

IMAGE SOURCE: https://www.pexels.com/photo/it-technician-working-in-data-center-server-room-37605911/
Was our account, company information, or user data affected?
If the vendor canโt give you a definite answer yet, ask whether your business is confirmed to be affected, possibly affected, confirmed not to be affected, or still under investigation.
That wording matters. โStill under investigationโ does not mean your business is safe. It means the vendor hasnโt finished checking.
Ask when you can expect a clearer answer, and whether the vendor recommends any precautions while it investigates.
Find Out What Happened and When
The date the vendor announced the breach is only one part of the timeline.
Ask when the unauthorised activity began, when the vendor detected it, and when the affected systems were contained. If the vendor only knows an estimated date range, ask it to share that.
Those dates help your IT provider decide how far back to review your own records. You may need to check login activity, file transfers, account changes, invoices, payment instructions, or messages sent during the affected period.
You also need to understand what the unauthorised person was able to do. Were they able to view information, copy it, change it, or delete it? Did they create new accounts, encrypt files, or use the vendorโs systems to contact customers?
The answer affects what you do next. Someone viewing a customer list creates a different risk from someone obtaining login credentials, or gaining access to a system connected to your network.
Ask Exactly What Information Was Involved
A statement such as โcustomer information may have been affectedโ is too broad to guide your response.
Ask the vendor which information connected to your business was involved. Depending on the software, this could include employee or customer contact details, payroll information, payment records, identity documents, contracts, files, messages, support tickets, usernames, password hashes, login records, API keys, or security tokens.
Then ask whether all customers had the same information exposed.
Two businesses may use the same software in completely different ways. One company might use a platform only to store names and email addresses. Another might have uploaded contracts, identity documents, invoices, and payment information. So the fact that both businesses use the same vendor doesnโt mean they face the same risk.
If the vendor says the information was encrypted, ask whether the encryption keys, or any system capable of decrypting the information, were also affected. Encryption can reduce the risk, but only if the attacker didnโt obtain what was needed to read the data.
Was the Information Viewed, Copied, or Simply Present on an Affected System?
This is where the vendorโs logs become important.
If the company says there is โno evidenceโ that your information was copied or misused, ask what records support that statement. You should also ask whether those records cover the entire period being investigated.
โNo evidence of misuseโ means the investigation hasnโt found evidence. It doesnโt always mean the vendor can prove that nothing happened.
For example, the relevant logs may not have been retained for the full period, or they may not record every action an attacker could take. That doesnโt prove that data was stolen, but you should understand how much the vendor can actually confirm before deciding that no further action is needed.
Check Passwords and Connected Systems
A password reset may be part of the response, but modern software often connects to other services without asking anyone to enter a password each time.
Your vendor may use single sign-on, API keys, access tokens, security certificates, or integrations with your email, accounting, payment, file-storage, or backup systems.
Ask whether any of these connections were affected. Then ask which credentials need to be reset, revoked, or replaced.
Your IT provider should manage these changes where possible. Replacing the wrong key, or disconnecting an integration without checking what depends on it, can interrupt business systems or stop information from syncing.
If an employee used the same password for the breached service and another account, that password should be changed everywhere it was reused. A criminal who obtains one password can test it against email, banking, cloud storage, and other common services.
Ask What the Vendor Has Done So Far
A vendor may say that the breach has been contained. Usually, that means it has stopped the activity it knows about. The investigation and repair work may still be continuing.
Ask what the company has done to secure the affected systems. Did it disable compromised accounts, revoke active sessions, patch a vulnerable system, rebuild affected servers, or replace exposed access keys? Has an independent security company reviewed the incident? And does the vendor currently consider the service safe to use?
You should also ask what work remains. Some early measures are temporary, so find out when the vendor expects to complete the permanent fixes.
NISTโs incident-response guidance explains that responding to an incident can involve several parties, including service providers, system owners, legal teams, and business leaders. Each party needs to understand what itโs responsible for doing.
The vendor will handle its own systems. Your business may still need to protect its accounts, review activity, contact affected people, or meet contractual and legal requirements.
Find Out What Your Business Needs to Do
Ask the vendor to give you customer-specific instructions in writing.
You may need to install an update, reset certain accounts, review activity logs, remove an integration, check recent transactions, or warn employees about related phishing attempts.
If an update is required, ask which versions of the software are affected and which version your business should now be using. Also confirm whether thereโs a deadline for completing the work.
Find out whether the attacker could use information from the breach to create convincing scams. Names, invoice details, support history, or the names of vendor employees could make a fraudulent message look genuine.
If the vendor has found related phishing emails, fake websites, or fraudulent support calls, ask it to share examples you can pass to your staff.
Ask Whether Another Company Was Involved
Software companies often rely on other providers to host systems, process payments, send emails, store backups, or run customer support. These other providers are sometimes called subprocessors.
If the breach happened at one of these companies, ask who it was, what service it provided, and what information it held. You should also find out whether it had direct access to your data or systems, and whether the software vendor still uses it.
This information may be important even if youโve never dealt directly with the other company. Your software vendor chose that provider and should be able to explain how the incident affected the service you use.
Agree on How Youโll Receive Updates
When an investigation lasts several days or weeks, getting information through a general support inbox can become frustrating. Each response may come from a different person, and you may have to explain the situation again and again.
Ask for a named contact or an incident response team that can answer follow-up questions. Confirm where official updates will be published and how often the vendor expects to provide them.
If the company doesnโt have new information yet, it should still be able to tell you when the next update will arrive.
Once the investigation is complete, ask for a final report. It should explain what happened, what information was involved, how the breach occurred, and what the vendor has changed since then.
The NCSCโs supplier security guidance recommends setting clear incident-reporting timescales, contacts, and responsibilities in supplier contracts. After the immediate response is over, check whether your existing agreement covers these points.
Keep a Record of Your Response
Create a folder for the incident and keep the original notice, later updates, your questions, and the vendorโs answers.
You should also record what your business did, when each action was taken, who approved important decisions, and what advice you received from your IT provider, insurer, or legal adviser.
Having this information in one place makes it easier for everyone involved to work from the same facts. It also gives you a record of how your business assessed and handled the incident if questions come up later.
Privacy authorities in several countries require organisations to document certain breaches and their response. For example, the UK Information Commissionerโs Office says organisations should record the facts, effects, and remedial action taken. Australiaโs privacy regulator recommends a response based on containing, assessing, notifying, and reviewing the breach.
The exact requirements depend on where your business operates, what information was involved, and your role in handling that information.
Decide Who Else Needs to Be Involved
The vendorโs notice may create responsibilities for your business as well.
Depending on what happened, you may need help from your IT provider, legal or privacy adviser, cyber insurer, senior management, or communications team. You may also need to contact affected customers, employees, regulators, or other organisations.
If the incident may be covered by cyber insurance, review your policy and notify your broker or insurer as required. Some policies require prompt notification, or the use of approved legal, forensic, or incident-response providers.
If personal information was involved, get privacy or legal advice early. Notification requirements vary by location, and may depend on the type of information, the likely harm, your contract with the vendor, and whether your business controls the information or processes it for someone else.
Under the GDPR, for example, a software provider acting as a data processor must notify the relevant controller without undue delay. The controller may still be responsible for assessing the breach and making any required notifications.
The European Data Protection Boardโs guidance also explains that a vendor can provide information in stages as the investigation develops.
Frequently Asked Questions
What if the Vendor Says There Is No Evidence That Our Information Was Misused?
Ask what evidence and logs support that statement, whether those records cover the full period, and whether the investigation is complete. The answer may be reassuring, but you need enough detail to understand how the vendor reached it.
Should Everyone Change Their Password Immediately?
Follow the vendorโs instructions and ask your IT provider which accounts are affected. If a password used with the vendor was also used elsewhere, change it on every affected account and stop reusing it. Your IT provider should also check whether active sessions, API keys, or access tokens need to be revoked.
Does a Vendor Breach Mean We Must 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 the laws that apply. Get appropriate 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 information was exposed, how the vendor responded, and whether the original problem has been fixed.
Pay attention to the quality of the vendorโs communication as well. If it repeatedly avoids reasonable questions or canโt explain how it has secured the service, you may need to reconsider whether youโre comfortable trusting it with your data.
Sources and Further Reading
NIST SP 800-61 Revision 3: Incident Response Recommendations and Considerations โ NISTโs current incident-response guidance.
UK National Cyber Security Centre: Supplier Assurance Questions โ questions to ask suppliers about security and incident handling.
UK Information Commissionerโs Office: Personal Data Breaches โ ICO guidance on recording and reporting breaches.
European Data Protection Board: Personal Data Breach Notification Guidance โ EDPB guidance on breach notification.
Office of the Australian Information Commissioner: Responding to Data Breaches โ OAIC guidance on containing, assessing, notifying, and reviewing a breach.
Whether youโre running a small team in Mackay or a growing business across Brisbane, a vendor breach notice is never a welcome email. But the businesses that come through it well are usually the ones that ask the right questions early and keep good records.
If a software vendor has reported a breach and youโre unsure what it means for your business, speak with your IT Support provider. And if youโd like help working through it, check out our cybersecurity services, or get in touch with us and weโll help you work through it.
—


