Powered by MOMENTUMMEDIA
For breaking news and daily updates, subscribe to our newsletter

Op-Ed: Your supplier's breach is your breach – customers and regulators won't see the difference

When a data breach makes the front page in Australia, the headline typically carries a single name, and it is rarely the supplier's.

user icon Jill Macmurchy, Head of Solutions Engineering, APJ, Vanta • Wed, 18 Nov 2026 •
Op-Ed: Your supplier's breach is your breach – customers and regulators won't see the difference

This year has demonstrated that repeatedly. In May, Queensland's Department of Education confirmed student and staff data was exposed through Instructure, its QLearn platform provider. In August, Quest Apartment Hotels disclosed a breach originating at a third-party technology provider, affecting almost two million customers. In October, Canva confirmed some enterprise customer records had been exposed through Canny, a feedback tool connected to its Salesforce environment.

Of the roughly 70 Australian breaches tracked by IronSights this year, my own analysis shows at least one in four originated with a third-party vendor.

Vendor breaches are also rarely one-to-one. When attackers targeted Ferve, the ticketing platform used by the Melbourne International Film Festival, around 26,700 MIFF customers were affected. Ferve serves other organisations too, so one compromised supplier can become a breach for many brands at once.

 
 

‘Our systems were not compromised’

Canva emphasised that its own platform and systems were not compromised. For a security team, that distinction matters, but for customers, it carries little weight. Their data was exposed, and the brand they trusted was Canva.

Qantas faced the same reality last year, when customer data was accessed through a third-party platform used by its contact centre. Regulators take the same view, since the organisation chose the supplier and granted the access.

A stronger position than ‘it wasn't us’ is ‘we knew that tool could reach customer data, and we revoked its access immediately’. Not every vendor breach can be prevented, but every organisation can know who has access to what.

How far down the supply chain to look

October's attack on Shopify merchants shows how deep the problem can run. Shoppers, including some in Australia, were redirected to fake checkout pages after one app developer, Selleasy, had an internal tool compromised and a script planted in merchants' settings. The merchant trusted the app, the developer trusted its tool, and the attacker went straight for the tool.

The answer is to follow the data. If a supplier, or one of its sub-processors, has a pathway to customer records, it is part of your attack surface, no matter whose name is on the invoice.

Moving beyond the annual questionnaire

Most vendor reviews still run on an annual cycle. A questionnaire is emailed, responses are chased and filed, and the process lies dormant for another twelve months. Meanwhile, the vendor may have changed sub-processors or suffered an incident.

These reviews are also rarely segmented by risk. An organisation might pay a facilities contractor ten times more than a small SaaS tool integrated with its CRM, yet the SaaS tool is the far greater risk. Scrutiny should follow data access, not spend.

The replacement is risk-based tiering supported by continuous monitoring. For the highest tier, that might mean six-monthly penetration tests, annual ISO 27001 checks and ongoing monitoring of trust centres and sub-processor lists. When a supplier's access changes, its tier should change too.

I have experienced this from the other side. In previous roles at technology companies, every major vulnerability triggered a wave of customer enquiries. For example, the recent PHP vulnerability would have resulted in multiple customers asking whether we used PHP and had patched it.

An organisation that already knows which vendors use PHP can go directly to the 30 that matter, the same morning rather than the following quarter.

Maturity claims are losing their value. ASD Essentials replaces maturity levels with evidence-based ratings by domain. Contracts and insurers requiring Maturity Level Two still apply for now, but a vendor citing a level without evidence will look increasingly unconvincing.

Expect to request proof rather than attestations.

Lessons from financial services

Since 1 July, CPS 230 has applied in full to banks, insurers and superannuation funds, including pre-existing arrangements with material service providers. Financial institutions have long led on supplier risk because APRA requires it.

Other sectors should follow suit, treating supplier monitoring as an ongoing discipline. Critical infrastructure operators are already moving this way under the SOCI Act, and the AESCSF framework and government suppliers face similar expectations.

ASIC's $1.35 million penalty against Fortnum Private Wealth centred on oversight of an adviser network of more than 200 advisers serving around 55,000 retail clients. Replace ‘authorised representatives’ with franchisees, resellers, or managed service providers, and the risk becomes familiar to many businesses.

Where partners hold customer data, regulators expect evidence that their security is being monitored.

Where to start

Few organisations know which applications have standing access to their customer data, yet a first map takes a working week. Every step can be done by hand with data exports, spreadsheets and email, but expect it to take weeks rather than days. In Vanta, the week starts with discovery: connect your identity providers and Vendor Discovery lists every app your people have authorised. AI Inventory, now in early access, adds the agents and MCP servers they’ve connected. Set requirements by tier so your highest-risk vendors are automatically asked for evidence and assessed. From then on, discovery and continuous monitoring keep the map current, so you don’t have to redraw it by hand next quarter.

When a vendor breach breaks at 9 am, an organisation should know by lunchtime whether it uses that vendor, directly or through another supplier. It should understand what the vendor can access, whether that access can be safely suspended, who owns the relationship, and what it will tell customers, the board or a regulator. If those answers take days, that is the first gap to close.

Too many enterprises still treat third-party risk as a procurement function: sign the contract, file the questionnaire and move on. In the eyes of customers, the media and regulators, a supplier's breach is the organisation's breach.

Vendors should be monitored with the same rigour as the organisation itself.

Cyber DailyWant to see more stories from trusted news sources?
Make Cyber Daily a preferred news source on Google.
Tags: