third party risk: The Breach That Was Never on Their
Information Technology Solutions for Dentists and the Dental Industry. Serving the GTA and Southern Ontario.
Dental I/T, Dental Information Technology, Network Security, Toronto, GTA, Dental, Network, I/T, Information Technology, Computer, Data, Abeldent, Dentrix, LiveDDM, Patterson Dental, Henry Schein, K-Dental, Sinclair Dental, Schick CDR, Dexis, Carestream, Carestream Dental, Digital Radiography, X-ray, Dental X-ray, Dental Software Support, Software
19366
bp-nouveau,wp-singular,post-template-default,single,single-post,postid-19366,single-format-standard,wp-theme-bridge,wp-child-theme-bridge-child,theme-bridge,woocommerce-no-js,ajax_fade,page_not_loaded,,columns-4,qode-child-theme-ver-1.0.0,qode-theme-ver-10.0,wpb-js-composer js-comp-ver-4.12,vc_responsive

The Breach That Was Never on Their Network: What a 7.7-Million-Record Cloud Vendor Hack Means for Your Dental Practice

A dental practice's patient data flowing outward to many external cloud vendors, one of which has been breached, illustrating third-party risk beyond the office network

The Breach That Was Never on Their Network: What a 7.7-Million-Record Cloud Vendor Hack Means for Your Dental Practice

In late October, the Japanese manufacturer Iris Ohyama disclosed a breach with a detail every dental practice should sit up and notice. Roughly 7.7 million customer records — names, addresses, phone numbers, email addresses, dates of birth and encrypted account passwords — may have been exposed. But the attackers did not break into Iris Ohyama’s own servers. The data was sitting with a third-party cloud service the company used, and that is where the compromise happened. The company pulled its online store offline, but by then the lesson was already written: your most careful in-house security does nothing for the data you have handed to someone else.

A dental practice is not a 7.7-million-customer manufacturer, but the structure of its risk is identical. The patient data that matters most to you no longer lives only on the server in the back office. It is scattered across cloud platforms, backup services and processors you do not own and cannot see inside. When one of them is breached, it is still your patients, your reputation and your legal obligation on the line. Here is how to understand that exposure and bring it under control.

A dental practice's patient data flowing outward to many external cloud vendors, one of which has been breached, illustrating third-party risk beyond the office network
Your firewall protects the office. It cannot protect the patient data you have handed to vendors — and that is where the newest breaches are happening.

The breach your firewall cannot stop

Most practice security spending is aimed inward: the firewall, the antivirus, the segmented network, the locked server room. That work matters, and it genuinely stops a whole category of attacks. But none of it protects data that has already left the building. When your cloud practice-management vendor, your imaging host or your backup provider is compromised, your firewall never sees the attack, because the attack is not aimed at you. It is aimed at them, and your patients’ records are simply part of the haul.

This is the uncomfortable shift in modern security: the perimeter you are responsible for defending is no longer the perimeter where your data actually sits. We saw a smaller version of this recently when malicious code slipped in through a trusted third-party script on practice websites — the weakness was never in the practice’s own code. A cloud-vendor breach is the same principle at a larger scale: someone else’s systems, your exposure.

Your practice has more vendors than you think

Ask most dental offices who holds their patient data and the answer is “we do, on our server.” The real answer is a much longer list. Depending on how the practice runs, protected health information is routinely entrusted to a cloud practice-management system, a cloud imaging or radiograph store, an off-site backup service, an insurance-claims clearinghouse, a billing or revenue-cycle company, an online-booking or recall-reminder platform, a payment processor, and the email and marketing tools that carry patient names every day.

Each of those is a company with its own staff, its own security maturity and its own list of sub-vendors underneath it. Every one of them is part of your attack surface, whether or not you have ever thought of it that way. The Iris Ohyama incident is a reminder that the weakest of them — not the strongest, and not your own office — is what sets your real level of risk. You cannot manage a risk you have never written down, which is why the first move is simply to list every outside party that touches patient data.

A map of the many external vendors a dental practice shares patient data with: cloud practice management, imaging, backup, claims, billing, booking, payments and email
Most practices share patient data with far more outside companies than they realise. Every one of them is part of your attack surface.

Why a vendor’s breach is still your breach

