Cybersecurity: 24/7/365

Your front desk computer is inside the office network. So it must be safe, right? That is the assumption traditional network security is built on — if you are inside the perimeter, you are trusted. Firewall on the outside, free movement on the inside.
That assumption got a Florida orthopedic practice breached in 2024. An attacker compromised one employee's email account through a phishing link. Because the network trusted everything inside the firewall, the attacker moved laterally — from email to the practice management system, to the billing database, to the PACS imaging server. Within 72 hours, they had access to 47,000 patient records. The ransom demand was $2.3 million.
Zero trust is built on the opposite assumption: trust nothing, verify everything. No device, user, or application gets access to anything until it proves it should have access — every single time. It is the security framework the federal government adopted in 2022, that major health systems are implementing now, and that the proposed 2026 HIPAA Security Rule would effectively require for medical practices of all sizes.
The perimeter-based security model — firewall at the edge, trusted network inside — was designed for a world where everyone worked in one building on wired computers. Healthcare in 2026 does not look like that:
The perimeter has dissolved. Your EHR runs in the cloud. Staff access systems from home, from satellite offices, from their phones in the parking lot. Telehealth connects patients from their living rooms. Cloud-hosted applications mean your data lives on servers you do not control. There is no single perimeter to defend anymore.
Inside threats are real. 58% of healthcare data breaches involve insiders — both malicious actors and accidental exposure. A disgruntled employee accessing records they should not see. A billing coordinator clicking a phishing link. A nurse plugging a personal USB drive into a workstation. Perimeter security does nothing against threats that originate inside the network.
Lateral movement is the real danger. In most healthcare breaches, the initial compromise is not what causes the damage. It is the attacker's ability to move freely once inside. They compromise one credential and then pivot across the network — email to EHR, EHR to file server, file server to backup system. In a flat network with implicit trust, one compromised account gives access to everything.
Connected devices expand the attack surface. A typical medical practice now has networked medical devices, IP cameras, smart thermostats, printers, VoIP phones, and IoT sensors. Each device is a potential entry point. A 2025 report found that 87% of connected medical devices run outdated operating systems with known vulnerabilities. If your network trusts these devices by default, they become backdoors.
Zero trust is not a product you buy. It is a security strategy built on five principles. Understanding these principles helps you evaluate whether your current setup falls short — and where to start improving.
1. Never trust, always verify. Every access request is treated as if it comes from an untrusted network — even if the user is sitting at a desk in your office. The user must authenticate (prove who they are) and be authorized (prove they should have access to that specific resource) before every session. No exceptions for "internal" users or devices.
2. Least privilege access. Users get access only to the resources they need for their specific role — nothing more. A front desk employee can access scheduling but not clinical notes. A billing coordinator can access claims data but not imaging records. A provider can access their own patients' records but not the entire database. If someone's job changes, their access changes immediately.
3. Assume breach. Design your security as if an attacker is already inside your network. Segment systems so that a compromised component does not expose everything. Monitor for unusual behavior continuously. Have incident response plans ready. This mindset drives decisions toward containment and resilience rather than just prevention.
4. Micro-segmentation. Divide your network into small, isolated segments. Your EHR system is in one segment. Your billing system is in another. Your guest Wi-Fi is completely separate. Medical devices occupy their own segment. Movement between segments requires explicit authorization. If an attacker compromises one segment, the blast radius is contained.
5. Continuous verification. Authentication is not a one-time event at login. The system continuously evaluates whether a session should remain active based on user behavior, device health, location, time of day, and risk signals. If a user who normally accesses records from the front desk at 9 AM suddenly accesses them from a foreign IP at 2 AM, the session is challenged or terminated automatically.
Zero trust sounds like an enterprise concept. But the principles scale down to a 5-person practice. Here is what zero trust looks like in practice for a small medical office:
Identity and access management. Every person has a unique account — no shared logins for the front desk, no generic "billing" account. Multi-factor authentication is required for every login, every time. Role-based access controls limit what each person can see and do. Microsoft 365 Business Premium and Google Workspace Business Plus both include identity management features that support these requirements.
Device trust. Only managed, verified devices can connect to practice systems. Personal laptops and phones that have not been enrolled in your device management system cannot access the EHR, even with valid credentials. Microsoft Intune (included with Microsoft 365 Business Premium) or similar mobile device management (MDM) tools enforce device compliance — checking for current operating systems, active antivirus, disk encryption, and screen lock policies before granting access.
Network segmentation. Your office network is divided into segments using VLANs (virtual local area networks) configured on your router or managed switch. At minimum, separate these:
A next-generation firewall (NGFW) controls traffic between segments. A medical device on the device network can send data to the EHR server on the clinical network — but cannot reach the billing system, the internet, or the guest Wi-Fi.
Application-level access controls. Access to applications is controlled individually, not by network location. Being on the clinical network does not automatically grant access to the EHR. Users still need to authenticate with their credentials and MFA to access each application. Cloud applications (EHR, email, practice management) use conditional access policies that evaluate the user's identity, device compliance, and risk level before granting a session.
Endpoint detection and response (EDR). Every workstation and server runs endpoint detection and response software — not just traditional antivirus. EDR monitors behavior in real time: if a workstation suddenly starts encrypting files (ransomware behavior), the EDR agent isolates it from the network within seconds. This containment is zero trust in action — even a trusted device loses trust the moment its behavior becomes suspicious.
Encrypted communications. All data in transit is encrypted — EHR sessions, email, file transfers, VoIP calls. All data at rest is encrypted — hard drives, backups, cloud storage. Encryption ensures that intercepted data is useless to attackers, even if they breach a network segment.
Logging and monitoring. Every access event is logged — who accessed what, when, from where, and on what device. These logs feed into a security information and event management (SIEM) system or your managed security provider's monitoring platform. Anomalies trigger alerts: unusual login times, access from new locations, large data downloads, and failed authentication attempts.
You do not implement zero trust overnight. Most practices adopt it in phases over 6 to 12 months, starting with the highest-impact, lowest-complexity changes:
Phase 1 — Identity (Month 1-2): This is the foundation. Eliminate shared accounts. Assign unique credentials to every user. Enable MFA on every system that supports it — EHR, email, practice management, remote access. Implement role-based access controls. Review who has admin privileges and remove unnecessary access. Cost: $0-$5/user/month (most identity features are included in business-tier Microsoft 365 or Google Workspace).
Phase 2 — Devices (Month 2-4): Enroll all practice-owned devices in a mobile device management platform. Set compliance policies: minimum OS version, encryption required, screen lock required, antivirus active. Block non-compliant devices from accessing practice applications. Deploy EDR on all endpoints. Cost: $5-$15/user/month for MDM + EDR.
Phase 3 — Network (Month 3-6): Segment your network into VLANs. Deploy or upgrade to a next-generation firewall. Create rules governing traffic between segments. Isolate medical devices and IoT. Set up a separate guest Wi-Fi network with no access to clinical systems. Cost: $500-$3,000 for a next-generation firewall (e.g., Fortinet, SonicWall, Meraki MX) depending on practice size, plus professional configuration.
Phase 4 — Monitoring (Month 4-8): Enable comprehensive logging across all systems. Configure alerts for suspicious activity. If you use a managed IT provider, ensure they monitor your environment 24/7 and have incident response procedures defined. Run a penetration test to validate your segmentation. Cost: included in most managed IT agreements, or $2,000-$5,000 for an annual pentest.
Phase 5 — Continuous improvement (Ongoing): Review access policies quarterly. Update device compliance requirements as new threats emerge. Conduct annual risk assessments that include zero trust maturity evaluation. Adjust segmentation as you add new systems or services. Train staff on new procedures.
Here is a realistic cost breakdown for a 10-person medical practice implementing zero trust over 12 months:
Total first-year cost: approximately $8,000-$15,000, or $67-$125/month per user. This aligns with typical healthcare IT budgets of $150-$350 per user per month for comprehensive managed IT services.
Compare that to the cost of a healthcare data breach: $10.93 million on average for healthcare organizations, or $200-$400 per patient record. For a practice with 10,000 patient records, a breach could cost $2-$4 million. Zero trust is not an expense — it is insurance.
The proposed 2026 HIPAA Security Rule NPRM does not use the phrase "zero trust" — but its requirements align directly with zero trust principles:
Practices that implement zero trust now will already be compliant with most of the proposed requirements when the final rule takes effect. Practices that wait will face a costly scramble to overhaul their security architecture under regulatory pressure.
"It is only for large enterprises." The principles scale to any size. A 5-person practice with MFA, segmented Wi-Fi, EDR, and role-based access is practicing zero trust — even without enterprise-grade tools. The smallest practices often benefit the most because they have fewer systems to segment and fewer users to manage.
"It will slow down my staff." MFA adds 10 seconds to login. Conditional access policies work silently in the background. Network segmentation is invisible to users. The only noticeable change is that staff may need to re-authenticate when accessing sensitive systems or when risk conditions change. After the first week, most staff barely notice the difference.
"We already have a firewall — we are fine." A firewall is one component — and it is focused on the perimeter. It does not protect against compromised credentials, insider threats, phishing attacks that bypass email filters, or lateral movement within the network. A firewall is necessary but not sufficient.
"It requires ripping out everything we have." Zero trust is additive. You build it on top of your existing infrastructure. Most practices start with identity (MFA, role-based access) using tools they already pay for. You do not replace your systems — you add layers of verification to them.
"We cannot afford it." You cannot afford not to. Cyber insurance carriers are increasingly requiring zero trust principles — MFA, network segmentation, EDR, and access controls — as conditions of coverage. Without them, you may not qualify for a policy or may face significantly higher premiums. The cost of zero trust is a fraction of the cost of non-compliance.
A healthcare-focused managed IT provider should design and implement zero trust as part of their standard service. Here is what to expect:
If your IT provider is not talking about zero trust, they are behind. Ask about their approach — and if they cannot explain how they implement these principles for healthcare practices, it is time to evaluate alternatives.
Zero trust is not a buzzword and it is not optional. It is the security framework that the federal government, major health systems, and cyber insurance carriers have adopted as the standard. The proposed 2026 HIPAA Security Rule aligns directly with zero trust principles, signaling that regulators expect healthcare practices to follow.
The good news: you do not need to implement everything at once. Start with identity — MFA and role-based access controls. Then layer on device trust, network segmentation, and monitoring. Each phase reduces your risk and moves you closer to a security posture that withstands modern threats.
The perimeter is gone. Trust must be earned, not assumed. That is the future of healthcare security — and it starts with your next login.
Book a free IT assessment to evaluate your practice's security posture and build a zero trust roadmap tailored to your size and budget. Explore our cybersecurity services and managed IT plans to see how we protect healthcare practices with zero trust principles built in.