Why would anyone bother attacking a six-chair dental office, and if they did, would a regulator really come after a practice this size? Dental owners ask us some version of that question constantly. The events of 2026 have answered it, and the answer should change how a practice approaches dental practice HIPAA compliance.
The short answer: dental practices are now a distinct HIPAA risk category because their patient data is concentrated in a small set of dental-specific vendors, attacks on dental offices are being reported at a steady pace, and recent enforcement against dental entities has turned on basics like risk analysis and written policies rather than exotic security failures. Size no longer offers cover.
Three things set dentistry apart from general healthcare. The first is volume. Becker's counted 23 dental cybersecurity incidents it had reported on in 2026 as of late September, ranging from single-location offices to multi-site groups. Hawaii Family Dental reported 45,853 people affected after an unauthorized individual used a compromised account, and San Antonio-based Soniva Dental Care reported up to 30,000 patients affected across several offices.
The second is the vendor ecosystem. A dental office's PHI rarely sits only on its own server. It flows through practice management software, imaging, patient communication and marketing platforms, outsourced billing, and insurance verification services, many of which serve thousands of practices at once. The third is the enforcement pattern, which in 2026 has repeatedly touched dental entities for failures that any small practice could have.
The common belief is that HIPAA risk for a small practice is mostly about whether its own network gets hacked. That framing leads owners to buy a better firewall and consider the matter handled. The more accurate view is that a dental practice's largest HIPAA exposure now lives in places it does not directly control, and in documentation it has not written.
Put plainly: for most dental offices, the HIPAA question an investigator will ask after an incident is not "how did they get in?" It is "show me the risk analysis that identified this system, the agreement that governed it, and the policy that told your staff what to do." Practices that cannot answer those questions are exposed even when the breach happened somewhere else.
The clearest example is a vendor. On March 5, 2026, HHS's Office for Civil Rights announced a settlement with MMG Fusion, LLC, a Maryland software company whose resolution agreement describes it as focused on helping oral healthcare professionals market, manage, and grow their practices. OCR said an intrusion in December 2020 led to PHI for approximately 15 million individuals, including names, contact details, dates of birth, and appointment dates and times, being exposed and posted on the dark web.
OCR found that MMG had failed to conduct an accurate and thorough risk analysis and failed to notify the covered entities affected. The penalty was $10,000, reflecting the company's financial condition, plus a three-year corrective action plan. The lesson for practices is not the dollar amount. It is that a dental-focused vendor's failure to notify left its practice customers unable to meet their own breach notification obligations, and OCR Director Paula Stannard said so directly in the announcement.
Practices themselves are not exempt. On October 8, 2026, OCR announced that Pennsylvania dental provider Shen Smiles agreed to pay $140,000 after a patient could not obtain her records. The practice said a workforce member had taken them. OCR found the practice lacked right-of-access policies and procedures and had not reasonably safeguarded PHI. That is a documentation failure, not a technology failure, and it cost a small practice six figures.
State attorneys general are active too. Indiana's Attorney General reached a $350,000 settlement with Westend Dental, a six-location Indianapolis practice, after alleging it failed to report a 2020 ransomware attack on time and never launched a forensic investigation. Because there was no investigation, the practice could not establish how many patients were affected.
In September 2026, eAssist Dental Solutions, an outsourced billing and insurance-verification service that Pact-One's technical alert notes is majority-owned by Henry Schein, told customers it was investigating a potential information security incident after a ransomware group listed it on a leak site. As of that alert, neither company had confirmed what data was involved. Practices using the service still had to decide which carrier portals, clearinghouse logins, and practice management credentials to rotate. We covered why a vendor's breach becomes your problem in Your Billing Vendor Had The Breach. Why Is It Your HIPAA Problem?
Yes. The HIPAA Security Rule requires an accurate and thorough risk analysis regardless of practice size, and OCR has made it the center of its enforcement. According to HIPAA Journal's report on OCR's 2026 priorities, Director Stannard confirmed the risk analysis initiative will continue and expand to target the Security Rule's risk management requirement, meaning OCR will look at whether you acted on what the analysis found.
Waiting for the proposed Security Rule overhaul is not a strategy. Butzel's July 2026 alert notes that HHS now projects the final rule for July 2027. The existing rule, which already requires risk analysis and risk management, is what OCR is enforcing today. Our post on why healthcare organizations should not wait on the delayed Security Rule changes covers that timing question in more depth.
The risk management half is where most small practices fall down. A risk analysis that lists twenty findings and then sits in a binder for two years tells an investigator the practice knew about its problems and chose not to act. OCR's corrective action plans, including MMG Fusion's, require both an accurate analysis and a plan that addresses what it found. If your team still thinks of the analysis as a once-and-done exercise, our post on common risk assessment myths is worth sharing with the office manager.
A dental risk analysis also needs to reflect how dentistry actually works. A generic template written for a medical clinic will miss the imaging bridge on the operatory workstation, the patient texting platform, and the outsourced billing team logging in remotely. The table below shows what a dental-specific analysis should capture.
| Dental system | Typical PHI held | What the risk analysis should record |
|---|---|---|
| Practice management software | Demographics, treatment plans, insurance, payments | Hosting model, who has admin access, MFA status, backup and restore test date |
| Digital imaging and sensors | Radiographs and intraoral images tied to patient records | Which workstations store images locally, patching status, vendor remote access |
| Patient communication and marketing tools | Names, contact details, appointment dates | Signed BAA, data retained by the vendor, breach notice terms |
| Outsourced billing and insurance verification | Insurance IDs, claims, sometimes Social Security numbers | Credentials the vendor uses, carrier and clearinghouse portals it can reach, BAA |
| Email and front-desk workstations | Referrals, records requests, attachments | MFA, retention settings, phishing training records |
When something goes wrong, the investigator, the cyber insurer, and potentially the state attorney general will all ask for proof that your program existed before the incident. Assembling it afterward puts the practice in the weakest possible position. This is the evidence file we recommend every practice keep current.
Backups belong in that conversation too. Ransomware recovery for a dental office often depends on whether imaging and practice management data can actually be restored, and cloud email is not a backup. Our article on why Microsoft 365 is not a complete backup strategy for regulated SMBs explains the gap. If your practice is also evaluating AI scheduling assistants or note-taking tools, the same BAA and risk analysis logic applies, as we outline in AI in Healthcare: Use Cases, HIPAA Risks, and Compliance Guardrails.
We start by mapping where a practice's PHI really lives: the practice management platform, imaging, communication tools, billing, and every vendor login that touches them. That map becomes the basis of a dental-specific risk analysis and a risk management plan with owners and dates, which is exactly the documentation OCR's current initiative examines. We then track BAAs, enforce MFA on practice and vendor accounts, and review access on a schedule so idle logins do not linger.
When a vendor incident like eAssist's surfaces, we help the practice work through credential rotation, integration review, and the notification-timing decision quickly, with records that show what was done. If you are comparing providers for this work, our MSP evaluation checklist for medical practices lists the questions worth asking any firm, including us.
Dental practices became a distinct HIPAA risk category because their data lives in a dense web of dental vendors and because enforcement keeps returning to the basics. The fastest way to reduce that risk is a current, dental-specific risk analysis backed by signed BAAs and written policies.
For ongoing help keeping that documentation current, see how Securafy's compliance management service supports regulated practices with continuous risk analysis, policy, and vendor tracking.
If you would rather talk through your specific environment first, book a strategy call with Securafy and we will walk your current HIPAA documentation, vendor exposure, and the fastest path to closing the gaps.