There is a tempting assumption that handing data to a vendor hands off the responsibility too. Legally, it does the opposite. Under HIPAA, any vendor that creates, receives, maintains or transmits protected health information on your behalf is a Business Associate, and you are required to have a Business Associate Agreement (BAA) in place that binds them to protect that data and to notify you if they lose it. If a business associate breaches your patients’ records, it is still a reportable breach for your practice. For Ontario practices, PHIPA frames it through agents and service providers, but the principle is the same: you remain accountable for personal health information you place in someone else’s hands, and “our vendor lost it” is not a defence.

This is not theoretical for healthcare. Some of the largest exposures of patient data in recent memory have come not from clinics themselves but from the suppliers sitting behind them — a single compromised processor can spill records from thousands of practices at once. When you evaluate where your biggest risk lives, the honest answer is often not your own network at all; it is the vendor with the most data and the least scrutiny.

A signed business associate agreement linking a dental practice to its vendor, representing shared legal responsibility for protected health information
Handing data to a vendor does not hand off the responsibility. A Business Associate Agreement is the paperwork that proves you managed that relationship.

How to vet a vendor before you trust them with patient data

Due diligence sounds like a corporate exercise, but for a dental practice it comes down to asking a handful of plain questions before a vendor is holding your records — not after they turn up in a headline. Before you sign with any service that will touch patient data, ask:

  • Will you sign a Business Associate Agreement (or, in Ontario, an equivalent written commitment to safeguard personal health information)? A flat refusal is a deal-breaker.
  • Is our data encrypted both in transit and at rest, and where is it physically stored?
  • Do you enforce multi-factor authentication for your own staff and for our access to your system?
  • Have you had a breach, and can you describe how you handled it? How quickly will you notify us if one happens?
  • Do you rely on your own sub-vendors for cloud hosting or storage, and how do you hold them accountable?
  • Can you show an independent security attestation — a SOC 2 report, an ISO 27001 certification, or similar?

You do not need to audit a vendor like a security firm would. You simply need to make clear that patient data comes with conditions, and to walk away from anyone who treats those conditions as an inconvenience.

A checklist filtering vendors by security criteria before patient data is entrusted to them, representing vendor due diligence
Due diligence is simply asking the right questions before you trust a vendor — not after they appear in a breach headline.

What to do about the vendors you already have

Most practices are not choosing vendors from scratch; they already have a dozen relationships, many inherited and never reviewed. Work the list you built earlier and tighten each one. Confirm a signed, current BAA exists for every vendor that touches PHI — this is the single most common gap, and the first thing an auditor will ask for. Practise data minimization: give each vendor only the data it genuinely needs, for only as long as it needs it, so a breach there exposes less. Make sure every login to a vendor portal uses MFA, since a stolen staff password is a common way attackers reach cloud data.

Then prepare for the day a vendor does fail, because resilience is the part you control. Know in advance who you would notify and how you would keep the practice running if a cloud system went dark. That is also where your own independent, tested backups of the data you cannot afford to lose earn their keep — a vendor outage or breach should never be the moment you discover you had no copy of your own. Vendor risk belongs inside your broader HIPAA security risk analysis, not as an afterthought but as one of its core categories, reviewed on the same annual cycle.

A repeating cycle of inventory, assess, contract and monitor for managing dental practice vendor risk over time
Vendor risk is not a one-time form. It is an ongoing loop: know who holds your data, vet them, bind them by contract, and watch for change.

A short vendor-risk checklist

If you do nothing else this quarter, run your practice against these five questions:

  • Do we have a written list of every outside company that stores, sees or transmits our patient data?
  • Is there a signed, in-date Business Associate Agreement (or PHIPA equivalent) for each one?
  • Does each vendor only hold the minimum data it needs, protected by encryption and MFA?
  • Do we know how — and how fast — each vendor would tell us about a breach?
  • Could we keep seeing patients if one of these vendors went offline or was compromised tomorrow?

If any of those answers is “no” or “not sure,” that is not a failure — it is a to-do list, and a far cheaper one to work through on a quiet week than in the middle of a vendor’s breach.

At Compudent Systems, managing third-party risk — inventorying where a practice’s data really lives, checking that the right agreements are in place, and building the resilience to survive a vendor failure — is part of treating a dental office as the connected system it has become. If you have never mapped the vendors holding your patient data, or cannot remember the last time those relationships were reviewed, contact Compudent Systems for a vendor and third-party risk review, and we will help you see the whole picture, not just the part inside your own walls.


Sources & further reading:

Related Reading



Contact us today - How can we help you?