Skip to main content
Security · CYBERSECURITY

Network Security for Dental Practices: The 8 Layers and Who Owns Each

An imaging technician plugs a laptop into the wall port beside the panoramic unit, works for an hour and leaves, and nobody in the office can say what that port connects to. The waiting-room TV, the patient tablets and the server share one Wi-Fi password on a sticky note. And when a payer's questionnaire asks about the firewall, guest Wi-Fi and remote access, nobody knows which of those the "network security" line on the IT invoice covers.

This guide walks the eight layers in the order an engineer would check them in an existing office, with what each layer does, what you can look for yourself, and who normally owns it. It then maps each layer to the words of the HIPAA Security Rule as published, gives you a self-audit you can finish in one visit to the server closet, separates what a managed network security plan covers from what the practice still owns, and ends with the questions to put to your IT provider. Regulation text is quoted from the Cornell Legal Information Institute and vendor pages were read on 18 November 2026; this guide quotes the rule and does not interpret it.

In this guide
  1. What does network security for a dental practice actually cover?
  2. The eight layers at a glance
  3. Layer 1: does a dental office need a business firewall, and what makes it "business grade"?
  4. Layer 2: how should a dental office network be segmented?
  5. Layer 3: what Wi-Fi standards should a dental office use, and should patients share it?
  6. Layer 4: how should remote access into a dental network work?
  7. Layer 5: what is DNS filtering and why does a small practice need it?
  8. Layer 6: why do switches and wall ports matter for dental network security?
  9. Layer 7: what should be monitored and how long should logs be kept?
  10. Layer 8: which devices on the network are the risk, and what should run on them?
  11. How do the eight layers map to the HIPAA Security Rule text?
  12. What does a managed network security plan cover, and what does the practice still own?
  13. Dental office network security self-audit: the one-visit checklist
  14. The IT side: what your provider should be doing that you never see
  15. What to ask your IT provider about network security
  16. How Legend Networking can help
  17. Frequently asked questions
  18. The bottom line

What does network security for a dental practice actually cover?

Network security covers everything between the internet and the computer in the operatory: the firewall at the edge, how the network is divided, how Wi-Fi is secured, how anyone connects from outside, which web addresses devices may reach, the switches and ports in the walls, the records kept, and the devices themselves. Endpoint tools and backups sit beside it.

The reason it matters more in a dental office than in a typical small business is the mix of devices on one network. A law office has laptops and a printer. A dental office has a practice management server, imaging workstations, sensors, a panoramic or CBCT unit with its own computer, intraoral scanners on Wi-Fi, a phone system, patient entertainment screens, cameras, a door controller and the patients' own phones. Most of those cannot run security software, and several are maintained by vendors who want remote access. A flat network puts every one of them one step away from the patient database.

Flat network (one segment, one Wi-Fi)Segmented network (several segments, separate Wi-Fi)
What a patient's phone can reachthe server, every workstation, the imaging computersthe internet only
What a compromised TV or camera can reacheverythingits own segment
Vendor laptop plugged into a wall portfull accessa port that is either disabled or on the right segment
Firewall rules possibleallow or block the whole officeper segment: imaging may not reach the guest network, guests may not reach anything inside
Evidence you can show an insurerone Wi-Fi passworda network diagram, segment list and firewall rule set
Who usually has itoffices whose network grew one device at a timeoffices whose network was designed, or redesigned, as a dental network

If the right-hand column reads like another office, the rest of this guide is the path from left to right. If your practice is still being built, the cabling, drops, closet and segment plan belong in our guide to dental office network setup; this page is about securing the network you already have.

The eight layers at a glance

#LayerWhat it doesWhat you can look forWho normally owns it
1Business firewalldecides what traffic may enter or leave, and inspects ita labelled business unit, not the carrier's modem alone; a current subscription dateIT provider (practice approves rule changes)
2Segmentationsplits the network so devices only reach what they needseparate names for staff, guest and device Wi-Fi; a segment listIT provider (practice supplies the device list)
3Wi-Fi standardsencrypts wireless traffic and controls who joinsWPA3 or WPA2 with a long passphrase; no sticky-note password for the clinical networkIT provider (practice owns the visitor rule)
4Remote accessone controlled door for staff and vendorsa list of who can connect, each with a named account and MFAIT provider (practice approves each vendor)
5DNS filteringstops devices resolving known-bad or off-policy web addressesa filtering report; blocked-category listIT provider
6Switches and portsthe physical sockets every device plugs intono unmanaged switches under desks; unused wall ports disabledIT provider (practice reports new devices)
7Monitoring and logsrecords what happened and who lookeda log retention period and a named reviewerIT provider (practice reads the monthly report)
8Devices on the networkthe computers and equipment the network carriesnothing on an operating system past its end-of-support date; EDR on every workstationshared

