Skip to main content
Client Portal
ITstuffed
Cybersecurity

What to Ask a Software Vendor After They Report a Data Breach

A breach notice from one of your software vendors lands in your inbox. Maybe it's your payroll platform, your practice management system, your accounting software, or the cloud storage your team uses every day. The email says a security incident occurred, that the vendor's team is investigating, and that certain systems may have been accessed. It ends with a support address and a promise of further updates.

What it doesn't answer is the question you actually need answered: what does this mean for your business?

The first notice often arrives before the vendor has finished its own investigation. Its security team may still be reviewing logs and confirming exactly what was accessed. That takes time, but you may need to reset accounts, check for unusual activity, warn staff, or notify your insurer before any final report is published. You don't have to wait.

Make sure the notice is genuine before you do anything else

Criminals often take advantage of public breach announcements by sending fake password-reset emails or posing as vendor support staff. Someone who already uses the affected software is more likely to trust the message, because the breach itself is real and the email sounds plausible.

Don't click links or call numbers in an unexpected notice until you've verified it. Go to the vendor's website by typing the address yourself, sign in through the customer portal you normally use, or contact a representative using details you already have on file. Once you've confirmed the notice is genuine, save the original email and any attachments. You may need them when speaking with your IT provider, insurer, or legal adviser.

Find out whether your business was actually affected

A breach at a software company doesn't necessarily affect every customer. It may have involved one product, one database, or a specific group of accounts. Ask the vendor directly whether your account, company data, or user information was involved.

If the vendor can't give a definite answer yet, ask which category applies: confirmed affected, possibly affected, confirmed not affected, or still under investigation. The last of those doesn't mean you're safe - it means they haven't finished checking. Ask when you can expect a clearer answer and whether the vendor recommends any precautions in the meantime.

Get the timeline clear

The date the vendor announced the breach is only part of the picture. Ask when the unauthorised activity began, when it was detected, and when the affected systems were contained. Even an estimated date range is useful, because it tells your IT provider how far back to review your own logs - login activity, file transfers, account changes, payment instructions, or messages sent during that period.

You also need to understand what the attacker was able to do. Were they able to view information, copy it, modify it, or delete it? Did they create new accounts, encrypt files, or use the vendor's systems to send messages to customers? Someone viewing a customer list creates a different risk from someone obtaining login credentials or accessing a system connected to your network.

Ask exactly what information was involved

A statement like "customer information may have been affected" isn't enough to guide your response. Ask the vendor which specific types of information connected to your business were involved. Depending on the software, that could include employee or patient contact details, payroll records, payment information, identity documents, contracts, support tickets, usernames, password hashes, API keys, or security tokens.

Then ask whether all customers had the same exposure. Two businesses using the same platform may use it in completely different ways. One might store only names and email addresses. Another might have uploaded contracts, identity documents, and payment records. The vendor is the same; the risk isn't.

If the vendor says the information was encrypted, ask whether the encryption keys or any system capable of decrypting the data were also affected. Encryption reduces risk, but only if the attacker didn't obtain what was needed to read it.

When the vendor says there is "no evidence" that your information was copied or misused, ask what records support that statement and whether those records cover the entire period under investigation. That response may be genuinely reassuring, but "no evidence of misuse" means the investigation hasn't found evidence - it doesn't necessarily mean the vendor can prove nothing happened. Logs may not have been retained for the full period, or they may not capture every action an attacker could take. You need enough detail to understand how the vendor reached its conclusion before deciding no further action is needed.

Check passwords and connected systems

Modern software connects to other services without asking someone to re-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, and 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 correctly. This is exactly the kind of technical response that a managed cybersecurity support team can coordinate on your behalf, so the right things get reset in the right order.

If anyone used the same password for the breached service and another account, that password needs to change everywhere it was reused. An attacker who obtains one password will typically test it against email, banking, cloud storage, and other common services.

Ask what the vendor has done and what still needs doing

When a vendor says the breach has been contained, that usually means it has stopped the activity it knows about. The investigation and repair work may still be ongoing. Ask what specific steps the vendor has taken - whether it disabled compromised accounts, revoked active sessions, patched a vulnerable system, or replaced exposed access keys. Ask whether an independent security company has reviewed the incident, and whether the vendor currently considers the service safe to use.

Ask what work remains and when the vendor expects permanent fixes to be in place. Some early measures are temporary, and you should know that.

Get written instructions for your business

Ask the vendor to give you customer-specific guidance in writing. You may need to install an update, reset particular accounts, review activity logs, remove an integration, or warn staff about related phishing attempts. If an update is required, ask which software version your business should be running and whether there's a deadline for completing the work.

Also ask whether information from the breach could be used to make scams more convincing. Names, invoice details, support history, or the names of vendor staff could make a fraudulent message look genuine. If the vendor has found related phishing emails or fake support calls in the wild, ask it to share examples so you can pass them to your team. Invoice and payment fraud is one of the more common ways criminals exploit the information they obtain from vendor breaches.

Find out whether another company was involved

Software vendors often rely on other providers to host systems, process payments, send emails, store backups, or run customer support. If the breach originated with one of these third parties, ask who it was, what service it provided, what information it held, and whether it had direct access to your data. You should also find out whether the vendor still uses that provider.

You may never have dealt directly with the other company, but your vendor chose it and should be able to explain its role in the incident.

Agree on how updates will reach you

When an investigation runs for days or weeks, communicating through a general support inbox becomes frustrating. Each reply may come from a different person, and you may have to re-explain the situation each time. Ask for a named contact or dedicated incident response team. Confirm where official updates will be published and how often.

Once the investigation is complete, ask for a written final report covering what happened, what information was involved, how the breach occurred, and what changes the vendor has made since.

Keep a record of your own response

Create a folder for the incident and keep the original notice, subsequent updates, your questions, and the vendor's answers. Record what your business did, when each action was taken, who made important decisions, and what advice you received from your IT provider, insurer, or legal adviser.

Under the NZ Privacy Act 2020, organisations may need to notify the Office of the Privacy Commissioner and affected individuals when a privacy breach is likely to cause serious harm. Whether that applies to your situation depends on what information was involved, the likely impact, and your role in handling that information - whether your business controls the data or was processing it on behalf of someone else. Get privacy or legal advice early if personal information was involved, rather than trying to work out the requirements under pressure. If you want to understand what your obligations can look like in practice, the steps New Zealand businesses take after a breach are worth reviewing before you need them.

If the incident may be covered by cyber insurance, check your policy and notify your broker promptly. Some policies require notification within a specific timeframe, or require that you use approved legal or forensic providers. Acting without checking first can affect your cover.

Deciding whether to continue using the vendor is a separate question from managing the immediate response. A breach alone doesn't automatically mean you should leave. How the vendor responds - the quality of its communication, whether it answers reasonable questions directly, and whether it can demonstrate the original problem has been fixed - tells you a great deal about how seriously it takes the security of the information you've entrusted to it.

If a vendor breach notice has landed and you're not sure what it means for your business, ITstuffed can help you work through it. To talk through your situation, book a 15-minute IT Fit Check at itstuffed.co.nz/booking.

What to Ask a Software Vendor After They Report a Data Breach | ITstuffed