How to recognise and respond to a data breach notification from your service provider
Summary
This guide helps you troubleshoot and resolve: How to recognise and respond to a data breach notification from your service provider. Follow the steps below to fix the issue.
Common Causes
When a service provider experiences a data breach, they are legally required under Australia's Notifiable Data Breaches scheme to notify affected customers. Receiving one of these notifications can be unsettling, but knowing how to verify the message, assess your risk, and respond quickly will help protect your business and personal information. This guide walks you through what to look for, what to do next, and how to strengthen your accounts against follow-on attacks.
Recognising a Legitimate Data Breach Notification
Cybercriminals often exploit real breach news by sending fake "notifications" designed to steal your credentials. Before acting on any message, confirm it is genuine.
What a real notification looks like
- It comes from an official domain you already have an account with (for example,
@companyname.com.au, not a lookalike such as@companyname-support.com). - It references a specific incident date, the type of data involved, and the regulator or statement page.
- It directs you to log in to your account through your normal browser, not by clicking an email link.
- It does not ask for your password, MFA code, or payment details.
Common signs of a phishing impersonation
- Urgent language such as "act within 24 hours or your account will be closed".
- Generic greetings like "Dear Customer" when the provider normally uses your name.
- Links that, when hovered, point to unfamiliar domains or shortened URLs.
- Attachments or QR codes that prompt you to "verify" your identity.
Assessing Your Exposure
Once you have confirmed the notification is genuine, work out what information may have been affected and where that information is reused.
Identify the data types involved
- Read the provider's breach notice carefully and note which categories of data were exposed (for example, names, email addresses, passwords, payment details, dates of birth).
- Check whether the breach included hashed or plaintext credentials. Plaintext exposure is far more serious.
- Determine whether any government identifiers (TFN, Medicare, driver's licence) were involved, as these require additional steps.
Map your reuse across other accounts
- List every account that uses the same email address or the same password as the breached service.
- Prioritise accounts that hold financial data, customer records, or admin access to business systems.
- Note any shared or service accounts that may have used the same credentials.
Securing Your Accounts
Take these steps in order to contain the impact and prevent attackers from using the leaked information against you.
Step 1: Change passwords immediately
- Log in to the breached service directly through your browser.
- Navigate to the password change section. Common menu paths include:
- Microsoft 365: Sign in to account.microsoft.com → Security → Password security.
- Google Workspace: Go to myaccount.google.com → Security → Signing in to Google → Password.
- Xero: Click your name in the top right → Account → Change password.
- MYOB: Select your profile → Settings → Change password.
- Create a new, unique password of at least 14 characters.
- Use a password manager to generate and store it.
- Repeat the process for every other account that shared the same password.
Step 2: Enable multi-factor authentication
- In the same Security menu, turn on Multi-Factor Authentication or Two-Step Verification.
- Prefer an authenticator app (such as Microsoft Authenticator, Google Authenticator, or Authy) over SMS where possible.
- Save the recovery codes in your password manager or print and store them securely offline.
Step 3: Revoke active sessions and API tokens
- Look for Sign out of all devices or Revoke all sessions in the security settings.
- Regenerate any API keys, OAuth tokens, or app-specific passwords that were issued to integrations.
- Confirm that no new mailbox rules, forwarding rules, or OAuth app consents have been added since the breach.
What to Do If You Cannot Log In
If you cannot access the breached service because your password has already been changed or your account is locked, take the following steps immediately.
- Use the provider's "Forgot password" or "Can't access your account" recovery flow from the official login page.
- If recovery fails, contact the service provider's support team through their official website or verified phone number to report an account takeover.
- Request that the provider lock or suspend the account until you can verify your identity and regain control.
- Once access is restored, change the password immediately, revoke all active sessions, and enable multi-factor authentication.
- Check for any changes to your recovery email address or phone number that an attacker may have added.
Business Email Compromise Checks
If the breached account is a business email account (such as Microsoft 365 Exchange or Google Workspace Gmail), attackers often configure hidden rules to monitor or steal email. Perform these checks as soon as you regain access.
- Check mailbox rules: In Outlook or Outlook on the web, go to Settings → Mail → Rules. In Gmail, go to Settings → See all settings → Filters and Blocked Addresses. Delete any rules you did not create, especially rules that forward email to external addresses or move messages to hidden folders.
- Check email forwarding: In Microsoft 365, go to the Microsoft 365 admin center → Users → Active users → select the user → Mail tab → Manage email forwarding. In Google Workspace, check the user's Gmail settings for forwarding addresses.
- Review mailbox delegation and send-as permissions: In Microsoft 365, check the admin center for delegates with full access or send-as rights. In Google Workspace, check for account delegation under Settings → Accounts and Import.
- Review sent items: Look for sent emails you did not write, particularly to clients or suppliers requesting payment changes.
Protecting Your Business Data
If the breached account is connected to your business, the response needs to extend beyond the single login.
Audit connected systems
- Review any cloud storage, CRM, accounting, or ticketing systems that were linked to the compromised account.
- Check for unauthorised file changes, new admin users, or unfamiliar integrations.
- Export and review audit logs for the 30 days before the breach was disclosed.
Notify the right people
- Inform your internal team or IT contact so they can monitor for suspicious activity.
- If customer data was exposed, seek legal advice on your obligations under the Privacy Act and the Notifiable Data Breaches scheme.
- Document the incident, including dates, actions taken, and communications sent, for compliance and insurance purposes.
Reporting Your Own Data Breach (OAIC Obligations)
Under the Privacy Act 1988 and the Notifiable Data Breaches (NDB) scheme, Australian organisations may be required to report a data breach to the Office of the Australian Information Commissioner (OAIC) and notify affected individuals.
You must report an eligible data breach if:
- There is unauthorised access to, or unauthorised disclosure of, personal information, or a loss of personal information that your organisation holds.
- The breach is likely to result in serious harm to one or more individuals whose information is involved.
- Your organisation has not been able to prevent the likely risk of serious harm with remedial action.
- Subscribe to a credential-monitoring service (such as Have I Been Pwned or your password manager's built-in dark-web watcher) for alerts involving your email domains.
- Set up transaction alerts on bank accounts and credit cards linked to the breached service.
- Consider a credit ban through Equifax, Experian, or Illion if government identifiers were exposed.
- Review your accounts monthly for the next six months and watch for password reset emails you did not request.
- Contact each credit reporting body individually to request a ban (also known as a credit freeze or ban period):
- Equifax: Visit equifax.com.au and apply for a ban on your credit report.
- Experian: Visit experian.com.au and request a credit ban.
- Illion: Visit illion.com.au and apply for a ban on your credit file.
- Provide identification documents as requested by each bureau.
- The ban prevents credit providers from accessing your credit report without your consent, making it harder for fraudsters to open new accounts in your name.
- Keep records of your ban requests and reference numbers.
- Use a unique password for every account, stored in a reputable password manager.
- Turn on MFA on every service that supports it, especially email, banking, and cloud admin consoles.
- Limit third-party app connections and review them quarterly.
- Keep devices and operating systems up to date so leaked credentials cannot be paired with unpatched vulnerabilities.
- Health clinics and medical practices: If Medicare numbers, health records, or patient identifiers were exposed, the breach is likely to result in serious harm and may be notifiable to the OAIC. You may also need to notify Services Australia and affected patients.
- Accounting and bookkeeping firms: If Tax File Numbers (TFNs), financial records, or client tax data were exposed, treat the incident as high risk. Seek legal advice on Privacy Act obligations and notify affected clients promptly.
- Retail and hospitality: Focus on payment card data. If card details were exposed, advise customers to contact their bank and monitor statements for unauthorised transactions.
If you suspect an eligible data breach has occurred, you must assess the situation promptly. If the assessment confirms serious harm is likely, you must notify the OAIC and affected individuals as soon as practicable. For more information and to submit a notification, visit the OAIC website at oaic.gov.au.
Monitoring for Ongoing Risk
Breached data often circulates for months after the initial incident. Ongoing vigilance is essential.
How to initiate a credit ban in Australia
Preventing Future Impact
Reducing the blast radius of the next breach is largely about good hygiene today.
Industry-Specific Considerations
Some Australian small businesses handle data that requires extra care after a breach.
Still Having Issues?
💻 Open a Ticket