Read across each row once; the sections below give every layer its own test.

Layer 1: does a dental office need a business firewall, and what makes it "business grade"?

Yes. A business firewall, often sold as a next-generation firewall, is a separate device that inspects traffic rather than just passing it, applies rules per segment, and carries paid subscriptions for intrusion prevention, web filtering and threat updates. The modem or router your internet carrier supplied does none of that, even when it has a setting called "firewall".

Three things separate a working business firewall from a box with the right name on it.

The subscriptions are active. Most business firewalls ship with the inspection services (intrusion prevention, anti-malware scanning, web and application control) as annual subscriptions. When the subscription lapses, the hardware keeps routing traffic and stops inspecting it. The office notices nothing. Ask for the renewal date in writing and put it on the same calendar as the practice software renewal.

The rules are written for a dental office. A default rule set allows everything outbound and blocks everything inbound. That is better than nothing, but it does not stop a compromised imaging computer from sending files out, and it does not keep the guest network away from the server. A dental rule set names the segments (next layer) and says what each may reach.

Somebody changes it on purpose. Every "can you just open a port so the vendor can get in" request is a firewall change. Over five years, an office that never reviews its rules ends up with a dozen holes, each opened for a vendor who may no longer exist. The owner of this layer is your IT provider, but the approver of each change should be a named person in the practice, and the list of open exceptions should come to you once a quarter.

The monthly line some owners resent as a "firewall rental" is often this layer: the hardware, its subscriptions and the person who manages the rules. The test of whether it is worth paying for is not the brand; it is whether you can get the three items above in writing.

Layer 2: how should a dental office network be segmented?

Segmentation splits one network into several that cannot see each other unless a firewall rule allows it. A small dental office needs about five segments: clinical (server, workstations, printers), imaging (sensors, panoramic or CBCT computers, scanners), voice (phones), devices (cameras, TVs, door controls, thermostats) and guest Wi-Fi. Patients and visitors never touch the first four.

SegmentWhat belongs in itMay reachMust not reach
Clinicalpractice management server, front-desk and operatory workstations, printers, label printersimaging (for image bridges), the internet through the firewallguest, devices
Imagingsensors' host computers, panoramic or CBCT acquisition PC, intraoral scanner, imaging server if separateclinical (image storage and bridges), vendor remote access when approvedguest, devices, voice
Voicedesk phones, phone system controller or gatewayits phone provider, the internetclinical, imaging
Devicescameras, patient entertainment screens, smart TVs, door controllers, thermostats, music playersthe internet, and only the services they needclinical, imaging
Guestpatients' and visitors' phones and tablets, reps' laptopsthe interneteverything inside

Two practical points matter more than the diagram.

Devices that cannot run security software belong in their own segment. A smart TV, a camera or a door controller cannot run EDR, is rarely patched, and often carries a vendor account you have never changed. In the devices segment, a compromised TV reaches the internet and nothing else. On a flat network it reaches the server.

Segments are only real if the firewall enforces them. A guest Wi-Fi name that is a separate word but the same network is cosmetic. The test is simple and your provider can run it in a minute: from a phone on the guest network, try to open the server's address or ping a workstation. If anything answers, the segments are names, not boundaries.

Intraoral scanners are the usual argument. Their vendors often ask for the scanner and the acquisition computer to be on one network with few restrictions. The answer is to put both in the imaging segment with a rule to the clinical segment for the image bridge, not to flatten the whole office for one device.

Layer 3: what Wi-Fi standards should a dental office use, and should patients share it?

The clinical network should run WPA3, or WPA2 with a long passphrase that is not shared with visitors, and the guest network should be a separate wireless network with a separate password that changes regularly. Patients should never be on the same wireless network as the practice software, whatever the access point's marketing says about isolation.

