- Published
- Updated
- 9 min read

TL;DR: Zero trust means no login, device or network connection is trusted just because it is inside your office. For a small Worcester medical practice that comes down to unique logins with multifactor authentication, known devices, the least access each person needs, a separated network and logs someone reads. It lines up with what the HIPAA Security Rule already asks for.
Zero trust is a way of designing access, and it fits small medical offices better than most people expect. The old model was a locked front door: once you were on the office network, you could reach almost everything. Today your staff reach patient records from home, the EHR talks to billing, billing talks to the portal, and a vendor logs in remotely once a month. There is no single front door anymore.
Worcester County had 342 offices of physicians and 351 dental offices with employees in 2023. Of those physician offices, 273 had fewer than 20 employees. (U.S. Census Bureau, County Business Patterns 2023 (opens in a new tab)) Most of those practices do not have a security team. Here is what zero trust looks like at that size, in plain steps.
Why is security hard for a small medical office?

Four things stack up in a practice in Worcester or Shrewsbury.
Remote access. Billing staff work from home, providers finish notes at night, and a laptop goes home in a tote bag. Each of those connections is a way in.
Integrations. Your EHR connects to billing, which connects to the patient portal, scheduling and payments. Every connection is a path, and attackers who get into one system look for the next.
Rules that feel abstract. The HIPAA Security Rule tells you what to protect, not which product to buy. That flexibility is useful, but it leaves the practice to work out the details.
Small teams. The office manager is often also the IT person. Security competes with patients, payroll and the phone.
The stakes are real. IBM's 2025 Cost of a Data Breach report found that healthcare remains "the costliest industry for data breaches, with each breach costing an average of $7.42 million," the top position for "the 14th consecutive year." (TechTarget, reporting IBM's 2025 report (opens in a new tab)) That average is driven by larger organizations, so do not read it as your bill. Read it as a sign that health data is worth a lot to the people who steal it.
What does zero trust actually mean?

NIST, the federal standards agency, defines it this way: "Zero trust (ZT) is the term for an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users, assets, and resources." The key line is this one: "Zero trust assumes there is no implicit trust granted to assets or user accounts based solely on their physical or network location." (NIST SP 800-207, Zero Trust Architecture (opens in a new tab))
In office terms: the old model checked your badge at the front door and then let you into every room. Zero trust checks at every room, every time.
Here is a hypothetical. Dr. Smith opens patient records from her laptop. A zero trust setup checks more than her password:
- Is this a device the practice knows and manages?
- Did she pass a second factor, like an app prompt or a security key?
- Does her role need the records she is opening?
- Does the request look like her normal pattern, or like 500 charts at 2 a.m. from a new machine?
If something is off, the system asks for more proof or stops the request, and someone reviews it. Our knowledge base has a longer explainer on zero trust architecture.
How does zero trust line up with HIPAA?
Closely. The HIPAA Security Rule's technical safeguards already ask a practice to "allow access only to those persons or software programs that have been granted access rights," to "Assign a unique name and/or number for identifying and tracking user identity," to "terminate an electronic session after a predetermined time of inactivity," to keep "mechanisms that record and examine activity in information systems," and to "verify that a person or entity seeking access to electronic protected health information is the one claimed." (eCFR, 45 CFR 164.312 (opens in a new tab)) Those are zero trust ideas written in regulatory language: unique identity, least access, verification and logs.
HHS has also proposed tightening the rule. A proposed rule published January 6, 2025 would require practices to "Deploy multi-factor authentication to all technology assets," to keep "a technology asset inventory and a network map," and to make sure systems "are segmented in a reasonable and appropriate manner." (Federal Register, HIPAA Security Rule proposed rule (opens in a new tab)) It is a proposal, not a final rule, and I track where it stands in HIPAA Security Rule changes for a small practice (opens in a new tab). Either way, those three items are good practice today. Our HIPAA explainer covers the rest of the rule.
Which threats does zero trust help a medical practice with?

HHS's 405(d) program, which publishes free cybersecurity practices for health care, organizes its training around five threats: social engineering, ransomware, loss or theft of equipment or data, insider data loss (accidental or malicious), and attacks against network connected medical devices. (HHS 405(d), Health Industry Cybersecurity Practices (opens in a new tab)) Here is how zero trust maps to the ones a small office sees most.
Stolen or reused passwords. Attackers try passwords leaked from other sites. A unique login per person plus a second factor stops most of these cold.
Business email compromise. An email that looks like your EHR vendor asks someone to "verify account details." Zero trust limits the damage: a stolen password alone does not open the chart system, and an account can only reach what its role needs.
Ransomware that spreads. When the front desk PC, the imaging workstation and the server sit on one flat network, one infected machine can reach them all. Segmentation keeps it in one zone.
Lost devices. A phone left in a cab is a smaller problem when the device is encrypted, managed and can be cut off from the EHR in minutes.
What does a zero trust rollout look like for a small practice?

