Ransomware and dental practices: prevention and recovery playbook
Ransomware is both an IT emergency and a HIPAA breach question. CISA's guide stresses offline, tested backups, phishing-resistant multi-factor sign-in, patching and closed remote access. If it happens, isolate systems, call your responder and insurer, and expect a breach analysis that starts from a presumption (our reading of 45 CFR 164.402; confirm with a HIPAA attorney).
Why do ransomware attackers target dental practices?
No source we could open shows that dental practices are hit more often than other small businesses, so we do not claim it. What is documented is narrower: a dental practice reported a ransomware incident to HHS in 2026, and OCR investigates every breach of protected health information affecting 500 or more people.
OCR's breach portal says it "investigates all breaches of protected health information (PHI) and Part 2 records that affect 500 or more individuals," and that breaches affecting fewer than 500 people "may be investigated based on Departmental resources and enforcement priorities" (HHS OCR Breach Portal, undated page).
One 2026 dental example
Tampa Bay Dental Implants & Periodontics disclosed a breach affecting about 6,400 people. According to Claim Depot, a breach-tracking site (published 19 May 2026), the practice identified a ransomware incident on 19 January 2026 and reported it to HHS on 8 March 2026. The affected system was an internal legacy server that "contained a backup of the practice's electronic medical records." Data involved included names, birth dates, clinical history and treatment notes, and possibly Social Security numbers or financial information for some people.
Claim Depot does not name the group behind the attack, so we do not either. This is one reported example, not a pattern.
DDSBreach, the breach tracker The DDS Hub sells, shows 317 dental cyber incident records from the last five years, with 26,942,557 people affected "in dental organizations' regulator filings, as filed" (DDSBreach site, as of 21 November 2026; the figures change). Its records include "claim reported" entries that its site says are not verified, and its people total is not deduplicated. It is a vendor's tally of incidents of all kinds, not an official ransomware statistic.
Which prevention controls matter most against dental ransomware?
Five controls from CISA's guide are a practical starting point: backups an attacker cannot reach and that you have tested, phishing-resistant multi-factor sign-in, prompt patching, no remote-access services exposed to the internet, and staff phishing training. The table follows CISA's #StopRansomware Guide (September 2023 edition), which does not rank them, and lists what to ask your IT provider.
| Control | What CISA's guide says | What to ask your IT provider |
|---|---|---|
| Offline, tested backups | "Maintain offline, encrypted backups of critical data" and test their "availability and integrity." | Where is the offline copy? When did we last restore from it, and how long did it take? |
| Multi-factor sign-in | "Implement phishing-resistant MFA for all services, particularly for email, VPNs, and accounts that access critical systems." | Which accounts have it today? Is it on email, remote access and admin accounts? |
| Patching | "Regularly patch and update software and operating systems to the latest available versions," plus regular vulnerability scanning. | Who patches the server, workstations, firewall and imaging PCs, and how do we know it happened? |
| Remote-access hardening | "Do not expose services, such as remote desktop protocol, on the web." If RDP is needed: audit for it, close unused ports, enforce account lockouts, apply MFA and log login attempts. | Is any remote desktop port open to the internet? How do the doctor and staff connect from home? |
| Phishing training | "Implement a cybersecurity user awareness and training program" that teaches staff to identify and report suspicious activity; filter malicious email and enable attachment filters. | How often is training run? Is there an easy way for staff to report a suspicious email? |
CISA's guide also recommends endpoint detection and response (or application allowlisting) on all assets, and says to assess the cyber hygiene of third parties and managed service providers and give them least-privilege access. In our reading, a dental office's IT vendor falls under that advice.
What backup setup does CISA actually recommend?
CISA publishes two separate pieces of backup advice.
- The 3-2-1 guideline. In its "Back Up Business Data" page, CISA calls 3-2-1 "a trusted guideline": three copies of important files, on two different types of storage media (like a hard drive and the cloud), with one copy stored off-site, away from your business location.
- Offline and tested copies. The #StopRansomware Guide says to keep offline, encrypted backups and test them. CISA's "Back Up Business Data" page adds that you should test full and partial restores, confirm you can roll data back at least seven days, and confirm critical files can be reached without internet access.
- Immutable storage, with a caution. The guide says "Some cloud vendors offer immutable storage solutions that can protect stored data," but also says to use it "with caution," because it "does not meet compliance criteria for certain regulations" and "misconfiguration can impose significant cost." It does not tell practices to buy it.
The CISA pages we read do not mention "3-2-1-1-0," so it is not a CISA rule. In plain terms (our explanation, not CISA's), offline and immutable also differ: an offline copy is disconnected from your network, while an immutable copy is locked against changes. Ask any backup vendor which it provides, and how long the lock and retention last.
What should a practice do in the first 24 hours of a ransomware attack?
Isolate affected systems, preserve evidence, call your IT provider or incident responder and your cyber insurer, report to law enforcement, and restore only from known-good backups once the intruder is out. CISA's checklist covers these steps but sets no 24-hour clock, so "first 24 hours" means the first day. Counsel before any payment decision is our advice, not CISA's.
Before you need it, CISA says to keep an incident response plan with response and notification procedures, including "a hard copy of the plan and an offline version." In our view, a plan stored only on a locked server will not help.
- Isolate. CISA: "Determine which systems were impacted, and immediately isolate them." If several systems seem affected, it says to take the network offline at the switch level, and to use out-of-band channels such as phone calls so the attackers are not tipped off. Power devices down only if you cannot disconnect them, because powering down loses evidence held in memory.
- Preserve evidence. Our advice: do not wipe or reinstall machines until your responder confirms the evidence is captured. CISA says to take a system image and memory capture of a sample of affected devices and to collect logs and malware samples. Your incident responder can do this.
- Call your people. CISA's checklist says to engage stakeholders under your plan, naming IT, managed security providers and your "cyber insurance company." Read your policy's notice requirements before hiring anyone; that is our advice, not CISA's.
- Report and ask about decryptors. CISA says to report the incident to CISA, your local FBI field office, the FBI's IC3 or the U.S. Secret Service, and to "consult federal law enforcement, even if mitigation actions are possible, regarding possible decryptors available."
- Do not pay before talking to counsel. The CISA page we opened does not address whether to pay a ransom, so this step is our advice. Your attorney should also start the HIPAA analysis below.
- Write down when you discovered it. Under HIPAA the breach-notice clock runs from discovery, so record the date and time, who found it and what they saw.
- Rebuild, then restore. CISA's order is to identify how the attacker got in (including email), contain remote-access paths such as VPNs, rebuild systems by priority, reset passwords after the environment is clean, and then "reconnect systems and restore data from offline, encrypted backups based on a prioritization of critical services," taking care not to reinfect clean systems.
What are a dental practice's HIPAA obligations after ransomware?
Under 45 CFR 164.402, an impermissible acquisition, access, use or disclosure of protected health information is presumed to be a breach unless you demonstrate a low probability of compromise through a risk assessment. If it is a breach, you generally must notify patients within 60 days of discovery and tell HHS. Confirm with a HIPAA attorney.
This is general information, not legal advice. Whether a particular ransomware incident is a reportable breach depends on facts, so confirm with a HIPAA attorney. Applying the rule to ransomware is our reading of the regulation text.
The presumption and the four-factor risk assessment
The eCFR text of 45 CFR 164.402 defines a breach as the "acquisition, access, use, or disclosure of protected health information in a manner not permitted" under the Privacy Rule "which compromises the security or privacy" of that information. Unless one of three narrow exceptions applies, such an event "is presumed to be a breach unless the covered entity or business associate, as applicable, demonstrates that there is a low probability that the protected health information has been compromised." The risk assessment must consider at least these four factors:
- The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification.
- The unauthorized person who used the protected health information or to whom the disclosure was made.
- Whether the protected health information was actually acquired or viewed.
- The extent to which the risk to the protected health information has been mitigated.
The notification rules apply to "unsecured" protected health information, meaning information not rendered unusable, unreadable or indecipherable to unauthorized persons through a method the Secretary specifies in guidance. Ask your attorney whether your encryption changes the analysis. Keep a written record.
Notification timing
| Who is notified | Deadline | Rule |
|---|---|---|
| Affected individuals | "Without unreasonable delay and in no case later than 60 calendar days after discovery of a breach." The default is written notice by first-class mail, or email if the person agreed to electronic notice. | 45 CFR 164.404(b), (d)(1) |
| HHS, breach affecting 500 or more people | At the same time as the individual notice, in the manner HHS specifies on its website. | 45 CFR 164.408(b) |
| HHS, breach affecting fewer than 500 people | Keep a log; report within 60 days after the end of the calendar year in which the breach was discovered. | 45 CFR 164.408(c) |
| Covered entity, when a vendor (business associate) has the breach | The business associate must notify you without unreasonable delay and no later than 60 calendar days after discovery. | 45 CFR 164.410(b) |
A breach is treated as discovered on the first day it is known to the practice, or would have been known with reasonable diligence, and a practice is deemed to know when any workforce member or agent other than the person committing the breach knows (45 CFR 164.404(a)). The 60 days is an outer limit, and "without unreasonable delay" can mean sooner. Sections 164.408 and 164.410 also point to 164.412, which covers a law-enforcement delay; ask your attorney whether it could apply. State breach laws may add their own duties, and CISA's guide also says breach notifications should follow applicable state laws. Your attorney should check both.
Is HIPAA's Security Rule about to change?
HHS proposed changes to the HIPAA Security Rule on 6 January 2025 (90 FR 898). They are not final. The federal regulatory agenda entry we opened lists final action for July 2027 under "Long-Term Actions," a planning target on a long-term list, not a deadline or an effective date. A later agenda may supersede it.
The Federal Register notice says the proposal responds to rising breaches and cyberattacks and to compliance gaps OCR has found in investigations. Comments closed 7 March 2025. The summary we read lists no specific requirements, so we do not describe any. The agenda entry is RIN 0945-AA22. Until a final rule is published, our reading is that the rule now in force is what applies; confirm with a HIPAA attorney. Do not wait: the prevention table above is what CISA recommends today.
Where do DDS apps fit in a ransomware plan?
These DDS apps touch this problem: DDSArk for off-site recovery points, DDSVPN for remote access, DDSBreach for breach alerts and DDS ID for passwordless sign-in. None of them replaces a risk analysis, an incident plan or an IT professional. The DDS Hub sells them, and the descriptions below come from each app's own site as of November 2026.
| App | What its site says it does | Limits to know |
|---|---|---|
| DDSArk | Off-site, encrypted, immutable ("object-locked") recovery points for practice-management and imaging data. An agent finds data from 20+ dental systems; automatic recurring test-restores; a BAA at no extra cost. | Lock duration and retention period are not stated. It holds no SOC 2 report or other third-party attestation. Its 11-minute median recovery time for a full practice server is from its own restore tests. |
| DDSVPN | Remote access to on-premises dental software through WireGuard-based encrypted tunnels, so the software stays in the office; every login is logged. | Its FAQ lists a UniFi Dream Machine firewall at your office, and says it can help if you don't already have one. Its BAA wording differs across its pages, so get the BAA in writing. Log retention is not stated. |
| DDSBreach | A public record of dental cyber incidents with a status for each claim, a weekly email digest, and alerts for vendors, locations and software. | It informs you; it does not stop an attack. No BAA, encryption or retention details are stated. It needs no patient data. |
| DDS ID | Passkey sign-in with Face ID, fingerprint, Windows Hello or a security key, role-based access across DDS apps, and one-step removal of a team member. | It covers DDS apps. Microsoft 365, Google Workspace and remote-access sign-in are listed as planned, so it does not yet protect your email or practice-management logins. |
How to read the table
DDSArk. Its site describes off-site, locked recovery points. CISA's guide names offline copies, which is not the same thing, so ask DDSArk how its design fits your backup plan. Its FAQ says it signs a BAA with every customer that handles PHI and that "HIPAA does not certify software."
DDSVPN. CISA says not to expose remote desktop to the internet. DDSVPN's approach is encrypted tunnels into the office, with the software staying on your own server, and its site says it does not store protected health information on its servers. We found no ransomware-prevention claim on the pages we reviewed.
DDSBreach. Its methodology page lists HHS OCR data, state breach-notice lists and news as sources, and says the OCR portal lags by weeks to months. Its value is awareness.
DDS ID. Its sign-in covers DDS apps for now. For your email, remote-access and practice-management logins, CISA's multi-factor advice still depends on the tools you use today, so ask your IT provider. Some DDS ID features are marked planned, so check what is live first.
For more on this topic, see the cybersecurity guides.
Sources
- HHS OCR Breach Portal, HHS Office for Civil Rights(as of 2026-11-21)
- Tampa Bay Dental Implants & Period data breach, Claim Depot (breach tracker; secondary source)(as of 2026-11-21)
- DDSBreach, DDSBreach (ROOT32 LLC)(as of 2026-11-21)
- CISA #StopRansomware Guide, CISA(as of 2026-11-21)
- Back Up Business Data, CISA(as of 2026-11-21)
- 45 CFR 164.402 (eCFR, version 2026-11-01), eCFR / U.S. Government(as of 2026-11-21)
- 45 CFR 164.404(a) (eCFR, version 2026-11-01), eCFR / U.S. Government(as of 2026-11-21)
- 45 CFR 164.408 (eCFR, version 2026-11-01), eCFR / U.S. Government(as of 2026-11-21)
- 45 CFR 164.410 (eCFR, version 2026-11-01), eCFR / U.S. Government(as of 2026-11-21)
- HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, Federal Register / HHS(as of 2026-11-21)
- Unified Agenda entry, RIN 0945-AA22, reginfo.gov / OMB(as of 2026-11-21)
- DDSArk, DDSArk (ROOT32 LLC)(as of 2026-11-21)
- DDSArk FAQ, DDSArk (ROOT32 LLC)(as of 2026-11-21)
- DDSVPN, DDSVPN (ROOT32 LLC)(as of 2026-11-21)
- DDSVPN security page, DDSVPN (ROOT32 LLC)(as of 2026-11-21)
- DDSVPN pricing page FAQ, DDSVPN (ROOT32 LLC)(as of 2026-11-21)
- DDSBreach alerts, DDSBreach (ROOT32 LLC)(as of 2026-11-21)
- DDSBreach methodology, DDSBreach (ROOT32 LLC)(as of 2026-11-21)
- DDS ID, DDS ID (ROOT32 LLC)(as of 2026-11-21)
- DDS ID pricing, DDS ID (ROOT32 LLC)(as of 2026-11-21)
General information, not legal or medical advice. For decisions about HIPAA, breaches or licensing, talk to a qualified attorney or your state board.