The Wi-Fi Alliance, the industry body that tests wireless equipment against its standards, states on its security page that "WPA3 is mandatory for Wi-Fi CERTIFIED devices" (read on 18 November 2026). Current access points therefore support WPA3; older intraoral scanners and tablets sometimes do not, which is why many offices run the clinical network in a WPA2/WPA3 mixed mode. That is a reasonable setting as long as the passphrase is long, is not written on the wall, and is changed when staff leave.

Wi-Fi settingClinical networkGuest network
Security standardWPA3, or WPA2/WPA3 mixed for older imaging devicesWPA2 or WPA3 with a simple visitor password, or an open network with a captive page, on its own segment
Who knows the passwordthe IT provider and one named person in the practiceprinted at the front desk; changed on a schedule
Devices allowedpractice-owned workstations, tablets and imaging devicesanything the visitor brings
What it can reachthe clinical and imaging segments per the firewall rulesthe internet only
Hidden network nameoptional; hiding the name is not a security controlno
Bandwidthpriority for imaging and the practice softwarecapped so the waiting room cannot slow the operatories

Three myths come up in nearly every office. Hiding the network name does not secure it; the name is still broadcast whenever a device connects. A MAC-address allow-list is a convenience, not a lock, because addresses are visible and easy to copy. And "the access point has client isolation" is not segmentation; it stops guest devices seeing each other, not seeing your server, unless the guest network is also a separate segment at the firewall.

If the office's wireless problem is reliability rather than security, the causes and the fixes are a different list, covered in our guide on when dental office Wi-Fi keeps dropping.

Layer 4: how should remote access into a dental network work?

All remote access should pass through one controlled door: a VPN or a remote-access gateway managed by your IT provider, with a named account for every person and vendor, multifactor sign-in on every connection and a log of each session. No remote desktop port should face the internet, and no vendor tool should run unattended without written approval.

This is the layer most often opened "temporarily" and then forgotten. Imaging vendors, the practice software company, the phone provider, the payroll firm and a former IT provider may each have left a way in. The practice's job here is small and important: keep a list of every outside party allowed to connect, the method they use and who approved it, and review it twice a year. The same named-account rule applies to the web portals staff share, covered in our guide to shared payer portal logins. Your IT provider's job is to make every entry on that list go through the same door with the same controls.

The detail, including the verdict on RDP, a register for every remote door, and safe patterns for staff working from home, is in our guide to remote access security for dental offices. The point for this page is that remote access is a network layer with an owner, not a favour done over the phone.

Layer 5: what is DNS filtering and why does a small practice need it?

DNS filtering checks every web address a device tries to reach against lists of known malicious, newly registered or off-policy domains and refuses the bad ones before a connection is made. It protects every device on the network, including the ones that cannot run security software, and it backs up the firewall and endpoint tools at low cost.

DNS is the lookup that turns a name such as a website address into the numbers computers actually connect to. Because every connection starts with that lookup, filtering it is an efficient control: a phishing link in an email, a malicious advert on a news site, or a smart TV calling home to an address on a threat list are all stopped at the same point. It also gives you a report. If a workstation tries to reach a known command-and-control domain at two in the morning, the filtering log is often the first place that shows it.

Two things to ask for. First, that filtering is applied at the firewall or on the network, so guest and device segments are covered, and also as an agent on laptops that leave the building. Second, a copy of the blocked-category list, so the practice decides whether, say, personal webmail or streaming is blocked on clinical workstations. That is a practice policy decision, and your provider should not be making it for you by default.

Layer 6: why do switches and wall ports matter for dental network security?

Switches are the boxes every wired device plugs into, and wall ports are the sockets that lead to them. Security fails here when an unmanaged five-port switch appears under a desk, when a live wall port in the waiting room is open to anyone with a cable, or when nobody can say which port belongs to which segment.

Walk the office once with this list.

    • Unmanaged switches. A small plastic switch under a desk or behind the panoramic unit, added because someone needed one more port, cannot be seen or controlled by your provider and often bridges two segments. Each one should be replaced by proper ports or by a managed switch your provider can see.
    • Live unused ports. Every wall port that is patched through and not in use is a door. Ask that unused ports be disabled at the switch, and that the vendor who plugs a laptop into the wall by the CBCT gets a port in the imaging segment, not whatever that socket happened to be.
    • Labels. Each port in the closet should carry a label that matches a label on the wall plate, and the switch configuration should say which segment the port is on. If your provider cannot produce that map, nobody can answer "what is plugged in where" on the day it matters.
    • Power over Ethernet budget. Phones, cameras and access points draw power from the switch. A switch running at the edge of its power budget drops devices at random, which looks like a Wi-Fi fault and is often blamed on one.
    • Physical access. The network closet should lock, and the switches should not be in the staff break room or under the front desk where a visitor can reach the cables.

