How should VLANs be set up in a dental office?
On this page
- Key facts
- Why use VLANs in a dental office?
- What VLANs does a dental office need?
- How should imaging be segmented?
- Why do phones get their own VLAN?
- Where do cameras and other IoT devices go?
- How should guest Wi-Fi be set up?
- How should vendors and the IT company connect?
- When should the VLAN plan be made?
- How FloorStack helps
- Free tools for this step
- Frequently asked questions
- Sources
Split the network by job and allow only the traffic each job needs. A typical 2026 dental office uses about 6 segments: clinical, imaging, phones, cameras, guest Wi-Fi and network management. HHS's small-practice cybersecurity guidance says to restrict access between devices and limit data exchange to what operations require (HHS 405(d) HICP).
Key facts
| Point | Guidance | Source |
|---|---|---|
| Why segment | Restrict access between devices; limit data exchange to what's required | HHS 405(d) HICP |
| High-impact devices | Medical devices and IoT (security cameras, badge readers, sensors) in more restricted zones | HHS 405(d) HICP |
| Guests | Guest networks separate from organizational data and systems | HHS 405(d) HICP |
| Guest Wi-Fi | Logically separated WLANs for guest and internal use | NIST SP 800-153 |
| Ransomware | Segmentation can contain intrusions and limit lateral movement | CISA |
| Vendors | Third parties only on networks their role requires, through tightly controlled interfaces | HHS 405(d) HICP |
| HIPAA | Security Rule is flexible, scalable and technology neutral; it doesn't mandate VLANs | HHS |
Why use VLANs in a dental office?
A flat network lets anything talk to anything. If a front-desk PC opens a malicious attachment, the ransomware can reach the imaging server, the cameras and the backups. CISA's ransomware guide says network segmentation can help contain an intrusion and prevent or limit lateral movement by attackers (CISA). HHS's cybersecurity practices for small healthcare organizations recommend configuring networks to restrict access between devices, so an attack can't spread across the network (HHS 405(d) HICP).
HIPAA itself doesn't name VLANs. HHS describes the Security Rule as flexible, scalable and technology neutral, leaving practices to choose reasonable and appropriate measures for their size and risks (HHS). Segmentation is one way to support the rule's access-control and transmission-security standards (45 CFR 164.312).
What VLANs does a dental office need?
Here is an example plan. The numbers and subnets are illustrative; your IT provider sets the real ones. It matches the logical example in our network diagram examples.
| VLAN | Segment | What's on it | Typical access |
|---|---|---|---|
| 10 | Clinical | Workstations, front desk, PMS server/NAS | PMS server, internet, printers |
| 20 | Imaging | CBCT, RCU, pano, sensor PCs, imaging server | Only the ports the imaging vendor requires to clinical workstations |
| 30 | Phones | VoIP handsets | Phone provider's cloud; prioritized |
| 40 | Cameras | Cameras, NVR | NVR only; no internet except vendor-approved |
| 50 | Guest Wi-Fi | Patient devices | Internet only |
| 60 | Management | Switches, APs, UPS, firewall admin | IT admins only |
Small offices sometimes merge clinical and imaging. Keep guest, cameras and management separate in every design.
How should imaging be segmented?
Carefully, because imaging software is sensitive to blocked ports. Dentsply Sirona's site survey lists ports that must be open, including SQL Server 1433 and several Sidexis services, and recommends reserved static IPs outside DHCP for the x-ray unit and RCU (Dentsply Sirona). If imaging lives on its own VLAN, the firewall rules must allow those ports between imaging and the workstations that view images. Some units skip the LAN entirely: Carestream's CS 8100 3D must connect to its computer through a point-to-point Ethernet link (Carestream Dental). Get the imaging vendor's survey before writing rules. See network requirements for imaging.
Why do phones get their own VLAN?
For call quality and separation. Cisco's switch guide explains that a voice VLAN lets an access port carry IP phone traffic on one VLAN and data from a PC plugged into the phone on another, and that because call quality can deteriorate when data is sent unevenly, the switch prioritizes voice with quality of service (Cisco). That lets a front-desk PC share a drop with a phone. Ask your phone provider which VLAN tagging their handsets support. See dental office phone systems.
Where do cameras and other IoT devices go?
In a restricted zone. HHS recommends placing high-impact assets, including medical devices and IoT items such as security cameras, badge readers, temperature sensors and building management systems, in more restricted network zones (HHS 405(d) HICP). Cameras should reach the NVR, and staff should reach the NVR's viewer, not the cameras directly. See dental office security cameras.
How should guest Wi-Fi be set up?
On its own VLAN with internet-only access. HHS recommends guest networks in waiting areas that separate organizational data and systems and allow only authorized guest services (HHS 405(d) HICP). NIST's wireless guidance says guest and internal WLANs should be logically separated so devices on one can't connect to devices on the other (NIST SP 800-153). See HIPAA-compliant Wi-Fi and dental office Wi-Fi.
How should vendors and the IT company connect?
Through a controlled path, onto only the segment they support. HHS recommends allowing third parties, including vendors, access only to networks necessary to their role and only through tightly controlled interfaces (HHS 405(d) HICP). The imaging vendor's remote support shouldn't land on the camera VLAN.
The management VLAN holds the keys to everything, so the practice should own those admin accounts, not the IT company. The free credential ownership checklist (coming soon) is planned to list every admin account (firewall, switches, Wi-Fi controller, NVR).
When should the VLAN plan be made?
Before the switch is ordered and before drops are labeled, so the low-voltage contractor knows which jacks are phones, cameras or imaging. The free network & IT plan generator (coming soon) is planned to turn your floor plan into a drops, rack, Wi-Fi and VLAN plan. FloorStack Studio (live, free plan) places every device in a 3D plan so each drop can be assigned a segment.
How FloorStack helps
FloorStack is a dental build-out platform that plans the network, including segments, before the walls close. FloorStack Studio (live, free plan) maps every device. The network & IT plan generator and credential ownership checklist are free tools coming soon. Back to the Dental Office IT Setup hub.
Free tools for this step
- Network & IT plan generator (free tool, coming soon): turn your floor plan into a drops, rack, Wi-Fi and VLAN plan.
- FloorStack Studio (live, free plan): a 3D IT plan of your office with every device placed.
- Credential ownership checklist (free tool, coming soon): list every admin account the practice should own, with a "password hostage" letter template.
Frequently asked questions
Does HIPAA require VLANs?
No. HHS calls the Security Rule flexible, scalable and technology neutral (HHS); segmentation is a common way to meet it.
How many VLANs does a dental office need?
Often about six: clinical, imaging, phones, cameras, guest and management. Small offices may merge clinical and imaging.
Should guest Wi-Fi be on a separate VLAN?
Yes. HHS and NIST both call for guest networks separated from internal systems (NIST SP 800-153).
Can imaging go on its own VLAN?
Yes, if the firewall allows the ports the imaging vendor lists (Dentsply Sirona).
Should security cameras be on the main network?
No. HHS recommends putting IoT devices like cameras in more restricted zones (HHS 405(d) HICP).
Does segmentation stop ransomware?
It can contain an intrusion and limit lateral movement, per CISA (CISA), but it isn't a substitute for backups.
Sources
- HHS 405(d): Health Industry Cybersecurity Practices, Technical Volume 1 (PDF)
- CISA: #StopRansomware Guide
- NIST SP 800-153: Guidelines for Securing Wireless Local Area Networks (PDF)
- HHS: Summary of the HIPAA Security Rule
- 45 CFR 164.312: Technical safeguards (Cornell LII)
- Dentsply Sirona: Imaging Site Survey, Version 44 (PDF)
- Carestream Dental: CS 8100 3D Installation Guide SM843 (PDF)
- Cisco: Configuring Voice VLANs, Catalyst 9200, IOS XE 17.15
More in Dental Office IT Setup
- HIPAA-Compliant Wi-Fi for Dental OfficesHow to make dental office Wi-Fi HIPAA compliant in 2026: WPA3, a separate guest network, unique logins, quarterly checks and what HIPAA actually requires.5 min read
- IT Onboarding Checklist for a New Dental StartupAn MSP's 2026 IT onboarding checklist for a dental startup: contract and BAA, owner-held accounts, network plan, PMS specs, security baseline and go-live tests.6 min read
- How to Back Up a Dental Practice: 3-2-1 and HIPAA (2026)How a dental practice should back up patient data in 2026: the 3-2-1 rule, offline copies, tested restores, imaging files and what HIPAA requires.6 min read
- Choosing a Firewall for a Dental OfficeHow to choose a dental office firewall in 2026: vendor support dates, IPS, VLANs, MFA-protected VPN, logging and owner-held admin access, vendor-neutral.5 min read
- Pricing IT Projects for Dental New BuildsHow MSPs should price IT for a dental new build in 2026: phases, cabling, hardware BOM, labor, allowances, change orders and milestone billing tied to the plan.5 min read
- Dental Office IT Setup Checklist for New PracticesA 2026 IT setup checklist for new dental practices: software choice, specs, cabling, rack, network, internet failover, backups, accounts and go-live tests.6 min read