Skip to main content
Security · SECURITY

Data Protection Services for Dental Offices: What's Included (2026)

Three companies have now used the words "data protection" in a quote for your practice: the backup vendor, the add-on your practice software is pushing, and the IT company that came to look at the server. Each one covers something different, none of them says exactly what, and the renewal form from your insurer wants a yes or no by Friday.

This guide is written for the owner comparing those quotes. It lays out the nine layers, shows where patient data actually sits in a dental office, quotes what the HIPAA Security Rule and the breach notification rules say (the text, read on 18 November 2026, not a vendor's version of it), and ends with a scorecard you can run against any proposal and a list of what a service should be able to show you every month.

In this guide
  1. What does a data protection service for a dental office include?
  2. The nine layers that protect patient data in a dental office
  3. Where does patient data actually live in a dental office?
  4. What does the HIPAA Security Rule text say about protecting patient data?
  5. What do the breach notification rules say?
  6. Backup product, data protection service or managed IT: which does your practice need?
  7. How do you evaluate a data protection service?
  8. What should a data protection service report to you each month?
  9. What does data protection cost for a dental office?
  10. The IT side: who does what in each layer
  11. What to ask your IT provider about data protection
  12. How Legend Networking can help
  13. Frequently asked questions
  14. The bottom line

What does a data protection service for a dental office include?

A data protection service covers every place patient data can be lost, locked, read or changed, and gives you evidence that each safeguard worked. A backup product only copies files. A managed IT plan usually includes data protection among many other things, but the word "included" needs checking line by line. The table shows what each one typically carries.

What is being soldUsually coversUsually leaves outWho is accountable when something fails
Backup product (software or appliance, bought on its own)Scheduled copies of selected folders or the whole server; cloud storage; sometimes a bootable imageWhether the practice database was captured in a usable state; restore tests; encryption of workstations; logins and MFA; email; vendors; disposalThe office, unless someone is paid to watch the job and test the restore
Data protection service (managed)The nine layers in this guide: tested backups with an offline or immutable copy, encryption at rest and in transit, access control and MFA, device protection and patching, logging and monitoring, email security, vendor agreements, disposal; a monthly evidence reportHelp desk for day-to-day problems; hardware; phones; practice software support, unless bundledThe provider, with named deliverables in the contract
Managed IT plan for a dental practiceHelp desk, monitoring, patching, workstations, server, network, plus some or all of the nine layersVaries by provider: restore testing, immutable copies, email filtering and disposal are the layers most often missing or sold as add-onsThe provider, for the layers the plan names
Cloud practice management softwareBackup and encryption of the vendor's own database and serversYour workstations, your email, your imaging files on local drives, your network, your logins, your old hardwareThe vendor for its platform; the office for everything in the building

Two things follow from the table. First, "we have cloud software, so our data is protected" covers one row of the data map further down and not the other eight. Second, a managed IT quote and a data protection quote can describe the same work in different words, so the scorecard later in this guide asks the same twelve questions of both.

The nine layers that protect patient data in a dental office

Patient data in a dental office is protected by nine layers working together, and a weakness in any one of them is where the data leaves. The table gives each layer, what it protects against, what a good implementation looks like in a dental office, and the evidence a service should be able to hand you on request. The sections after it go through each layer.

LayerProtects againstWhat good looks like in a dental officeEvidence to ask for
1. Backup and restoreServer failure, deletion, ransomware, fire, flood, theftThree copies on two kinds of storage, one off site and one offline or immutable; the practice database captured in a usable state; restores tested on a scheduleThe last restore-test record: date, what was restored, how long it took, who signed
2. Encryption at restStolen or lost laptops, servers and drives; decommissioned hardwareFull-disk encryption on every workstation, laptop and server; encrypted backup media; recovery keys stored where the office can reach themA device list with the encryption state of each one
3. Encryption in transit and remote accessInterception of data moving over the internet; exposed remote desktopEncrypted remote access through a VPN or a managed remote-access tool; no remote desktop open to the internet; secure sending of images and recordsA diagram or list of every remote path into the office and how each is protected
4. Access control and MFAShared passwords, departed staff who still have access, phished loginsOne login per person on Windows, the practice software and email; role-based rights; MFA on email, remote access and admin accounts; access removed the day someone leavesA quarterly user-access review with join and leave dates
5. Device protection and patchingMalware, exploited software flaws, unsupported operating systemsEndpoint protection with central alerts; security updates applied on a schedule and checked; no unsupported Windows versions; screens that lockA patch report by device and an inventory of operating system versions
6. Logging and monitoringSilent failures, unnoticed intrusions, backup jobs that stopped weeks agoBackup, security and login events collected centrally and watched; alerts that reach a person; a record of what was reviewedA sample of the monthly review and the alerts it raised
7. Email securityPhishing, spoofed senders, mailbox takeoverFiltering for malicious attachments and look-alike senders; MFA on every mailbox; a way to send patient information securely; short training with test phishingPhishing test results and the filter's quarantine report
8. Vendor agreements and accessBreaches through vendors, cloud tools and remote supportA register of every vendor that creates, receives, stores or sends patient data, with a signed business associate agreement and a record of which of them has remote accessThe vendor register, with agreement dates and access method
9. Disposal and media re-usePatient data leaving on an old server, drive, sensor PC or copierEvery retired device wiped or destroyed by a method you can name, with a certificate or record per serial numberThe disposal log

Layer 1: backup, with a copy ransomware cannot reach

Backups are the layer most offices believe they have and most often discover they do not on the day of a failure. The common pattern is a cloud job that stopped months ago, or a job that copies every folder except the one with the live practice database, which is locked while the software runs. A service, as opposed to a product, owns both problems: it confirms the database is captured in a restorable state and it restores something on a schedule to prove it.

The federal cybersecurity agency's ransomware guide puts the storage rule in one sentence: "Maintain offline, encrypted backups of critical data, and regularly test the availability and integrity of backups in a disaster recovery scenario". The same guide notes that "Some cloud vendors offer immutable storage solutions that can protect stored data without the need for a separate environment" and adds, "Use immutable storage with caution as it does not meet compliance criteria for certain regulations and misconfiguration can impose significant cost." In plain words: an offline copy is disconnected; an immutable copy is online but cannot be changed or deleted for a set period. Either keeps a working copy out of reach of an attacker who already controls the server. Ask which one you are buying and how it is proven.

What to back up, how often, how to set recovery targets and how a restore test is run is covered in our guide to dental data backup; the step-by-step test and the scorecard are in the dental backup and disaster recovery checklist. For the service itself, see dental backup and disaster recovery services.

Layer 2: encryption at rest

Encryption at rest means the data on a drive is unreadable without the key, so a stolen server, a laptop left in a car or a drive pulled from an old workstation gives up nothing. Microsoft describes its built-in Windows tool this way: "BitLocker is a data protection feature that integrates with the operating system to address the threats of data theft or exposure from lost, stolen, or improperly decommissioned devices." Microsoft lists Windows Pro, Enterprise and Education among the editions that support it; the work is turning it on for every device, storing the recovery keys somewhere the office controls, and keeping a list that shows the state of each machine.

Two places get missed. The first is the server itself, because it never leaves the building, until the day it is carried out by a thief or a recycler. The second is backup media: an external drive that rotates off site is a copy of every patient record, and it needs the same protection as the server.

Layer 3: encryption in transit and remote access

Data in transit is data moving over a network: a remote login from home, an X-ray sent to a specialist, a claim sent to a clearinghouse, a backup leaving for the cloud. The protection is an encrypted channel for each one and, above all, no remote desktop port open to the internet. The same CISA guide is blunt about why: "Threat actors often gain initial access to a network through exposed and poorly secured remote services, and later traverse the network using the native Windows RDP client." A data protection service should be able to list every path into the office and say how each is secured.

How to set up remote work safely is in our guide to dental office remote access security; the secure way to move images is in how to send scans to a dental lab securely.

Layer 4: access control and multi-factor authentication

Access control is one login per person, rights that match the job, and removal of access the day a person leaves. Shared operatory logins are the usual failure: convenient at the chair, but no record of who did what, and a password everyone knows is a password nobody changes. The practice software makers build for individual logins. Open Dental's manual says, "Every person who uses Open Dental should have a unique user name and password for logging on," and notes that "Every time a user logs in, logs off or closes Open Dental, an entry is created in the Audit Trail." Dentrix, Eaglesoft and other systems have their own user settings; a service sets them up and reviews them.

Multi-factor authentication adds a second proof at login. The federal cybersecurity agency's description: "MFA is a layered approach to securing your online accounts and the data they contain. When you enable MFA in your online services (like email), you must provide a combination of two or more authenticators to verify your identity before the service grants you access." For a dental office the three places MFA matters most are email, remote access and any administrator account. Password handling for the rest is covered in password management for dental offices, and the leaver process in IT onboarding and offboarding for dental staff.

Layer 5: device protection and patching

Every workstation, sensor PC and server runs software with known flaws until it is updated, and an unsupported operating system never gets the fix. Device protection is endpoint security that reports to a central console, security updates applied and verified on a schedule, screens that lock when unattended, and no machine running a Windows version that has left support. Imaging rooms are where this slips, because an update that breaks a sensor driver is remembered longer than the flaw it closed; a service tests updates against the imaging software and keeps a record of what was applied where. Our guide to patch management for dental practices covers the schedule and the exceptions.

Layer 6: logging and monitoring

Logging is the record; monitoring is someone reading it. The practice software keeps an audit trail of who opened which chart, Windows records logins and failures, the backup software records each job, and the firewall records connections. A data protection service collects these centrally, sets alerts that reach a person, and reviews them on a schedule it can show you. This is the layer that turns "the backup stopped in March" into "the backup failed last night and was fixed this morning".

Layer 7: email security

Phishing is one of the initial access routes CISA's ransomware guide names, and in a dental office it arrives as a convincing invoice, a fake login page, a message from a "vendor" asking to change bank details. Email security is filtering for malicious attachments and look-alike senders, MFA on every mailbox, a secure way to send patient information when it must go by email, and short, regular training with test phishing so the front desk knows what a lure looks like. What a secure email setup needs is covered in HIPAA email for dental offices.

Layer 8: vendor agreements and vendor access

Patient data leaves the building every day through vendors: the cloud practice software, the clearinghouse, the texting tool, the imaging cloud, the billing company, the IT provider itself. Each one that creates, receives, stores or sends patient data on your behalf will usually be asked for a business associate agreement (which ones need one is a question for your compliance adviser), and each one with remote access to your systems needs that access known and controlled. A data protection service keeps the register: who the vendors are, which agreement is signed and when, and how each connects. The agreements themselves are explained in business associate agreements for dental practices.

Layer 9: disposal and media re-use

The last layer is the one most offices never budget for. Servers, workstations, sensor PCs, external drives, copiers with hard drives and old phones all leave the practice at some point, and each one can carry patient data out with it. Disposal means wiping or destroying the storage by a method you can name and keeping a record per device. A widely used reference is the National Institute of Standards and Technology's Special Publication 800-88 Revision 2, Guidelines for Media Sanitization (published September 2025), which defines sanitization as "a process that renders access to target data on the media infeasible for a given level of effort." Ask for the method and the certificate, not a promise.

Where does patient data actually live in a dental office?

Patient data in a dental office sits in far more places than the practice management database: imaging folders, CBCT workstations, scanned documents, email, texting and phone platforms, cloud software, backup media, staff phones and retired hardware. A data protection service starts with this map, because a layer that covers the server and misses the imaging PC protects half the practice.

Where the data sitsTypical formLayers that must cover itOften forgotten because
Practice management database (Dentrix, Eaglesoft, Open Dental and others on a local server)A database file set that is locked while the software runs1, 2, 4, 5, 6Backup jobs skip locked files without saying so
Imaging and CBCT filesLarge image folders on the server or on the imaging workstation; a separate CBCT PC with its own drive1, 2, 5, 9The CBCT machine came with its own computer that nobody manages
Scanned documents, treatment plans, consent formsFiles in the practice software's document folder or a shared drive1, 2, 4Shared drives grow for years without a backup check
Cloud practice management softwareThe vendor's database, reached by browser3, 4, 7, 8The office assumes the vendor covers its workstations and email too
Email and attachmentsMailboxes, often in Microsoft 365 or Google Workspace; X-rays and referrals attached3, 4, 7, 8Nobody counts a mailbox as a patient record store
Texting, reminder, phone and AI answering platformsVendor-held messages and recordings with names, appointments and sometimes treatment details8They were bought by the front desk, not by IT
Clearinghouse and payment toolsClaims, statements and card data in transit and in vendor portals3, 8Treated as billing, not as data
Backup media and cloud backup accountsFull copies of everything above2, 4, 6A backup account with one shared password protects a complete copy of the practice
Staff phones and home computersEmail on a personal phone; a remote login from a family PC3, 4, 5Convenience during a staff shortage became permanent
Retired servers, workstations, drives, copiersWhole records on hardware that has left the building9There was never a disposal step

Walk this table with your current provider. If a row has no owner, that row is where the next problem starts. For the wider picture of how the practice, the IT provider and the software vendor split these duties, see who owns what in dental HIPAA IT responsibilities.

What does the HIPAA Security Rule text say about protecting patient data?

The Security Rule (45 CFR Part 164, Subpart C) names the safeguards covered entities and business associates must address, marks each implementation specification "Required" or "Addressable", and leaves the choice of measures to the organisation. The quotations below are the rule text as published by the Cornell Legal Information Institute, read on 18 November 2026, beside the layer each touches.

What your practice must do under any of them is a question for your compliance adviser, not for this guide.

The general rule, at 164.306(a)(1), is that covered entities and business associates must "Ensure the confidentiality, integrity, and availability of all electronic protected health information the covered entity or business associate creates, receives, maintains, or transmits." On the two labels, 164.306(d)(3) says that for an addressable specification an organisation must "Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment, when analyzed with reference to the likely contribution to protecting electronic protected health information" and, if it does not implement it, "Document why it would not be reasonable and appropriate to implement the implementation specification" and "Implement an equivalent alternative measure if reasonable and appropriate."

Rule text (quoted)SectionMarkedLayer in this guide
"Risk analysis (Required). Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate."164.308(a)(1)(ii)(A)RequiredAll nine: the analysis is where the data map comes from
"Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports."164.308(a)(1)(ii)(D)Required6
"Identify the security official who is responsible for the development and implementation of the policies and procedures required by this subpart for the covered entity or business associate."164.308(a)(2)StandardThe practice names this person; a service supports them
"Termination procedures (Addressable). Implement procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends or as required by determinations made as specified in paragraph (a)(3)(ii)(B) of this section."164.308(a)(3)(ii)(C)Addressable4
"Protection from malicious software (Addressable). Procedures for guarding against, detecting, and reporting malicious software."164.308(a)(5)(ii)(B)Addressable5, 7
"Password management (Addressable). Procedures for creating, changing, and safeguarding passwords."164.308(a)(5)(ii)(D)Addressable4
"Response and reporting (Required). Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity or business associate; and document security incidents and their outcomes."164.308(a)(6)(ii)Required6
"Data backup plan (Required). Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information."164.308(a)(7)(ii)(A)Required1
"Disaster recovery plan (Required). Establish (and implement as needed) procedures to restore any loss of data."164.308(a)(7)(ii)(B)Required1
"Emergency mode operation plan (Required). Establish (and implement as needed) procedures to enable continuation of critical business processes for protection of the security of electronic protected health information while operating in emergency mode."164.308(a)(7)(ii)(C)Required1
"Testing and revision procedures (Addressable). Implement procedures for periodic testing and revision of contingency plans."164.308(a)(7)(ii)(D)Addressable1
"A covered entity may permit a business associate to create, receive, maintain, or transmit electronic protected health information on the covered entity's behalf only if the covered entity obtains satisfactory assurances, in accordance with § 164.314(a), that the business associate will appropriately safeguard the information."164.308(b)(1)Standard8
"Workstation security. Implement physical safeguards for all workstations that access electronic protected health information, to restrict access to authorized users."164.310(c)Standard5
"Disposal (Required). Implement policies and procedures to address the final disposition of electronic protected health information, and/or the hardware or electronic media on which it is stored."164.310(d)(2)(i)Required9
"Media re-use (Required). Implement procedures for removal of electronic protected health information from electronic media before the media are made available for re-use."164.310(d)(2)(ii)Required9
"Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity."164.312(a)(2)(i)Required4
"Automatic logoff (Addressable). Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity."164.312(a)(2)(iii)Addressable5
"Encryption and decryption (Addressable). Implement a mechanism to encrypt and decrypt electronic protected health information."164.312(a)(2)(iv)Addressable2
"Audit controls. Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information."164.312(b)Standard6
"Integrity. Implement policies and procedures to protect electronic protected health information from improper alteration or destruction."164.312(c)(1)Standard1, 6
"Person or entity authentication. Implement procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed."164.312(d)Standard4
"Transmission security. Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network."164.312(e)(1)Standard3
"Encryption (Addressable). Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate."164.312(e)(2)(ii)Addressable3
"Time limit (Required). Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later."164.316(b)(2)(i)RequiredThe evidence a service produces is part of this documentation

Two points for the buying decision. The words "Required" and "Addressable" in the table are the rule's own labels; whether an addressable specification is reasonable and appropriate for your practice is the assessment the rule describes, and it belongs to the practice and its adviser. And the rule text names things a service produces, such as audit logs, access reports, retrievable exact copies and documented incidents, which is why the monthly evidence table later in this guide matters as much as the technology.

Terms such as "security official", "risk analysis" and "business associate" are used here as they appear in the rule text. The full list of what a dental office needs in place, organised as a checklist with owners, is in our HIPAA compliance checklist for dental offices. The IT safeguards Legend runs day to day are described on the HIPAA IT support for dental practices page.

What do the breach notification rules say?

The breach notification rules (45 CFR Part 164, Subpart D) define a breach, set a presumption, and give notification duties and deadlines. The text below is quoted from the Cornell Legal Information Institute as read on 18 November 2026, because terms such as "unsecured", "discovered" and "log" describe records a data protection service either produces or does not.

How the rules apply to a given event is a question for your compliance adviser.

The definition, at 164.402: "Breach means the acquisition, access, use, or disclosure of protected health information in a manner not permitted under subpart E of this part which compromises the security or privacy of the protected health information." The same section says that, with stated exceptions, such an acquisition, access, use or disclosure "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 based on a risk assessment of at least the following factors", and lists four: the nature and extent of the information involved, the unauthorized person who used it or received it, whether it "was actually acquired or viewed", and "The extent to which the risk to the protected health information has been mitigated."

The same section defines the information the notification duties attach to: "Unsecured protected health information means protected health information that is not rendered unusable, unreadable, or indecipherable to unauthorized persons through the use of a technology or methodology specified by the Secretary in the guidance issued under section 13402(h)(2) of Public Law 111-5."

What the text coversQuoted textSection
When a breach counts as discovered"a breach shall be treated as discovered by a covered entity as of the first day on which such breach is known to the covered entity, or, by exercising reasonable diligence would have been known to the covered entity."164.404(a)(2)
Deadline for notifying individuals"a covered entity shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach."164.404(b)
What the notice must contain"A brief description of what happened, including the date of the breach and the date of the discovery of the breach, if known"; the types of information involved; steps individuals should take; what the entity is doing "to investigate the breach, to mitigate harm to individuals, and to protect against any further breaches"; and contact procedures.164.404(c)(1)
Plain language"The notification required by paragraph (a) of this section shall be written in plain language."164.404(c)(2)
Notifying the Secretary, 500 or more individuals"For breaches of unsecured protected health information involving 500 or more individuals, a covered entity shall, except as provided in § 164.412, provide the notification required by paragraph (a) of this section contemporaneously with the notice required by § 164.404(a) and in the manner specified on the HHS Web site."164.408(b)
Notifying the Secretary, fewer than 500"For breaches of unsecured protected health information involving less than 500 individuals, a covered entity shall maintain a log or other documentation of such breaches and, not later than 60 days after the end of each calendar year, provide the notification required by paragraph (a) of this section for breaches discovered during the preceding calendar year, in the manner specified on the HHS web site."164.408(c)
What a business associate's contract must say about incidentsThe contract must provide that the business associate will "Report to the covered entity any security incident of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410."164.314(a)(2)(i)(C)

For the buying decision, notice what the text asks an organisation to be able to say: when it knew, what was involved, whether the data was viewed, how the risk was mitigated, and what it is doing to prevent a repeat. Logs, encryption records, access reviews and incident records are the raw material for those sentences, and a service that keeps them is worth more on a bad day than one that does not. What to do in the first hours after a suspected incident, and how the practice recovers, is in dental ransomware recovery.

Backup product, data protection service or managed IT: which does your practice need?

Most single-location practices with a server need every layer covered, and a managed IT plan that names each layer is usually the simplest way to buy that; a stand-alone backup product only makes sense beside someone who already runs the other eight layers. The table matches common situations to the right purchase.

Your situationWhat you most likely needWhyWhat to check before you buy
Server-based practice software (Dentrix, Eaglesoft, Open Dental on a local server), one location, no in-house ITA managed IT plan that names all nine layers, or a data protection service alongside a basic support planEvery layer in the data map is your responsibility; nobody else is watching the serverThat restore tests, an offline or immutable copy, MFA, email filtering and disposal are written into the plan, not "available"
Cloud practice software, one locationA data protection service or a managed plan covering layers 2 to 9, with layer 1 for imaging files, documents and emailThe vendor protects its database; the imaging PC, workstations, mailboxes and old hardware are still yoursWhat the vendor's agreement says it backs up and for how long; whether your imaging is local
A practice with a part-time or family IT personA data protection service as a defined scope beside that personThe nine layers need tools, a console and a schedule one person rarely runs aloneA written split of who owns each layer and who gets the alerts
Two to ten locations, or an acquired office joining a groupA managed plan with the same standard at every site and one evidence reportEach acquired office arrives with its own backup, logins and vendorsWhether the provider standardises and reports per location
Any practice renewing cyber insuranceWhichever of the above, plus the evidence pack the questionnaire asks forRenewal questionnaires often ask about MFA, backups, endpoint protection and trainingThat the provider can produce the answers with dates, not opinions

If the quote in front of you is a managed plan, our guide to managed IT services for dental practices sets out what a plan should cover and how to compare one against another. If it is a stand-alone backup product, keep it only if the other eight layers have a named owner. The cyber insurance questions that drive many of these purchases are listed in dental cyber insurance requirements.

How do you evaluate a data protection service?

Evaluate a data protection service by asking for evidence, not features: the last restore-test record, the device encryption list, the user-access review, the vendor register and the disposal log. A provider that runs these layers has them at hand. The twelve questions below separate a service from a product, with a good answer and a weak one for each.

QuestionA good answerA weak answer
1. When did you last restore our practice database from backup, and can we see the record?A dated record with what was restored, how long it took and who signed itThe jobs run every night and we get success emails.
2. Which backup copy can an attacker who controls our server not reach, and how is that proven?An offline or immutable copy, named, with the retention period and a testIt is in the cloud.
3. Which of our devices are encrypted at rest, and where are the recovery keys?A device list with encryption state; keys stored in a place the office controlsThe server is in a locked closet.
4. How does anyone reach our systems from outside the office?A list of every remote path, each through a VPN or managed tool, with MFA; no remote desktop open to the internetWe use remote desktop; it has a strong password.
5. Does every person have their own login to Windows, the practice software and email?Yes, with a quarterly access review and leave datesThe operatories share a login so hygienists can move rooms.
6. Where is MFA turned on?Email, remote access and administrator accounts at least, with the enforcement reportWe can turn it on if you want.
7. What is our patch status, and are any machines on an unsupported operating system?A report by device, with exceptions explained and datedWindows updates itself.
8. Who reads our logs and alerts, and what did they find last month?A monthly review with the alerts raised and what was doneEverything is monitored.
9. What stops a phishing email reaching the front desk, and what happened in the last test?Filtering in place, MFA on mailboxes, test results by quarterStaff know not to click links.
10. Which vendors have access to our systems or hold our patient data, and where are the agreements?A register with agreement dates and access method, including the provider's own agreementYou would need to ask the vendors.
11. How do you dispose of a retired server or workstation, and what record do we get?A named wiping or destruction method and a certificate or log per deviceWe recycle them.
12. What do we receive from you every month?A report covering the layers above, in writingCall us any time.

What to verify before you sign

    • The contract names each layer the service covers and what you receive as evidence, with a frequency.
    • Restore testing is a scheduled deliverable, with the database and imaging named, not a one-off at onboarding.
    • The offline or immutable copy is described: where it is, how long it is kept, how it is tested.
    • Recovery keys, administrator passwords and the backup account belong to the practice, and you have a copy or a documented way to get them.
    • The provider's own business associate agreement is signed before any access is granted, and its remote-access tool is on the vendor register with MFA.
    • Exit terms say how your data, your backups and your keys come back to you, and in what format, if you leave.
    • The quote states which layers are excluded, so an excluded layer is a known gap rather than a surprise.

This scorecard works alongside how to choose a dental IT company, which covers the wider questions of response, references and contract terms, and our list of the best dental IT companies, for a side-by-side view of national providers.

What should a data protection service report to you each month?

A data protection service should send a short written report every month that shows, layer by layer, what ran, what failed, what was fixed and what was tested, with dates. The report is how an owner who is not technical knows the service is real. The table is the minimum worth asking for.

LayerWhat the monthly report showsA red flag in the report
Backup and restoreJobs completed per day; failures and fixes; the restore test performed this period or the date of the last oneA month with no restore test and no date for the next
Encryption at restCount of devices encrypted versus total; any new device added unencrypted"Not applicable"
Remote accessPaths in use; any new remote account; MFA status on eachA remote desktop port opened "temporarily"
Access controlAccounts added and removed, with dates against your staff changes; last access review dateA departed employee still active
Device protection and patchingPatch compliance by device; machines with exceptions; endpoint alertsAn operating system past its support date with no replacement plan
Logging and monitoringAlerts raised, by type; what was investigated; what was closedZero alerts for a whole month
Email securityMessages quarantined; phishing test results; mailboxes without MFAA mailbox added without MFA
VendorsChanges to the vendor register; agreements signed or expiredA new tool with access and no agreement
DisposalDevices retired and the method and certificate for eachDevices removed from the inventory with no disposal record

Keep these reports. Under 164.316(b)(2)(i), quoted above, documentation the rule requires is retained for six years, and your compliance adviser can tell you which of these records fall under it. A folder of twelve monthly reports also answers most of a cyber insurance questionnaire without a scramble.

What does data protection cost for a dental office?

Data protection for a dental office is usually priced in three shapes: per device per month inside a managed plan, per server or per gigabyte for backup storage, and per user for email security and MFA. A stand-alone backup product is the cheapest line and the smallest part of the protection; compare quotes on layers and evidence, not the total.

Three questions keep a comparison honest. First, which of the nine layers does the price cover, and which are add-ons? A plan that excludes restore testing, email filtering or disposal is not cheaper; it is smaller. Second, what is storage-dependent? Backup prices usually rise with the size of the imaging archive, so ask for the price at your current data size and at double. Third, what is the exit cost? Getting your backups and keys back should not carry a fee you learn about on the way out.

Legend publishes two price points: dental IT support "Starting at $360 per month", and backup protection from $39.99 per month (storage-dependent). The rest of a quote depends on the practice's systems and is set out after a review. For how dental IT pricing is structured in general, see the dental IT support cost guide.

The IT side: who does what in each layer

A data protection service runs the technology in each layer; the practice keeps the decisions the rule text assigns to the organisation, such as naming the security official, owning the risk analysis and setting policies. The table shows the usual split, so the contract and the practice's own HIPAA program fit together without gaps or double counting.

LayerWhat the IT provider doesWhat stays with the practice
1. Backup and restoreConfigures jobs; verifies the database capture; keeps the offline or immutable copy; runs and records restore tests; sets recovery targets with youDecides the recovery targets; owns the emergency-mode plan for seeing patients while systems are down
2. Encryption at restEnables encryption on every device; stores and escrows keys; reports stateDecides where keys are held and who in the practice may retrieve them
3. Encryption in transit and remote accessBuilds the remote-access path; closes exposed ports; secures image and record sendingDecides who may work remotely and from which devices
4. Access control and MFACreates individual accounts; sets role-based rights; enforces MFA; removes leavers on noticeTells IT the same day someone joins, changes role or leaves; signs off the quarterly review
5. Device protection and patchingRuns endpoint protection; schedules and verifies updates; retires unsupported systems; tests updates against imagingApproves replacement of unsupported machines; agrees maintenance windows
6. Logging and monitoringCollects logs; watches alerts; reviews activity; records incidents and outcomesReviews the monthly report; decides what counts as an incident for its own procedures
7. Email securityConfigures filtering and MFA; runs phishing tests and trainingSets the policy on what may be sent by email and follows the training
8. Vendor agreements and accessMaintains the technical side of the register; controls vendor remote access; signs its own agreementSigns agreements with every vendor; decides which vendors may hold patient data
9. Disposal and media re-useWipes or destroys media by a named method; issues certificates; updates the inventoryKeeps the disposal records with its other documentation

The rule text at 164.308(a)(2), quoted above, asks the covered entity to identify its security official; who holds that role, and who makes the risk decisions, is for the practice and its compliance adviser to settle. A good provider makes those decisions easier by putting the evidence in front of the person who holds the role. For the whole picture of a provider's duties, from the server to the help desk, see dental IT support; for the security stack specifically, see dental cybersecurity services.

What to ask your IT provider about data protection

Use these in the next review meeting or send them with a request for proposal. A provider that runs these layers every day will answer from records; a vague answer on any of them is itself the answer.

Backups

  • Which copy of our data can an attacker who controls the server not reach, and how do you prove it each month?
  • When did you last restore our practice database and our imaging folder, how long did each take, and who signed the record?

Devices and encryption

  • Which of our devices are not encrypted today, and when will they be?
  • Where are our recovery keys and administrator passwords kept, and how does the practice get them if we part ways?

Access

  • Which accounts are shared, and what is the plan to end that?
  • Where is MFA enforced, and where is it still optional?
  • How quickly is access removed when we tell you someone has left, and how do we confirm it happened?

Monitoring and email

  • Who reads our alerts, and what did they act on last month?
  • When was our last phishing test, and what did the results show?

Vendors and disposal

  • Which vendors have remote access to our systems, and is each one on the register with a signed agreement?
  • What happens to a retired server, and what record do we receive?

The service itself

  • Which of the nine layers are excluded from our plan, and what would it cost to add them?
  • What does the monthly report contain, and can we see last month's for a similar practice with the names removed?

The answers belong in the file with your risk analysis and policies, where the practice's own HIPAA program lives.

How Legend Networking can help

Legend Networking, based in Dallas, has served over 3,500 practices since 2004. Its engineers are in-house, with no outsourced first-level triage; monitoring runs 24/7, and the helpdesk is staffed 24/7 at 1-800-794-1588. To see how the nine layers stand in your own office, the Free Dental IT Assessment looks at your computers, software, network security, backups and performance, and ends with written findings and prioritized recommendations.

Ian Lynch, who wrote this guide, has 22 years in dental IT; he oversees the NOC, onsite dispatch and client technology roadmaps. Legend's Google rating is 4.8, from 173 reviews. You can see the shape of the work in a managed IT onboarding whose published scope includes backups, security and user access, or find dental IT in your city.

Questions

Frequently asked questions

What is a data protection service for a dental office?

A data protection service is a managed set of safeguards that keeps patient data available, intact and private, with evidence that each safeguard worked. It covers tested backups with an offline or immutable copy, encryption on devices and connections, individual logins with MFA, patching, logging and monitoring, email security, vendor agreements and secure disposal, and it reports on all of them each month.

Is a backup the same as data protection?

No. A backup is one of nine layers. It protects against loss and ransomware if the copy is restorable and out of an attacker's reach, but it does nothing about a stolen laptop, a shared password, a phished mailbox, a vendor with open remote access or an old server leaving the building. A data protection service covers all of those and shows the evidence.

What is an immutable backup and does a dental office need one?

An immutable backup is a copy that cannot be changed or deleted for a set period, even by an administrator, so an attacker who controls the server cannot destroy it. An offline copy achieves the same by being disconnected. CISA's ransomware guide recommends offline, encrypted backups and notes that immutable storage should be used with caution. Ask which kind your service provides and how it is tested.

What types of records are kept in a dental office that need protecting?

A dental office keeps charts, treatment notes and plans, X-rays and CBCT scans, intraoral photos, consent forms, insurance and payment records, correspondence with specialists and labs, appointment and recall histories, and staff records. Most of it is electronic and sits in the practice software, imaging folders, email, vendor platforms and backups, so each of those places needs a named safeguard.

Does cloud dental software protect our patient data?

Only partly. A cloud practice management vendor backs up and encrypts its own database and servers. Your workstations, imaging computer, mailboxes, network, logins, remote access and retired hardware are still in your building and still your responsibility. Read the vendor's agreement for what it backs up and for how long, then cover the remaining layers yourself or through a service.

How long does a dental office have to notify patients after a breach?

The rule text at 45 CFR 164.404(b) says a covered entity "shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach." Section 164.404(a)(2) sets out when a breach is treated as discovered. Whether an event is a breach, and what your practice must do, is a question for your compliance adviser.

What is HIPAA in the dental field?

HIPAA is the federal law whose rules, in 45 CFR Parts 160 and 164, cover how a dental practice uses, discloses and protects patient health information. The Privacy Rule (Subpart E) covers uses and disclosures, the Security Rule (Subpart C) names administrative, physical and technical safeguards for electronic information, and Subpart D covers breach notification. Which rules apply to your practice is for your compliance adviser.

How much do data protection services cost for a dental office?

Prices are usually set per device per month inside a managed plan, per server or per gigabyte for backup storage, and per user for email security and MFA. Legend's published price points are dental IT support "Starting at $360 per month" and backup protection from $39.99 per month (storage-dependent). Compare quotes on which layers are included and what evidence comes with them.

How should a dental office dispose of an old server or computer?

Have the storage wiped or destroyed by a named method before the device leaves, and keep a record per serial number. The rule text at 45 CFR 164.310(d)(2)(i) marks disposal as Required, and NIST Special Publication 800-88 Revision 2 is a widely used reference for sanitization methods. A recycler's receipt without a wiping certificate is not a disposal record.

Who in the practice is responsible for data protection if we hire a service?

The rule text puts naming one on the practice: 45 CFR 164.308(a)(2) asks a covered entity to "Identify the security official who is responsible for the development and implementation of the policies and procedures required by this subpart." A service runs the safeguards and produces the evidence; that official, with the practice's compliance adviser, owns the risk analysis, the policies and the decisions.

The bottom line

If you cannot name the copy of your data an attacker cannot reach, the devices that are not encrypted, or the vendors with remote access to your systems, start there. Ask for a review of your dental backup and disaster recovery setup and the other eight layers, and run the twelve questions above against whatever you are quoted. For the wider scope of dental IT support for your practice, the same team can walk through the data map with you and show what the monthly report would contain.

Ian Lynch
About the author

Ian Lynch

Owner & Operator, Legend Networking

22 years in dental IT. Oversees the NOC, onsite dispatch and client technology roadmaps for practices nationwide.

  • Operations center

    Dallas, Texas

    Serving dental practices nationwide since 2004

  • NOC hours

    24/7 monitoring

    Helpdesk staffed 24/7 at 1-800-794-1588

  • Engineers

    In-house only

    No outsourced first-level dental IT triage

  • Onsite dispatch

    By appointment

    Technicians deployed across served dental markets

About Legend Networking
Your next step

Ask for a review of how your patient data is protected

Tell us what you are running and we will review it with you.

Or call 1-800-794-1588

Free IT assessment

Tell us what you are running

Your information is secure and will never be shared.