For a new build, the number of drops per room, cable category and closet design are specified in our dental office network setup guide; for an existing office, the question is simply whether the switches you have are managed, labelled and locked away.

Layer 7: what should be monitored and how long should logs be kept?

At minimum, the firewall, the remote-access gateway, the DNS filter and the server's sign-in records should be collected centrally, kept for a period the practice has written down, and reviewed by a named person on a known schedule. Monitoring without retention cannot answer "what happened last month"; retention without a reviewer is evidence nobody reads.

Three questions make this layer concrete.

What is collected? Firewall allow and deny events, VPN or gateway sessions with the account name, DNS filter blocks, failed and successful sign-ins to the server and the practice software, and alerts from the endpoint tools. Ask for the list.

How long is it kept? The right period is a decision for your risk analysis and your compliance adviser, not for this page, but it should be a written number, and the practice should know where the records live and how to get them if a lawyer or an insurer asks.

Who reads it, and what do you see? "Monitored" means a person or a system reacts to events, and the practice sees a summary. A monthly report that lists blocked threats, remote sessions by vendor, firewall rule changes and devices that joined the network is the plainest evidence that this layer exists. If you have never seen such a report, ask for last month's.

Layer 8: which devices on the network are the risk, and what should run on them?

The devices that need attention are the ones nobody counts: the acquisition computer bundled with an imaging unit years ago, the spare workstation in the consult room, and anything on an operating system past its end-of-support date. Every workstation and server should carry endpoint detection and response (EDR), and nothing unsupported belongs on the clinical or imaging segment.

Microsoft's lifecycle page states that "Windows 10 will reach end of support on October 14, 2025" (read on 18 November 2026), a date now more than a year past. Imaging computers are the most common survivors, because the imaging vendor supported its software on that version and the unit still works. A computer that no longer receives security updates is a permanent weakness on whichever segment it sits in. Where it cannot be replaced yet, the smaller step is to move it into a segment with the tightest rules, remove its internet access except to the vendor's update address, and record the exception with a date.

What runs on each device is the endpoint layer, which sits beside network security rather than inside it. The difference between the antivirus you already pay for and EDR, what the Security Rule text actually names, and how exclusions for practice software are set up are covered in our comparison of EDR vs antivirus for dental offices.

How do the eight layers map to the HIPAA Security Rule text?

The Security Rule does not name firewalls, segments, Wi-Fi standards or DNS filters. It sets standards and implementation specifications for electronic protected health information, and each network layer serves one or more of them. The table quotes the published text of 45 CFR 164.312 and 164.308 from the Cornell Legal Information Institute, read on 18 November 2026, without interpretation.

LayerStandard or specification (quoted)Text as published
1 Firewall · 5 DNS filtering164.312(e)(1) 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."
2 Segmentation · 6 Switches and ports164.312(a)(1) Access control"Implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights as specified in § 164.308(a)(4)."
3 Wi-Fi standards164.312(e)(2)(ii) Encryption (Addressable)"Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate."
4 Remote access164.312(a)(2)(i) Unique user identification (Required) · 164.312(d) Person or entity authentication"Assign a unique name and/or number for identifying and tracking user identity." · "Implement procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed."
7 Monitoring and logs164.312(b) Audit controls · 164.308(a)(1)(ii)(D) Information system activity review (Required)"Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information." · "Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports."
8 Devices164.308(a)(5)(ii)(B) Protection from malicious software (Addressable)"Procedures for guarding against, detecting, and reporting malicious software."
All eight164.308(a)(1)(ii)(A) 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."

Two notes on reading the table. "Required" and "Addressable" are the rule's own labels for its implementation specifications, quoted as published. And which measures satisfy a standard in your office is a question for your own risk analysis and your compliance adviser; NIST publishes "SP 800-66 Rev. 2, Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide" for exactly that work. This page gives you the network facts to bring to it.

