Quick answer
Do nurses working remotely need a VPN?
Use the remote-access tools your employer approves, and add a VPN for shared Wi-Fi. A VPN encrypts your traffic between your device and the VPN server, so a coffee shop, hotel or patient's home network can't read it. It doesn't make you HIPAA compliant, and it doesn't replace multi-factor authentication or your employer's policies.
| Situation | What a VPN does |
|---|---|
| Coffee shop, hotel or patient's Wi-Fi | Encrypts your traffic to the VPN server, so the network can't read it. |
| Known phishing sites | CyberFence's Web Shield blocks known ones while connected. |
| Your employer's EHR access rules | A VPN doesn't replace them. Follow your employer's policy. |
| Stolen passwords | Multi-factor authentication matters more here than any VPN. |
Telehealth is now a routine part of nursing. If you are a nurse doing telehealth consultations, remote patient monitoring or clinical documentation from home, you may be working with patient data on networks your employer doesn't control.
That gap between where patient data is and how it is protected is where problems can start.
Healthcare data breaches are reported to HHS, and its breach portal lists the larger ones publicly. Remote access is part of the risk: home and public Wi-Fi, personal devices, and stolen passwords used to sign in to health record systems.
HIPAA doesn't name VPNs, and a VPN doesn't make you compliant. On networks you don't control, it's a practical way to encrypt your traffic, alongside the tools and policies your employer sets.
Why Remote Nursing Creates Real HIPAA Risk
HIPAA's Security Rule requires regulated organizations to guard against unauthorized access to electronic protected health information (ePHI) sent over an electronic network. In a hospital, the facility's network and IT team handle much of that. At home, you're on a network your employer doesn't control, so follow its remote-access policy: usually its approved devices, apps and VPN.
Your home Wi-Fi encryption (WPA2 or WPA3) protects traffic between your device and your router. Beyond the router, your EHR, telehealth platform or patient portal should be protecting the connection with HTTPS. The weaker points are shared networks, such as a coffee shop or a patient's Wi-Fi, an out-of-date router, and stolen passwords.
Phishing and stolen passwords are a recurring problem in healthcare, and remote staff can't easily lean over and ask a colleague whether a message looks right.
The risks remote nurses face include:
Data in transit on networks you don't control. Most clinical platforms encrypt their connections with HTTPS. On a shared network, others can still see which services you connect to, and fake hotspots and sign-in pages try to catch the rest.
Public Wi-Fi exposure. Nurses doing telehealth from a coffee shop, a patient's home or anywhere outside their own network face the same shared-network risks described in our hotel Wi-Fi banking guide, but with patient data instead of financial data. Check your employer's policy before working on public Wi-Fi at all.
Phishing aimed at remote workers. Away from the office, you can't easily check a suspicious message with a colleague in person. CyberFence's Web Shield blocks known phishing sites while the VPN is connected, but it can't catch every new one, so report suspicious messages to your IT team.
A major healthcare breach started with remote access. UnitedHealth Group's CEO told the Senate Finance Committee that in February 2024, criminals used compromised credentials to remotely access a Change Healthcare Citrix portal that did not have multi-factor authentication. Change Healthcare later told HHS that about 192.7 million people were affected. The lesson is multi-factor authentication and protecting your login, not just encryption.
On hotel, airport and café Wi-Fi, connect first.
See CyberFence encrypt your connection on shared Wi-Fi, in under a minute.
Watch the Hotel. Airport. Café. film
Select play to load YouTube, then start the film in the player. YouTube processes data when loaded; its privacy policy applies.
Watch on YouTube (opens a new tab)
Read the video transcript
Is this network safe to use? You ask it at every stop on a trip.
At the hotel, turn on CyberFence, and your laptop's connection is encrypted through US-based servers. At the airport, the Network view on your phone shows the network you're on, and whether it's secured. At the café, one tap connects your iPad.
Sign in on each device with the same account.
Hotel. Airport. Café. CyberFence comes with you. Get protected today.
What HIPAA Actually Requires for Remote Access
HIPAA does not explicitly name VPNs in its text. What it does require, under the Security Rule's Technical Safeguards:
- Encryption of ePHI in transit (§164.312(e)(2)(ii)) — an addressable implementation specification. HHS explains that addressable doesn't mean optional: an organization must encrypt where it's reasonable and appropriate, or document why not and use an equivalent measure.
- Access controls — Unique user identification and authentication for anyone accessing ePHI
- Audit controls — Hardware, software, and procedural mechanisms to record access to ePHI
- Transmission security — Technical measures to protect ePHI from unauthorized access during transmission
A VPN is one way to encrypt traffic in transit: it creates an encrypted tunnel between your device and the VPN server. Most EHR and telehealth platforms also encrypt their own connections. Which remote-access tools you use for patient data is your employer's call, set in its risk analysis and policies, so use the tools it approves.
HHS has proposed changes to the Security Rule that would require encryption of ePHI at rest and in transit and multi-factor authentication, with limited exceptions. It's a proposal: the current rule remains in effect while HHS works on it.
What to Look for in a VPN for Remote Nursing
If your employer's policy allows a personal VPN for some of your work, here is what to evaluate:
Clear, Modern Encryption
Look for a VPN that uses modern, well-reviewed encryption and says clearly which protocols it uses. Ask the provider rather than assuming, and check whether your employer specifies what it accepts.
CyberFence encrypts your traffic between your device and its US-based VPN server, for the apps that go through the VPN while it's connected.
A Published No-Logs Policy
A VPN provider can see your connection to its servers, so read what it keeps. CyberFence's published privacy policy says it doesn't keep logs of your VPN activity. Read it and decide for yourself. CyberFence doesn't claim an independent audit of that policy.
US-Based Operation and Jurisdiction
For US healthcare workers, it helps to know which country's laws apply to your security vendors. Ask any VPN provider where it's based and where its servers are.
CyberFence is a US company with US-based servers.
Blocking Known Phishing Sites
Phishing is a common way into healthcare systems. Some VPNs, including CyberFence, also block known phishing and malware sites while connected, which helps when a convincing link slips through.
CyberFence's Web Shield blocks known malicious and phishing sites while the VPN is connected. It isn't antivirus and can't catch every new site.
Multi-Platform Coverage
Remote nursing can involve several devices: a laptop, a tablet and a phone for patient portal notifications. CyberFence works with iPhone, iPad, Android, Mac and Windows; check your plan's device allowance. On a work-managed device, ask IT before installing any VPN.
The Practical Setup for Remote Nurses
Setup takes a few minutes:
- Check your employer's policy — use the remote-access tools it approves for EHR and patient systems.
- Sign up on the CyberFence plans page
- Download CyberFence on the personal devices you use — laptop, phone, tablet. Check your plan's device allowance.
- Connect before you sign in — on shared Wi-Fi, turn the VPN on before opening your EHR, telehealth platform or patient messages, where your employer allows it.
- Check it's connected — CyberFence connects with one tap. Before a session, glance at the app to make sure it's on.
That quick check matters in a busy shift. One-tap connect keeps the VPN from adding friction, and it protects the apps that go through the VPN while it's connected.
Common Telehealth HIPAA Risks That a VPN Helps Prevent
Here are common telehealth risks for nurses, and where a VPN does and doesn't help:
Using unapproved platforms. A VPN doesn't make an unapproved platform acceptable. Use the telehealth tools your employer approves. A VPN only adds encryption between your device and the VPN server.
Working from shared networks. On a network you don't control, the VPN encrypts traffic between your device and the VPN server, so others on that network can't read it.
Storing patient data on personal devices. A VPN does not solve device-level storage issues. It encrypts data between your device and the VPN server while it's connected. Follow your employer's rules on where patient data may be stored.
Phishing leading to credential theft. Web Shield blocks known phishing sites while the VPN is connected. It can't catch every new site, so check the address before you sign in and use multi-factor authentication.
What the Liability Looks Like Without It
The consequences of HIPAA violations are not abstract. HHS's Office for Civil Rights enforces the Security Rule, and HHS has proposed tightening it. Your employer is the regulated organization, and its policies set what you must do.
For individual nurses, the practical risk is a breach that starts with your login or your device. Following your employer's remote-access policy, using multi-factor authentication and reporting anything suspicious quickly matter more than any single tool.
Protecting yourself starts with the same steps your organization requires: encrypted connections, verified access, and consistent security regardless of where you are working from.
The Bottom Line
Telehealth nursing is not going away — and neither is the responsibility to protect patient data wherever you work. HIPAA's transmission security requirements apply whether you are in the hospital or at your kitchen table. A VPN helps on the networks you don't control; your employer's policies and tools do the rest.
When you choose a VPN for the shared Wi-Fi you use, look for clear encryption details, a published no-logs policy, a provider you can identify, and blocking of known phishing sites. CyberFence offers US-based servers, a published no-logs policy and Web Shield, from $7.99 a month. It isn't a HIPAA compliance tool, so use it alongside your employer's approved systems.
Frequently Asked Questions
Does a VPN make me HIPAA compliant?
No. HIPAA's Security Rule applies to your employer as a regulated organization, and compliance depends on its risk analysis, policies and tools. A VPN is one way to encrypt traffic on networks you don't control.
Should I use my employer's VPN or a personal one?
Use your employer's VPN or remote-access tool for EHR and patient systems. A personal VPN like CyberFence is for your own devices on shared Wi-Fi, where your employer's policy allows it.
Do I need a VPN on my home Wi-Fi?
Less than on shared Wi-Fi. Your own router with a strong password is lower risk, and clinical platforms use HTTPS. A VPN still hides which sites you visit from your internet provider.
Does a VPN stop phishing?
Not on its own. CyberFence's Web Shield blocks known phishing sites while the VPN is connected, but no blocklist catches every new site. Multi-factor authentication helps most if a password is stolen.
Can I install CyberFence on a hospital-issued laptop?
Ask your IT team before you install it. Work-managed devices often have their own VPN and rules about extra software.
Read Next
Want to go deeper? Read how CyberFence protects other regulated industries , the CyberFence Teams product page , or CyberFence plans and pricing .