Health IT vendors sit in an unusual spot. They may never see a patient, yet they often hold the most privileged access in their clients’ environments: domain administrator rights, remote management agents on every workstation, backup copies of entire EHR databases, or vendor support accounts on clinical systems. When an IT vendor is compromised, every client it manages can be affected at once.
Under HIPAA, most health IT vendors that maintain, host, back up, support or access systems containing ePHI are business associates. That brings direct Security Rule liability and contractual obligations to each client. This page focuses on managed service providers, hosting and backup companies, EHR and clinical software vendors, and device or system vendors that provide remote support.
Determining your HIPAA role
The test is whether you create, receive, maintain or transmit ePHI on behalf of a covered entity or business associate. An MSP that administers servers holding patient data, a backup provider storing encrypted copies and a software vendor whose support team can view production records generally all qualify. HHS’s cloud computing guidance states that a provider storing ePHI is a business associate even when the data is encrypted and the provider does not have the key.
Vendor types and where their risk sits
| Vendor type | Typical PHI exposure | Controls clients ask about |
|---|---|---|
| Managed service provider (MSP) | Administrative access to client networks, servers, email and endpoints | Remote monitoring tool security, technician authentication, per-client credential separation, logging of administrative sessions |
| Hosting, colocation and backup | Storage of full databases and file systems | Encryption, backup integrity and restore testing, physical safeguards, data destruction at termination |
| EHR and clinical software vendor | Support access to production data, hosted instances, interfaces | Support access approval and logging, release management, audit log availability to clients |
| Device or system vendor with remote support | Remote sessions into imaging, lab or monitoring systems | Who can initiate sessions, whether clients approve each one, how sessions are recorded |
Key regulatory considerations for IT vendors
Direct Security Rule obligations
As a business associate, you need your own risk analysis (§164.308(a)(1)(ii)(A)), risk management, security official, workforce training, incident procedures, contingency planning and documentation retained for six years under §164.316. Your clients’ compliance programs do not cover your internal environment.
Subcontractors
MSPs rely on remote management platforms, ticketing systems, offsite backup and sometimes subcontracted technicians. Any of these that handle client ePHI are your subcontractor business associates and need BAAs. If your remote management platform stores session recordings or files from client systems, it may hold ePHI.
Breach notification upstream
Under §164.410, you must notify each affected client without unreasonable delay and no later than 60 days after discovery — and most client BAAs are stricter. A compromise of your remote management tooling may trigger notification obligations to many clients at once.
Rules beyond HIPAA
Developers of certified health IT have separate obligations under ONC’s certification program and information blocking regulations. Those fall outside HIPAA and outside our scope, so confirm them with counsel; we focus on HIPAA privacy and security.
Challenges we frequently see
- Technicians sharing a single administrative account across multiple clients.
- Remote access tools exposed to the internet without multi-factor authentication, which HIPAA does not explicitly mandate under the current rule but which is widely regarded as essential good practice.
- Backups that clients assume are encrypted and tested, with no evidence either way.
- BAAs signed years ago that do not reflect current services or subcontractors.
- No defined process for telling clients when the vendor itself has a security incident.
How we tailor IT vendor engagements
We generally start with a HIPAA security risk assessment of your own environment — the tools, accounts and processes you use to manage clients — rather than your clients’ environments. A HIPAA technical safeguards assessment then tests access control, audit logging, integrity and transmission security in depth.
Vendors who need to answer client due diligence with evidence often pair this with HIPAA security consulting to close gaps, and business associate compliance work to bring client and subcontractor BAAs in line with what you actually deliver.
Planning for a compromise of your own tools
The scenario that worries health IT vendors most is not an attack on one client but an attack through the vendor: stolen technician credentials, a compromised remote monitoring platform or malicious use of a support account, used to reach many client environments at once. Your contingency plan and security incident procedures under §164.308(a)(6) and §164.308(a)(7) should address this directly, not only outages at a single client.
A workable plan answers practical questions in advance. How quickly can you disable remote management access across all clients? Who decides to do it, and how do clients keep operating while it is off? Which logs will show what an attacker touched in each environment, and how long are they retained? Which clients have the shortest notification deadlines, and who contacts them? Running a tabletop exercise against this scenario with your leadership and technical leads usually surfaces dependencies — a single admin account, an unmonitored tool — that are much cheaper to fix before an incident than during one.
Starting checklist for health IT vendors
- 1
Confirm your role for each client
Document which services involve ePHI and confirm a current BAA covers each one.
- 2
Inventory privileged access
List every account and tool your staff use to reach client systems, and eliminate shared credentials.
- 3
Harden remote management
Restrict who can use remote tools, require strong authentication and log every session.
- 4
Prove your backups
Test restores on a schedule and keep records clients can review.
- 5
Map subcontractors
Identify platforms and partners that touch client ePHI and confirm BAAs with each.
- 6
Write a client notification plan
Define how you will notify every affected client within the shortest BAA deadline if your own tooling is compromised.
Frequently asked questions
We only fix computers. Are we really a business associate?
If your work involves maintaining or accessing systems that contain ePHI on a client’s behalf, you are usually a business associate. Occasional, incidental exposure is treated differently from routine administrative access, so the facts matter.
Our backups are encrypted and we don’t have the key. Do we still need a BAA?
Generally yes. HHS’s cloud computing guidance states that a service provider maintaining ePHI is a business associate even if it cannot decrypt the data.
Is multi-factor authentication required by HIPAA?
The current Security Rule does not name MFA explicitly, though it requires person or entity authentication and a risk-based approach. MFA is widely recommended good practice, and many client contracts require it. A proposed Security Rule update published in January 2025 addresses MFA, but it is a proposal; verify its current status.
Can a HIPAA assessment help us answer client security questionnaires?
Yes. A documented risk analysis, remediation plan and policy set give you consistent, evidence-based answers. It is not a certification — HIPAA has none — but it is what knowledgeable clients expect to see.
Authoritative sources
- HHS — Guidance on HIPAA and Cloud Computing
- HHS — Security Rule
- HHS 405(d) Health Industry Cybersecurity Practices
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.