What does a managed network security plan cover, and what does the practice still own?

A managed plan normally covers the firewall and its subscriptions, segment design and firewall rules, Wi-Fi configuration, the remote-access gateway, DNS filtering, switch management, log collection and review, and patching of the devices it manages. The practice still owns the decisions: who may connect, what visitors may do, which devices exist, and whether the exception list is acceptable.

AreaWhat the plan should coverWhat the practice still owns
Firewallhardware or service, subscriptions renewed, rules written per segment, changes loggedapproving each rule change; naming who may request one
Segmentationthe segment design, the firewall rules between segments, the test that they holdsupplying the device list; telling the provider about every new device before it is plugged in
Wi-Fiaccess point configuration, standards, passphrase changes, guest network separationthe visitor policy: who gets the guest password and whether reps may use it
Remote accessthe gateway, MFA enforcement, named accounts, session logs, removal when someone leavesapproving each vendor; telling the provider the same day a staff member or vendor relationship ends
DNS filteringdeployment on the network and on laptops, the block lists, the reportsthe policy categories (webmail, streaming, social media on clinical machines)
Switches and portsmanaged switches, disabled unused ports, labels, the port mapnot adding unmanaged switches or moving devices between ports without asking
Monitoring and logscollection, retention to the agreed period, review, the monthly reportreading the report; writing down the retention period in the practice's own policies
Devicesinventory of managed devices, patching, EDR deployment, end-of-support trackingdeciding to replace or isolate unsupported equipment; funding the replacement
Documentationthe network diagram, segment list, exception list, vendor access list, current as of a stated datekeeping a copy the practice can open without the provider

The last row is the one to insist on. A practice that holds its own current network diagram, exception list and vendor-access list can change providers, answer an insurer and brief a new office manager without asking anyone. If a plan is priced as managed IT services for dental practices, these documents are what you should expect in return for the network part of the fee, and their absence is the first sign that "managed" means "billed".

Where the practice's building, cabling and network design were done by one company and support by another, the ownership of switches and ports in particular needs to be in writing. For the commercial side of a new design or a redesign, the owner page is dental office network design and installation.

Dental office network security self-audit: the one-visit checklist

This audit covers the network only; accounts, email, backups and training are in the wider dental office cybersecurity checklist. Answer each line yes, no or don't know. "Don't know" is a legitimate answer and the most useful one, because every "don't know" is a question for your provider. The evidence column says what a yes should look like; a yes without the evidence is a don't know.

#CheckEvidence of a yes
1The office has a business firewall, separate from the internet carrier's equipment or configured as one by your providerthe make and model, and a photo of it in the closet
2Its security subscriptions are active, with a renewal date you have seenthe renewal date in an email or the monthly report
3Firewall rule changes need a named approver in the practicethe name, and the last change request
4Guest Wi-Fi is a separate segment, not just a separate namea provider's test: a guest device cannot reach the server
5Imaging equipment and the server are not on the same segment as cameras, TVs and door controlsthe segment list with devices named
6The clinical Wi-Fi uses WPA3 or WPA2/WPA3 and its passphrase is not posted anywherethe access point setting, and a walk round the front desk
7The guest password is changed on a schedulethe schedule, and the date of the last change
8Every remote connection goes through one gateway with multifactor sign-inthe vendor access list with method and approver
9No remote desktop port is open to the internetthe provider's external scan result, dated
10Former staff and former vendors have no remaining accessthe removal date for the last person who left
11DNS filtering runs on the network and on laptops that leave the buildingthe blocked-category list and last month's report
12There are no unmanaged switches under desks or behind equipmenta walk round the office
13Unused wall ports are disabled at the switchthe port map
14The network closet locksa key or code, held by named people
15Logs are collected centrally and kept for a written periodthe retention number, in the practice's own policy
16A named person reviews alerts and the practice receives a monthly reportlast month's report
17No computer on the clinical or imaging segment runs an operating system past its end-of-support datethe device inventory with operating system versions
18EDR runs on every workstation and serverthe endpoint console count matched to the inventory
19The practice holds its own current network diagram, exception list and vendor access listthe documents, dated within the last year
20The eight layers above appear in the practice's risk analysisthe risk analysis, with the date

