Your payroll provider, accounting software or cloud platform has reported a security breach. You know there has been an incident, but you might not know whether your business has been affected or what information could be at risk.
For a business that relies on these services every day, that uncertainty can be difficult to manage. You might be waiting for answers from the provider while also wondering whether your own systems need attention.
The important thing is not to assume the worst, but that doesn’t mean you should assume everything is fine either.
Here are the questions to ask and the steps you should take when a software provider reports a data breach.
Make sure the notification is genuine
Before clicking a link or following instructions in the tagged email, confirm that it came from the official software provider.
Cyber criminals can use real security incidents to make fraudulent emails more convincing. You might receive a fake password reset request, a message offering technical support or an email asking you to sign in to secure your account.
Visit the provider’s official website directly or contact your usual representative using details you already know and trust. The UK National Cyber Security Centre’s guidance on phishing explains how to recognise suspicious messages and check whether communications are genuine.
Once you have confirmed the notice is legitimate, save the original email and any attachments. You may need these when speaking with your IT provider, insurer or legal adviser.
Find out whether your business was affected
A breach at any software company does not automatically mean every customer has been affected. The incident may involve a particular service, database or group of accounts/clients.
Contact the provider and ask for a clear update on your business specifically.
If the investigation is ongoing, establish whether your organisation is confirmed to be affected, potentially affected or still under investigation. Ask when further information will be available and whether you should take any immediate precautions.
Do not treat an incomplete investigation as confirmation that your data is secure.
What information was involved?
Ask the official provider to identify any information that may have been exposed. Depending on the service, this could include:
- Employee or customer contact details
- Payroll information and financial records
- Invoices, contracts and business documents
- Usernames, passwords or login records
- API keys, access tokens or other credentials
The type of information involved will help determine the level of risk. Exposure of a customer contact list presents a different concern from compromised login credentials that could provide access to other business systems.
If the provider says the information was encrypted, ask whether the encryption keys or systems needed to decrypt it were also affected.
When did the breach happen?
The date the provider announced the breach may not be the date the incident began.
Ask when the unauthorised activity started, when it was detected and when the affected systems were secured. Your IT provider may need these dates to determine how far back you need to review your own systems.
That review could include sign-in activity, changes to user accounts, unusual file transfers, invoices or payment instructions.
It is also worth asking what the attacker was able to do. Was information viewed, copied, changed or deleted? Were accounts created or access permissions altered?
If the provider says there is no evidence that your information was misused, ask what records support that conclusion and whether the investigation is complete.
Check passwords and connected systems
Changing a password may be necessary, but it might not be enough to protect your business.
Business applications often connect to other services, including Microsoft 365, accounting software, payment platforms, file storage and backups. These connections can rely on access tokens, API keys or other credentials that do not require someone to enter a password each time.
Ask the provider which accounts and integrations could have been affected. Your IT provider can then help establish whether passwords need to be changed, active sessions revoked or access keys replaced.
Avoid making changes to business-critical integrations without checking what depends on them. Replacing a credential or disconnecting a service without proper planning can interrupt systems your team relies on.
If a password used for the affected service was also used elsewhere, change it on every account where it was reused.
For businesses using Microsoft 365, it is also worth checking whether any connected accounts, permissions or sign-in activity require further investigation. ITM Tech helps businesses secure their Microsoft environment through its Microsoft 365 security services.
Ask what the provider has done to secure its systems
A provider may say the breach has been contained. That is useful, but it does not necessarily mean the investigation and recovery work are finished.
Ask what action has been taken to secure the affected systems. Have compromised accounts been disabled? Have access credentials been revoked or vulnerable systems patched? Has the provider confirmed that the service is safe to use?
Find out what work remains and whether you need to install an update, review account activity or take other precautions.
You should also ask whether the incident could lead to follow-up scams. Information such as names, invoice details or support history can help criminals create convincing emails and phone calls.
If the provider has identified related phishing attempts, ask whether it can share examples so you can warn your staff.
Could another supplier be involved?
Software companies often rely on other providers for hosting, payment processing, email delivery, backups and customer support.
If the breach occurred at one of these suppliers, ask which company was involved, what service it provided and whether it had access to your information or systems.
You may never have dealt directly with that company, but its role could still affect the security of a service your business uses.
The National Cyber Security Centre’s supplier assurance guidance provides useful questions for assessing the security arrangements of third-party providers.
It is a reminder that your business’s security depends on more than the systems you own. It also depends on the services and suppliers you trust.
Keep a record of the incident
Create a central record of the breach and keep the original notice, subsequent updates, questions sent to the provider and answers received.
Record the actions your business takes, when they happen and who is responsible. Include any advice received from your IT provider, insurer or legal adviser.
Ask the provider for a final incident report when its investigation is complete. This should explain what happened, what information was involved and what measures have been taken to address the problem.
Keeping a clear record helps everyone involved work from the same information. It may also be important if your business needs to demonstrate how it assessed and responded to the incident.
Do you need to notify customers or the authorities?
Not every breach involving a software provider means your business must notify its customers. The requirements depend on the information involved, the risk to individuals, your role in handling the data and the laws that apply.
If personal data may have been affected, seek appropriate advice promptly.
Under the GDPR, a software provider acting as a data processor must notify the relevant data controller of a personal data breach without undue delay. Where a breach presents a risk to individuals, the controller may need to notify the relevant supervisory authority within 72 hours of becoming aware of it. A breach likely to result in a high risk to individuals may also require communication with those affected.
The Irish Data Protection Commission’s guidance on personal data breaches explains the requirements in more detail.
If your business has cyber insurance, check your policy and contact your insurer or broker as required. Some policies specify notification deadlines or require particular incident response providers to be used.
Do not assume the software provider will handle every responsibility on your behalf.
Should you stop using the software?
Not necessarily.
Before deciding whether to leave a provider, consider what happened, how much information was affected, how the company responded and whether the security issue has been resolved.
Communication matters too. If the provider cannot answer reasonable questions, repeatedly delays important updates or fails to explain how it has secured the service, you may need to reconsider whether you are comfortable continuing to use it.
For now, focus on understanding the risk and protecting your business. You can make a more informed decision about the supplier once you have a clearer picture.
How ITM Tech can help
A breach at one of your software providers can create work for your own team, even if your systems were not directly attacked.
You may need to review account activity, secure connected services, check for suspicious transactions or establish whether other parts of your network could be affected.
Having an IT partner who understands your systems can make that process easier. ITM Tech provides Irish businesses with managed IT support and cybersecurity services, helping them protect their systems, reduce risk and respond to potential security issues.
Our managed cybersecurity services include security monitoring, endpoint protection, security hardening and practical guidance to help businesses reduce their exposure to cyber threats.
If a software provider has reported a breach and you are unsure what it means for your business, get in touch with ITM Tech. We can help you work through the technical questions and identify the areas that may need attention.
The priority is to establish what happened, understand what may be at risk and take the right steps to protect your business.
Sources and Further Reading
- NIST SP 800-61 Revision 3: Incident Response Recommendations and Considerations
- UK National Cyber Security Centre: Supplier Assurance Questions
- UK Information Commissioner’s Office: Personal Data Breaches
- European Data Protection Board: Personal Data Breach Notification Guidance
- Office of the Australian Information Commissioner: Responding to Data Breaches