Every breach represents a real dental practice facing fines, lawsuits, and patients who may never come back. Here's what's happening, why, and how to prevent it at your practice.
Two of the more instructive dental data breaches from recent enforcement.
Takeaway: Multi-location groups are a high-value target. One shared back-office server can expose every location simultaneously. Practice isolation and per-record encryption keys are the first line of defense.
Takeaway: Ransomware continues to be the #1 vector for independent practices. MFA on every account and encrypted backups are non-negotiable.
Six protective layers shipped on every Intake.Dental account.
Every PHI field gets its own AES-256-GCM data encryption key, then wrapped in our Glyph Cipher polyglottal layer: both layers included on every account. If one record is ever exposed, the rest of the database stays dark.
Per-record encryption keys mean a server compromise doesn't equal a database compromise. Attackers have to break each record individually.
Role-based access control, MFA, and automatic session timeout on every account. Staff can only see the data their role actually needs.
Append-only timestamped access logs with IP and user identification on every PHI read and write. Exportable for your own compliance audits.
Tenant-specific encryption and row-level security mean no practice can ever see another practice's data, even in a worst-case application bug.
Signed Business Associate Agreements with every practice and a 72-hour incident notification runbook built into our on-call rotation.
Every Intake.Dental account ships with the protections above (encryption, MFA, audit logging, and an executed BAA) at no extra cost.