Count the yes answers with evidence. Fewer than ten means the network has probably grown one device at a time and needs a design pass rather than a product. Ten to sixteen means the structure exists and the gaps are specific; take the "no" and "don't know" lines to your provider as a list. Seventeen or more is a well-run network; keep the evidence current and repeat the audit once a year and after any construction or new imaging equipment.

The IT side: what your provider should be doing that you never see

Behind the eight layers there is routine work that produces no visible change in the office and is the difference between a network that is secure on the day it was installed and one that stays secure. Your provider should be able to describe each item below and show when it was last done.

    • Firmware on the firewall, switches and access points. Network equipment has its own software with its own vulnerabilities. Updates should be scheduled outside clinic hours, recorded, and tested afterwards by checking that imaging bridges and the practice software still connect.
    • Rule review. A quarterly read of the firewall rule set to remove exceptions whose reason has gone, and a check that each segment still cannot reach what it must not.
    • External scan. A periodic scan of the practice's public internet address from outside, to confirm nothing is listening that should not be, with the result kept.
    • Configuration backup. A saved copy of the firewall, switch and access-point configurations, so a failed device can be replaced in an hour instead of rebuilt from memory.
    • Device discovery. A regular comparison of what is actually on the network with the inventory, so the new TV or the spare laptop a hygienist brought in is found and placed in the right segment.
    • Account hygiene. Removal of VPN and gateway accounts the same day the practice reports a departure, and a review of vendor accounts that have not been used in months.
    • Reporting. The monthly summary described under layer 7, in words an office manager can read.

The items with a named practice-side step (new devices, departures, vendor approvals) only work if the practice does its part on the same day. A good provider makes that easy with one address or form for all three.

What to ask your IT provider about network security

Ask about the four things a provider with a real network method can show you on paper: the firewall and its subscriptions, the segment design and the test that it holds, how remote access and vendor access are controlled, and what is logged, kept and reported. Answers should be documents, dates and screenshots, not reassurance.

About the firewall

  • What firewall protects this office, when do its security subscriptions renew, and can we see the renewal confirmation?
  • Who in our practice approves a firewall rule change, and can we see the current list of exceptions with the reason for each?
  • When was the firewall's firmware last updated, and is its configuration backed up?

About segmentation and Wi-Fi

  • Which segments does our network have, which devices are in each, and can you show from a guest device that it cannot reach the server?
  • What security standard does the clinical Wi-Fi use, who knows the passphrase, and when was the guest password last changed?
  • Are there any unmanaged switches in the office, and are unused wall ports disabled?

About remote access and vendors

  • Who can connect to our network from outside, by what method, with multifactor sign-in on which accounts, and who approved each one?
  • Is any remote desktop service reachable from the internet, and when was the last external scan?
  • When a staff member or a vendor relationship ends, what do we send you, and how fast is their access removed?

About monitoring, logs and devices

  • What is logged, how long is it kept, who reviews it, and can we see last month's report?
  • Does DNS filtering run on our network and our laptops, and which categories does it block?
  • Which of our computers run an operating system past its end-of-support date, and what is the plan for each?
  • Can we have our own copy of the network diagram, segment list, exception list and vendor access list, dated?

If you are comparing providers on these answers, our review of the best dental IT companies compares the national firms, and our guide on how to choose a dental cybersecurity provider sets out what a whole security plan should include and how to score each proposal. The network is one of nine components; the rest are mapped in our guide to IT infrastructure for dental practices.

How Legend Networking can help

Legend Networking is based in Dallas and has served over 3,500 practices since 2004, with 22+ years in dental IT. Its engineers are in-house, with no outsourced first-level triage; it provides 24/7 monitoring; and support is remote-first nationwide, with onsite dispatch by appointment across served dental markets. Its Google rating is 4.8 from 173 reviews.

This guide's author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. The commercial side of hardening the eight layers, from firewall rules to vendor access, is set out on our dental cybersecurity services page. On a new office the network is planned before the first device arrives; one example is a startup build whose project update covers computers, networking, Wi-Fi, dental software, imaging integration and security planning. For day-to-day help with the devices on that network there is dental IT support, and city pages are listed under dental IT in your city.

Questions

Frequently asked questions

What is network security for a dental practice?

Network security for a dental practice is the set of controls between the internet and the computers that hold patient records: a business firewall with active subscriptions, a network divided into segments, secured Wi-Fi, controlled remote access, DNS filtering, managed switches and ports, monitored and retained logs, and supported devices. Endpoint software and backups sit beside it as separate layers.