You do not buy zero trust in a box. CISA's maturity model breaks it into five pillars, "Identity, Devices, Networks, Applications and Workloads, and Data," and describes "traditional, initial, advanced, and optimal" stages within each. (CISA, Zero Trust Maturity Model (opens in a new tab)) A small office does not need to reach optimal. It needs to move each pillar one step forward, in an order that does not stop patient care.
Phase 1: Identity and devices
- Multifactor authentication everywhere. CISA says MFA "adds an extra layer of protection by requiring two or more ways to verify a user's identity," and that "Businesses should aim to use a phishing-resistant MFA method." (CISA, require multifactor authentication (opens in a new tab)) Start with email, the EHR and remote access.
- One login per person. No shared front desk account. HIPAA already asks for unique user identification.
- Known devices only. Practice-managed laptops and phones get full access. Personal devices get a limited, browser-only path, or none.
Phase 2: Least access and logging
- Access by role. Billing sees billing. The front desk sees scheduling. Providers see their patients.
- Automatic logoff. Idle sessions end, and remote sessions expire.
- Logs someone reads. Turn on audit logs and decide who reviews unusual access, and how often.
Phase 3: Zero trust network segmentation
- Separate zones. Patient systems in one zone, office PCs in another, guest Wi-Fi and medical devices on their own.
- Narrow vendor access. The vendor who logs in monthly gets one path to one system, turned on only when needed.
What should a Worcester practice do first?

Take a hypothetical six-person family practice in Westborough. Here is a plan that fits around patients.
This week: map what you have
- List every system with patient data and every connection between them.
- List every device and person with access, including vendors.
- Check which accounts are shared and which have no second factor.
- Look at the logs you already have for anything odd.
This month: the core zero trust controls
- Turn on MFA for email, the EHR and remote access.
- Retire shared logins and set access by role.
- Enroll practice devices and decide what personal devices may do.
- Brief the team in fifteen minutes on what changes and why.
This quarter: contain and rehearse
- Segment the network so patient systems sit apart.
- Write a short incident plan with names and phone numbers. Our note on the first 24 hours after a breach is a good place to start, along with our incident response explainer.
- Test your backups by restoring one. See the 3-2-1 rule in practice.
- Review access every quarter and remove what nobody uses.
What does zero trust cost a small practice?
An earlier version of this post printed a monthly price range and average fine and downtime figures. We could not trace those numbers to a reputable source, so we took them out. Honest answer: the cost depends on how many systems you run, whether your EHR is in the cloud, how many devices you manage, and how much of the work your current IT provider already does. Many first steps, like turning on MFA in systems you already pay for, cost staff time rather than new software.
The value side is clearer. Zero trust limits how far one stolen password or one infected PC can reach, and it produces the access records and logs HIPAA already expects you to keep.
Common objections, and honest answers

"It's too complicated." It is a series of small changes. Do them in stages, starting with identity, and nobody gets locked out.
"My staff will hate it." Done well, single sign-on with one strong login replaces a sticky note of passwords. The extra tap on a phone takes seconds.
"We're too small to be a target." Small practices hold the same kind of records as large ones, usually with fewer people watching.
"Our current setup is fine." Maybe. Run the one-week map above. If you find shared logins, accounts without a second factor or a flat network, you have your first project.
Frequently asked questions
Is zero trust a product we buy?
No. It is a way of designing access. Products help, but the work is deciding who needs what, checking it every time, and cutting the paths nobody needs.
Does HIPAA require zero trust?
Not by name. The Security Rule asks for unique user IDs, access control, automatic logoff, audit controls and authentication, which are core zero trust ideas. A 2025 proposal would add MFA and segmentation.
Is zero trust only for large hospitals?
No. Small practices with remote staff and cloud systems benefit quickly, because one stolen password can otherwise reach everything on a flat network.
Where should a small practice start?
With identity: one login per person and multifactor authentication on email, the EHR and remote access. Then devices, then roles, then the network.
Do we have to turn off our VPN?
Only when an identity-based path is ready and tested. Move access over in stages so nobody is locked out of the systems they need.
How long does a zero trust rollout take?
There is no standard timeline. A small office can usually get MFA and unique logins done in weeks; segmentation and logging take longer.
This article is general information, not legal advice. Kief Studio is not a law firm, and reading it does not create an attorney-client relationship. Laws and regulations change, so check the current text and talk with a licensed Massachusetts attorney about your situation.
Where we fit

Kief Studio is in Shrewsbury, and we work with practices in Worcester, Shrewsbury and across Central Massachusetts. Our zero trust architecture work maps identities, devices, applications and the paths between them, puts identity checks and least privilege in front of each system, segments the network so one compromised account cannot reach everything, and rolls changes out in stages so the team keeps working while access tightens. Swapping one product for another and calling it zero trust while the network stays flat is not what we do.
For the HIPAA side, our HIPAA compliance consulting maps where regulated data actually lives, closes the gaps in the systems first and then brings the documentation in line. We are not your auditor of record, and we keep those roles apart.
First conversation is free. No commitment.




