How to Choose a Dental Cybersecurity Provider: 12 Controls (2026)
Three proposals are on the desk: one from the IT company that already looks after the server, one from a security firm a colleague uses, one bundled with the practice management software renewal. All three say "complete protection", and none of them lists the same things.
This guide gives you that list. It compares the kinds of provider a dental office can hire, defines what "included" has to mean for each of the twelve controls, adds the questions a group should ask that a single office need not, explains how plans are priced, and ends with what to verify before you sign and what the first 90 days should look like.
Choose a dental cybersecurity provider by holding each proposal against a fixed list: the twelve controls a managed security plan must include, written evidence for each one, named experience with your practice software and imaging, a signed business associate agreement, and a plain monthly report. Then ask the same questions of every provider and compare the answers in writing.
- Hold every proposal against the same twelve controls, each marked included, optional or excluded, with the evidence named.
- A plan described by product names is a product list; ask for the restore test date, the EDR device count and a sample monthly report.
- One dental-focused provider for support and security usually beats two vendors for a single office; a group with its own IT lead can run both.
- Plans are priced per user, per device, per location or flat; compare inclusion lists before totals, and separate one-time from monthly.
- The first 90 days should end with MFA, EDR, a tested backup, segmentation, logging, a rehearsed incident plan and an insurance side-by-side.
In this guide
- What should a dental cybersecurity provider do for your practice?
- What should a managed security plan for a dental practice include?
- How do you find the most experienced cybersecurity partner for a dental service organization?
- What are the red flags when comparing dental cybersecurity providers?
- How are managed cybersecurity plans for dental offices priced?
- What to ask your IT provider before you sign a security plan
- What to verify before you sign
- The IT side: how a security plan sits on a dental network
- How does the plan line up with HIPAA, CISA and your cyber insurance?
- What should the first 90 days with a new security provider look like?
- How Legend Networking can help
- Frequently asked questions
- The bottom line
What should a dental cybersecurity provider do for your practice?
A dental cybersecurity provider takes ownership of a defined set of protective controls on your network, operates them every day, proves they work with reports and tests, and leads the response when something gets through. That is different from selling tools. A provider you can hold to account names the controls, the evidence and the person responsible in the contract.
Most dental offices choose between five kinds of provider. The table is the first filter; the sections below give you the questions for whichever kind you shortlist.
| Kind of provider | Best for | What you usually get | Where it falls short |
|---|---|---|---|
| General IT company that also "does security" | An office that wants one vendor and has a simple network | Antivirus, patching, backups, a firewall; security as part of a support plan | Rarely knows imaging devices or the practice management server; security is often a product list, not a plan |
| Dental-focused IT company with a managed security plan | One to several locations running Dentrix, Eaglesoft, Open Dental or similar | Support and the twelve controls from one team that knows the clinical day | Only as good as the plan's inclusion list; ask for the evidence, not the brochure |
| Security-only firm (managed security service provider) | Groups with an IT team or IT provider already in place | Monitoring, detection, response and reporting across many clients | Needs a hand-off with whoever runs your network; two vendors can point at each other during an incident |
| Security bundle from a software or imaging vendor | Offices that want the vendor's own stack covered | Protection around the vendor's product | Does not cover the rest of the network, the front desk email or the staff accounts |
| In-house or do-it-yourself | A group large enough to employ its own technician | Control and speed on site | Nobody watching after hours; one person holds every password; no outside test of the work |
Should you hire a separate security firm or one dental IT provider?
For a single office whose IT company already runs the network, one provider with a written security plan is usually the better choice; a separate security firm fits a group with its own IT lead who can manage two vendors and settle disputes between them. Three questions decide which side of that line you are on.
First, who runs the network today? If one company already manages your server, workstations and firewall, adding a security-only firm creates a seam, and incidents live in seams; ask that company for a written security plan first and judge it against the twelve controls. Second, does anyone on your side own security? A group with an IT lead can run a security firm beside its IT provider and arbitrate between them; a single office usually cannot. Third, how much of the risk is clinical? Imaging devices, sensors and the practice management database are where dental networks differ from offices, and the provider who protects them must understand them. When one provider covers both support and security, make sure the proposal reads as managed IT services for dental practices with the security controls listed line by line, not as support with "security included".
If you are choosing an IT company as a whole, not only its security plan, our guide on how to choose a dental IT company covers response, contracts and references. This guide stays on the security plan itself.
What should a managed security plan for a dental practice include?
A managed security plan for a dental practice should include twelve controls: endpoint detection and response, multifactor authentication, patching, email security, backups with an immutable copy, DNS filtering, network segmentation with secured remote access, logging and alert review, security awareness training, vendor and business associate management, incident response, and alignment with your cyber-insurance application. Each needs an owner and evidence.
The table defines what "included" has to mean. A proposal that lists a control by name without the right-hand column is a product list, and you should ask for the missing evidence before you compare prices.
| # | Control | "Included" means | Evidence to ask for |
|---|---|---|---|
| 1 | Endpoint detection and response (EDR) | An EDR agent on every workstation and server, with a person or team reviewing its alerts, not antivirus alone | The console's device list against your own inventory; who reviews alerts and when |
| 2 | Multifactor authentication (MFA) | MFA on email, remote access, the practice management cloud or portal, administrative accounts and payer portals; one account per person | A report of accounts without MFA; a list of shared logins still in use |
| 3 | Patching | Operating system and application updates on a schedule, with tested rollouts for the practice software and imaging bridges, and a report of what is behind | The monthly patch report; how an update that breaks imaging is held back |
| 4 | Email security | Filtering in front of the mailbox, link and attachment checks, sender authentication records for your domain, and a reporting path for staff | Your domain's SPF, DKIM and DMARC status; the quarantine report |
| 5 | Backups with an immutable copy | Automatic backups of the server and practice database, one copy that cannot be altered or deleted from the network, and a restore test on a schedule | The date and duration of the last full restore test, with the file list restored |
| 6 | DNS filtering | Blocking of known malicious and newly registered domains on every device, including laptops off site | The block report for the last month |
| 7 | Network segmentation and secured remote access | Imaging devices, guest Wi-Fi, phones and workstations on separate network segments; every remote door inventoried and behind MFA | A network diagram with segments; the remote-access register |
| 8 | Logging and alert review | Logs collected from the firewall, servers, email and EDR, kept long enough to investigate, and reviewed by a named person or service | What is logged, where it is kept, for how long, and who reads it |
| 9 | Security awareness training | Short, recurring training for every person, including doctors, with simulated phishing and results | The completion report by person; the last simulation's click rate |
| 10 | Vendor and business associate management | A list of every vendor that reaches patient data or your network, with a signed agreement and a note of how its access is secured | The vendor list; the provider's own signed business associate agreement with you |
| 11 | Incident response | A written plan naming who is called, in what order, and who decides to take systems down, with a tabletop exercise | The plan; the date of the last exercise |
| 12 | Cyber-insurance alignment | The controls your application attests to are in place and evidenced before you sign the form | A side-by-side of the application's questions and the evidence |
Identity and endpoints: controls 1 to 3
Start where attackers start: with credentials and unpatched software. CISA's performance goals report notes that "the absence of basic protections such as multifactor authentication (MFA), strong password management, and maintaining backups, among other foundational measures, repeatedly exposes critical infrastructure to damaging cyber intrusions." In a dental office that means one account per person, MFA on anything reachable from the internet, and an EDR agent on every machine that touches the practice software. Our comparison of EDR vs antivirus for dental offices explains the difference and the tool prices; our guide to password management for dental offices covers the policy and the tools.
Email, web and backups: controls 4 to 6
The front desk opens attachments from patients, labs, suppliers and insurers all day, so email filtering has to be tuned to that work rather than fight it, and the practice domain needs its sender records set so that spoofed messages fail. DNS filtering stops a clicked link from reaching a known bad site. Backups are the control that decides whether a ransomware day ends in a restore or a ransom: the HIPAA Security Rule's data backup plan asks a practice to "establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information", and a provider should prove the "retrievable" part with a dated restore test. The detail is in our guide to dental data backup.
Network, visibility and response: controls 7, 8 and 11
Sensors, panoramic units and CBCT machines often run operating systems the manufacturer controls, so they are segmented rather than patched. Every remote door, including the vendor's support tool and the doctor's home connection, belongs on a register behind MFA; our article on dental remote access security shows how to build that register. Logging is the control most proposals skip: CISA's event logging publication of 21 August 2024 "defines a baseline for event logging best practices to mitigate cyber threats", and the Security Rule's audit controls standard asks for mechanisms that "record and examine activity in information systems that contain or use electronic protected health information". Without logs, the incident response plan has nothing to work from. Our dental ransomware recovery playbook shows what the first hours look like when the plan exists.
People, vendors and insurance: controls 9, 10 and 12
The Security Rule's administrative safeguards include a standard for "a security awareness and training program for all members of its workforce (including management)". The vendor control is the one a provider is least keen to discuss because it includes the provider. Every company that creates, receives, maintains or transmits patient data on your behalf needs a business associate agreement, and under 45 CFR 164.314 that agreement must require the business associate to "report to the covered entity any security incident of which it becomes aware". Ask how the provider's own remote tools and administrator accounts are secured, and who at the provider can reach your server. Control 12 closes the loop: the attestations on your insurance application must be true and evidenced before you sign. Our guide to dental cyber insurance requirements lists the evidence file carriers commonly ask for.
Two of these controls connect to pages of their own in this series: network security for dental practices covers the firewall, Wi-Fi and segmentation design, and a dental disaster recovery plan covers recovery time and recovery point targets.
How do you find the most experienced cybersecurity partner for a dental service organization?
Judge a provider's experience with dental service organizations by evidence of multi-site work: identity run from one directory across every office, one firewall and segmentation standard at each location, acquired practices brought onto the standard on a dated plan, logging and reporting per location, and a written process for vendor access. Ask to see each, not to hear about it.
A group has every risk a single office has, multiplied by the number of locations, plus three of its own: inconsistency between offices, inherited systems from acquisitions, and shared logins that make it easier to run the group. The table separates what a single office should ask from what a group must add.
| Question | Single office | Dental service organization |
|---|---|---|
| Who holds the accounts? | One account per person, MFA everywhere it is offered | One directory for the group, roles by job, access removed the day someone leaves any office |
| What is the standard? | The twelve controls, evidenced | The same twelve controls at every location, with a written standard and an exception list |
| What happens with a new office? | Not applicable | A dated onboarding plan for an acquired or de novo office, with a security baseline before it joins the group network |
| How are payer and vendor portals handled? | Per-person logins where the portal allows | A policy for shared logins, who reviews them, and a path to individual access; see our article on shared payer portal logins and MFA in dental groups |
| How is the plan reported? | One monthly report | A report per location and a roll-up for leadership, with the exceptions named |
| Who runs it? | The provider | The provider, your IT lead, or both under a written split of duties; see co-managed IT for dental groups |
Ask also how the provider treats a location that was breached before you bought it, how acquisition due diligence feeds the security plan, and how it reports to a board or private-equity owner. Our pages on DSO IT support and dental practice acquisition IT due diligence go further on the group view.
What are the red flags when comparing dental cybersecurity providers?
The red flags are the same whoever is selling: a plan described by product names instead of controls and evidence, no business associate agreement offered, no monthly report, a refusal to show a restore test, nobody named for after-hours alerts, promises about outcomes that no one can keep, and a proposal that never mentions your practice software or imaging equipment.
| What you hear | Why it matters | What to ask instead |
|---|---|---|
| "We include antivirus" | Antivirus alone does not detect an intruder using stolen credentials | Which EDR product, on which devices, and who reviews its alerts? |
| "Your data is backed up to the cloud" | A cloud copy that the server can overwrite is also a copy ransomware can encrypt | When was the last full restore test, and is one copy immutable? |
| "We monitor your network" | Monitoring without logging and a named reviewer is an alert nobody reads | What is logged, how long is it kept, and who reads it overnight? |
| "You will be fully compliant" | No product or provider can make a practice compliant; the practice documents its own risk analysis and safeguards | Which Security Rule safeguards does the plan cover, and which stay with us? |
| No business associate agreement in the proposal | The provider reaches patient data and must sign one | Send your agreement, and show how your own administrator access is secured |
| No mention of Dentrix, Eaglesoft, Open Dental, DEXIS or your sensors | Patching and segmentation that ignore the clinical stack break the clinical day | Which practice management and imaging systems do you support today? |
| A price with no inclusion list | You cannot compare two plans without knowing what each covers | Send the inclusion list for the twelve controls with the evidence for each |
| "Set up fee includes everything" | Firewalls, licences and a server rebuild are usually separate | What is one-time, what is monthly, and what is quoted separately? |
Red flags are not verdicts. A provider that answers the right-hand column well may simply have a weak brochure.
How are managed cybersecurity plans for dental offices priced?
Managed cybersecurity plans for dental offices are priced per user, per device, per location or as a flat monthly plan, with the tools' own licences passed through or bundled, and one-time projects such as a firewall replacement or server rebuild quoted separately. Published prices are rare, so compare inclusion lists before you compare totals, and ask what moves the number.
| Pricing model | How it is billed | Fits | Watch for |
|---|---|---|---|
| Per user | A monthly fee for each person with an account | Offices where staff outnumber devices | Doctors who work at two offices counted twice |
| Per device | A monthly fee for each workstation, server and laptop | Offices with shared operatory computers | Servers priced far above workstations; imaging PCs forgotten |
| Per location | A flat fee per office | Groups that want a predictable line per site | What a "location" includes when one office has twice the chairs |
| Flat monthly plan | One number for the whole practice | Single offices that want simplicity | The inclusion list; what happens when you add a chair or a hygienist |
| Tools separate from management | Licences at list price plus a fee for running them | Groups comparing tool costs | Two invoices, two renewals, and who owns the licences if you leave |
Tool licences give you a floor. On 18 November 2026 Microsoft listed Defender for Business, which includes endpoint detection and response, at $3.00 per user per month, paid yearly; the work of running it, reviewing its alerts and responding is what a provider adds, and that is where plans differ. What moves the price: the number of users and devices, the number of locations, whether a server or a cloud practice system sits at the centre, how much on-site work the plan includes, whether logging and after-hours alert review are in or out, and how much of the backup storage and retention you choose. Hardware, major cabling projects and software licensing are usually quoted separately, so ask for the one-time and monthly columns on the same page. For the wider support budget, see our dental IT support cost guide.
What to ask your IT provider before you sign a security plan
About the plan
- Which of the twelve controls are included, which are optional, and which stay with us?
- Who is the named person responsible for the plan, and who covers when they are away?
- What will the monthly report show, and can we see one from an existing client with the name removed?
About our systems
- Which practice management and imaging systems do you support today, and how do you patch around them?
- How are our sensors, panoramic unit and CBCT separated from the rest of the network?
- Which remote-access tools do you use to reach our server, and how are your own administrator accounts protected?
About incidents
- Who reviews alerts outside office hours, and what happens when one is serious?
- When did you last run a full restore of a client's practice database, and how long did it take?
- Will you sign our business associate agreement, and how do you report a security incident to us?
About money and exit
- What is one-time, what is monthly, and what is quoted separately?
- If we leave, who owns the licences, the backups and the documentation, and how do we get them?
What to verify before you sign
Demos look alike. These checks separate a plan from a product list, and each is something you can request in writing before you commit.
- The inclusion list. Every one of the twelve controls marked included, optional or excluded, with the evidence named.
- A sample report. A real monthly report from another client with the name removed, showing devices, patch status, backup results and alerts handled.
- A restore test. The date, scope and duration of the last full restore the provider ran for a client of your size.
- The device list. How the provider will reconcile its agent count against your inventory in the first month.
- The business associate agreement. Signed by the provider, with incident reporting to you in writing.
- Named systems. Your practice management software and imaging systems named in the proposal, with how updates are tested before they reach you.
- Insurance alignment. A side-by-side of your current application's questions and the evidence the plan produces.
- After-hours ownership. Who sees an alert at night and what they are allowed to do without calling you.
- Exit terms. Ownership of licences, backups, passwords and documentation, and the hand-over period if you change providers; our guide to switching dental IT providers without downtime lists what to secure.
- References from dental offices. Two practices on your software, with permission to call them.
The IT side: how a security plan sits on a dental network
A dental network is harder to secure than an ordinary office network because of three things. Imaging hardware from DEXIS, Carestream, Planmeca and Vatech often runs embedded systems the manufacturer controls, so the control is segmentation rather than patching, and the segmentation has to let the sensor reach the imaging server and nothing else. The practice management server, whether it runs Dentrix, Eaglesoft or Open Dental, concentrates the schedule, charts, imaging links and billing in one place, so backups, EDR and access control on that one machine matter more than anywhere else. And the people at the chair share workstations and move between rooms all day, so per-person accounts need fast user switching or a sign-in method that does not slow the operatory.
A provider who knows this will ask about your imaging bridges before quoting a patching schedule, will put the practice database restore at the centre of the backup test, and will treat every vendor's remote-support tool as a door to be inventoried. Those are the signs of dental experience you can check in the first conversation. If the office also needs day-to-day help, the same team should be able to show how its security plan and its dental IT support work from one ticket queue, so that a slow workstation and a blocked attachment are not two phone calls. The practice side of the same picture is our dental office cybersecurity checklist, which you can score before any provider visits, and our dental cybersecurity services page describes how Legend lays these layers onto a dental network.
How does the plan line up with HIPAA, CISA and your cyber insurance?
The twelve controls map onto three things a practice is measured against: the HIPAA Security Rule's safeguards, CISA's voluntary performance goals for small and medium organizations, and the questions on a cyber-insurance application. A provider does not make you compliant or insured; it operates and evidences controls that let you document your own compliance and answer the application truthfully.
The Security Rule starts with a risk analysis: "conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information". It asks for security incident procedures, a contingency plan with a data backup plan, workforce training, access controls, audit controls and person or entity authentication, and it lists encryption as "addressable", a term 45 CFR 164.306 defines: the practice implements the specification "if reasonable and appropriate", or documents why it would not be and implements "an equivalent alternative measure if reasonable and appropriate". Documentation must be kept "for 6 years from the date of its creation or the date when it last was in effect, whichever is later". On 6 January 2025 HHS published a proposed rule to modify the Security Rule; it was still a proposal when this guide was written, so check its status before relying on it. This guide describes safeguards and does not interpret the rule for your practice; our HIPAA compliance checklist for dental offices covers the documentation side.
CISA describes its Cross-Sector Cybersecurity Performance Goals as "a common set of protections that all critical infrastructure entities - from large to small - should implement to meaningfully reduce the likelihood and impact of known risks and adversary techniques", and says they are meant to "help small- and medium-sized organizations kickstart their cybersecurity efforts". HHS's 405(d) program publishes the HICP practices for healthcare and voluntary Healthcare and Public Health performance goals it describes as "aligned with HICP and CISA". Our checklist article maps each item to those documents. For context on why healthcare is on the list: the FBI's Internet Crime Complaint Center received "more than 3,600 complaints reporting ransomware, with losses exceeding $32 million" in 2025, and names Healthcare and Public Health among the critical sectors most affected by the top ten reported variants; the FBI notes its loss figure "does not normally include estimates of lost business, time, wages, files, or equipment, or any third-party remediation services acquired by an entity".
Insurance applications commonly ask about MFA, endpoint protection, backups, patching, training and an incident plan. The California Dental Association's 2025 toolkit for members includes a guide on choosing "a cybersecurity-savvy IT provider" and a vendor-risk checklist, and its regulatory compliance analyst put the buyer's job plainly: "ask smart questions, set clear expectations and choose vendors that take your patients' data as seriously as you do."
What should the first 90 days with a new security provider look like?
The first 90 days should move from inventory to evidence: an inventory of devices, accounts, vendors and remote doors in the first two weeks, the high-impact controls (MFA, EDR, backups with a restore test) by day 30, segmentation, logging and training by day 60, and the first full monthly report, tabletop exercise and insurance side-by-side by day 90.
| Period | What the provider does | What you should receive |
|---|---|---|
| Days 1 to 14 | Discovery: device and account inventory, vendor and remote-access register, network map, backup check, risk analysis started | The inventory reconciled against your own list; a gap list against the twelve controls |
| Days 15 to 30 | MFA on email, remote access and administrative accounts; EDR on every device; backup repaired and a first restore test | The MFA exception list; the EDR device count; the restore test record |
| Days 31 to 60 | Segmentation of imaging and guest networks; DNS filtering; email sender records; logging switched on; first training session | A network diagram; the quarantine and block reports; training completion by person |
| Days 61 to 90 | Incident response plan written and exercised; vendor agreements collected; insurance application reviewed against evidence | The plan; the tabletop notes; the first full monthly report; the insurance side-by-side |
If you are moving from one provider to another, the hand-over runs beside this plan, and the old provider's access should be removed only after the new controls are verified. Day 90 is also the point to score the provider against the "verify before you sign" list: everything promised should now exist as a document or a report.
How Legend Networking can help
Legend Networking is a Dallas-based dental IT company with 22+ years in dental IT that has served over 3,500 practices since 2004. Legend provides 24/7 monitoring from in-house engineers, with no outsourced first-level triage; onsite dispatch is by appointment across served dental markets, and service is remote-first nationwide. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, which is where most of the segmentation and patching questions in this guide live.
The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. For the shape of the first 90 days described above, see a managed IT onboarding for a Texas practice that covered network and server review, security, backups, software and user access. If you are comparing several companies at once, our list of the best dental IT companies sets out what each publishes, and Legend's city and state pages list the cities and states Legend works in.
Frequently asked questions
What does a dental cybersecurity provider do?
A dental cybersecurity provider operates a defined set of protective controls on a practice's network, such as endpoint detection and response, multifactor authentication, patching, email filtering, backups and logging, proves they work with reports and tests, and leads the response to an incident. It should also understand the practice management server and imaging devices that make a dental network different.
How do I choose a cybersecurity company for a dental practice?
Hold every proposal against the same list: the twelve controls, written evidence for each, named experience with your practice management and imaging systems, a signed business associate agreement, a sample monthly report and clear exit terms. Ask the same questions of each company, insist on answers in writing, and compare inclusion lists before you compare prices.
What is the best cybersecurity firm for a small dental practice?
There is no single best firm; the right one for a small practice names your practice software and imaging systems, includes the twelve controls with evidence, signs a business associate agreement, reports monthly and prices the plan with an inclusion list. Our list of the best dental IT companies shows what the main dental IT companies publish, so you can shortlist and then run this guide's questions.
Do I need a separate security firm if I already have a dental IT company?
Usually not, if your IT company can show a written security plan that covers the twelve controls with evidence and a named person reviewing alerts. A separate security firm makes sense for a group with its own IT lead who can manage two vendors. For a single office, two vendors create a seam, and incidents tend to fall into seams.
What should managed security for a dental office include?
Managed security for a dental office should include endpoint detection and response on every device, multifactor authentication, scheduled patching tested against the practice software, email security, backups with an immutable copy and restore tests, DNS filtering, network segmentation with secured remote access, logging with alert review, staff training, vendor and business associate management, an incident response plan and alignment with the cyber-insurance application.
Who is the most experienced cybersecurity partner for dental service organizations?
Experience with dental service organizations is shown, not claimed: one directory for identity across every office, a single segmentation and firewall standard per location, acquired offices brought to the standard on a dated plan, reporting per location with a roll-up, and a written process for vendor and portal access across the group. Ask any candidate to show each of these for a current group client.
How much does dental cybersecurity cost per month?
Plans are priced per user, per device, per location or as a flat monthly fee, with tool licences bundled or passed through and one-time projects quoted separately. Published figures are rare; Microsoft, for example, listed Defender for Business at $3.00 per user per month on 18 November 2026, and the managed service is priced on top. Compare inclusion lists before comparing totals.
What questions should I ask a dental cybersecurity provider?
Ask which of the twelve controls are included, who is named as responsible, what the monthly report shows, which practice management and imaging systems the provider supports, how its own remote tools and administrator accounts are protected, who reviews alerts after hours, when it last ran a full restore, whether it will sign a business associate agreement, and who owns the licences and backups if you leave.
Is a cybersecurity provider a HIPAA business associate?
HIPAA's definitions at 45 CFR 160.103 make a business associate of a person who, on a covered entity's behalf, "creates, receives, maintains, or transmits protected health information"; a provider with remote access to your server fits that description, and the practice needs a signed agreement with it. Under 45 CFR 164.314 that agreement must require the provider to report security incidents it becomes aware of to the practice.
What do IT security services for dentists usually leave out?
The gaps most often found in proposals are logging with a named reviewer, an immutable backup copy with a dated restore test, segmentation of imaging devices, an inventory of vendor remote-access tools, a tabletop exercise for the incident plan, and the provider's own business associate agreement. Each is on the twelve-control list in this guide, so ask for it by name.
The bottom line
Before you sign any of the three proposals, get a written picture of what is running today. Ask for a Free Dental IT Assessment: a review of your computers, software, network security, backups and performance, with written findings and prioritized recommendations, then score each proposal against the twelve controls. If you want to talk through the findings with a team that works on dental networks every day, ask our dental cybersecurity services team for a consultation, and bring the questions above; the same team handles dental IT support when the plan needs a hand on the keyboard.