Does a dental office need a firewall if every computer has antivirus?

Yes. Antivirus works on one computer at a time and cannot run on sensors, imaging units, phones, cameras or patient devices. A business firewall protects every device on the network at the point where traffic enters and leaves, enforces the boundaries between segments, and records what crossed them. The two tools cover different ground and a dental office needs both.

What is network segmentation in a dental office?

Segmentation divides one office network into several smaller networks that cannot reach each other unless a firewall rule allows it. A typical dental office uses five: clinical, imaging, voice, devices such as cameras and TVs, and guest Wi-Fi. It keeps a patient's phone or a compromised smart TV away from the server, and it is only real when the firewall enforces it, not when the Wi-Fi names differ.

Should patients use the same Wi-Fi as the dental practice?

No. Patients and visitors should use a guest wireless network that is a separate segment with its own password, reaches the internet only, and is capped so it cannot slow the operatories. A separate network name on the same segment is not enough; your IT provider should be able to show from a guest device that the server and workstations cannot be reached.

Does HIPAA require a firewall for dental practices?

The published text of the Security Rule does not name a firewall or any other product. It sets standards such as access control, audit controls, person or entity authentication and transmission security, quoted in the table above from 45 CFR 164.312, and requires a risk analysis under 164.308. Which measures meet those standards in your office is a question for that risk analysis and your compliance adviser.

What is the biggest data breach threat for dental practices at this time?

This page does not rank threats, because no single dated figure settles it. On the network, the two gaps that expose the whole practice at once are remote access reachable from the internet without multifactor sign-in, and a flat network where a patient's phone or a compromised TV can reach the server. A compromised email account is the other common door, and belongs with staff training.

What is DNS filtering and does a small dental office need it?

DNS filtering checks the web address each device tries to reach against lists of malicious, newly registered or off-policy domains and refuses the bad ones before a connection is made. A small dental office benefits because the filter protects every device, including imaging units, TVs and cameras that cannot run security software, and because its reports often show the first sign of a compromised machine.

How often should a dental office's firewall be updated?

Two things need updating on different clocks. The security subscriptions update their threat lists automatically as long as they are paid for, so the practice should know the renewal date. The firewall's own firmware should be updated when the maker releases security fixes, scheduled outside clinic hours and recorded, with a check afterwards that imaging bridges and the practice software still connect.

What does a managed network security plan include for a dental office?

A managed plan should cover the firewall and its subscriptions, segment design and rules, Wi-Fi configuration, the remote-access gateway with multifactor sign-in, DNS filtering, managed switches with disabled unused ports, log collection and review with a monthly report, patching of managed devices, and a current network diagram the practice holds. The practice keeps the decisions: who connects, what visitors may do, and which exceptions to accept.

How much does network security cost for a dental practice?

Cost depends on the firewall class and its annual subscriptions, the number of access points and managed switches, whether a remote-access gateway and DNS filtering are included, how much log retention is wanted, and how many devices are managed. Ask any provider to price those items separately rather than as one line, so you can see which layers you are paying for and which are missing.

Who is responsible for network security, the practice or the IT provider?

Both, in different ways. The IT provider owns the technical layers: the firewall, segments, Wi-Fi settings, remote-access gateway, filtering, switches, logs and patching. The practice owns the decisions and the information: which devices exist, who may connect, when someone leaves, what visitors may do, and whether the exception list is acceptable. The practice's risk analysis is where those responsibilities should be written down.

Can a cloud-based dental practice skip network security?

No. A practice whose software runs in the cloud still has imaging equipment, workstations, phones, cameras and a guest network in the building, still needs a firewall and segments to keep them apart, and depends on the network and the internet connection for every appointment. Cloud software moves the server out of the closet; it does not remove the network the staff and devices use.

The bottom line

If more than a few lines of the self-audit came back "don't know", the useful moment to find the answers is now, before an insurer, a payer or an incident asks. Start with a Free Dental IT Assessment: a review of computers, software, network security, backups and performance, with written findings and prioritized recommendations. Bring this page's self-audit to it, and read how the layers are hardened under dental cybersecurity services. For everything else on the network, from the imaging computer that will not update to the printer that disappears every Monday, the same team provides dental IT support.

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 your network before the next renewal asks the questions

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.