Cybersecurity for Healthcare Practices in Roanoke: HIPAA Security Basics
A plain-English guide to HIPAA security for Roanoke healthcare practices: risk analysis, MFA, encryption, backups, breach response and a 30-day plan.
It's a Tuesday morning at a small dental or physical therapy practice in Roanoke. The front desk can't open the scheduling system, the shared drive is full of files with strange extensions, and a ransom note is sitting on the desktop of the billing workstation. Patients are already in the waiting room. If that picture makes your stomach drop, this guide on HIPAA security for Roanoke healthcare practices is for you.
Most small practices aren't breached by some brilliant hacker. It's usually a reused password, a missed update, or a backup nobody had tested. The good news is that the HIPAA Security Rule, for all its legal language, mostly asks you to do the practical things that stop those attacks.
My partner Mukesh has spent 25 years in cybersecurity, and I've spent 15 building and running networks. This post is the plain-English version of what we tell practice managers and owners in the Roanoke Valley when they ask, "What do we actually need to do?" It isn't legal advice, so please confirm anything compliance-related with your attorney or compliance advisor.
In this guide
- What the HIPAA Security Rule actually asks of a small practice
- Start with a real security risk analysis
- The technical safeguards that matter most
- People and paperwork: the administrative side
- Backups, downtime and breach response
- What's changing: the proposed Security Rule update
- A 30-day HIPAA security plan for Roanoke practices
- Frequently asked questions
What the HIPAA Security Rule actually asks of a small practice
The Security Rule covers electronic protected health information, or ePHI. That's anything in your EHR, practice management system, email, scanned intake forms, billing exports and even the spreadsheet someone keeps on their desktop.
The rule groups its requirements into three buckets:
- Administrative safeguards: risk analysis, policies, workforce training, assigning a security official, managing vendors.
- Physical safeguards: controlling who can get to servers, workstations and devices, and how you dispose of old hardware.
- Technical safeguards: access controls, audit logs, integrity protections and secure transmission.
The rule is "scalable," which means a three-provider clinic isn't expected to run like a hospital system. But scalable doesn't mean optional. You still need to look at your risks, decide what's reasonable, and write down why.
Who this applies to
If you're a covered entity (a provider who bills insurance electronically, a health plan or a clearinghouse), it applies to you. It also applies to your business associates: your IT provider, your cloud EHR vendor, your billing company and anyone else who touches ePHI on your behalf. Each of them should have a signed business associate agreement (BAA) with you.
Start with a real security risk analysis
If I could get every small practice to do one thing, it would be a proper risk analysis. It's the foundation of the whole rule, and it's the item regulators keep asking about after a breach. The HHS Office for Civil Rights (OCR) has run a dedicated enforcement initiative focused on risk analysis, and many recent settlements cite a missing or incomplete one.
A risk analysis is not a checkbox form you fill out once. It's an honest look at where your ePHI lives, what could go wrong, and how likely and how bad each problem would be.
What a useful risk analysis covers
- An inventory of where ePHI lives. EHR, PM system, email, file shares, laptops, phones, scanners, fax-to-email services, backup drives and cloud apps.
- Who can access it. Every user account, including former employees and shared logins.
- Threats and weak spots. Phishing, ransomware, lost laptops, unpatched systems, weak Wi-Fi, a vendor breach.
- Current controls. What you already have in place, such as MFA, encryption, backups and antivirus.
- Risk ratings. Likelihood and impact for each issue, so you know what to fix first.
- A remediation plan. Specific fixes, owners and target dates.
The free HHS Security Risk Assessment (SRA) Tool is a reasonable starting point. Where people get stuck is the technical part: open ports, missing patches and old accounts that are still active.
The technical safeguards that matter most
You can spend a fortune on security tools and still miss the basics. In my experience, these six controls do the heavy lifting for a small practice.
1. Multi-factor authentication everywhere it counts
Turn on MFA for email, your EHR, remote access and any admin accounts. Stolen passwords are one of the most common ways attackers get in, and MFA stops a large share of those attempts. If a front-desk employee clicks a bad link, MFA is often the difference between a scare and a breach. (If that does happen, here's what to do in the first hour after someone clicks a phishing link.)
2. Encryption on laptops, phones and email
Encrypt every laptop and any phone that gets work email. Use BitLocker on Windows and FileVault on Macs. Under the HIPAA breach rules, a lost device that was properly encrypted is generally treated very differently from one that wasn't, so this one control can save you a breach notification.
For email, use your platform's secure or encrypted message option when sending ePHI outside the practice.
3. Patching and supported operating systems
Unsupported Windows versions and out-of-date software are open doors. Set a monthly patch routine for workstations, servers, firewalls and any imaging or practice software. If a piece of clinical equipment can't be updated, isolate it on its own network segment.
4. Endpoint protection that actually watches behavior
Traditional antivirus looks for known bad files. Modern ransomware often doesn't trip it. An endpoint detection and response (EDR) tool watches for suspicious behavior and can isolate a machine before encryption spreads.
5. Separate networks for patients, staff and devices
Guest Wi-Fi in the waiting room should never sit on the same network as your EHR workstations. Put patient Wi-Fi, staff computers, and medical or IoT devices on separate networks with rules between them. This limits how far an attacker can move if one device is compromised.
6. Unique logins and audit logs
Every person gets their own account, with no shared "frontdesk" login. Turn on audit logging in your EHR and email platform, and have someone glance at it monthly for odd sign-ins or after-hours access.
People and paperwork: the administrative side
Technology is only half the job. A lot of HIPAA security comes down to people and documentation.
Name a security official
HIPAA requires a designated security official. In a small practice this is often the practice manager, sometimes with help from an outside IT partner. The point is that one person owns the program and knows where everything is.
Train your team, then train them again
Train staff when they're hired and at least once a year after that. Short, frequent refreshers work better than a single long annual video. Focus on what your team actually sees:
- Phishing emails that look like payer notices, EHR vendor alerts or package deliveries
- Phone calls from someone "from IT" asking for a password or a remote session
- What to do with a lost phone or laptop
Manage your business associates
Keep a list of every vendor that touches ePHI, confirm each has a signed BAA, and know how to reach them in an emergency. Ask your IT provider how they secure their own remote access tools.
Handle offboarding the same day
When someone leaves, disable their accounts that day: EHR, email, VPN, door codes and any shared passwords they knew. Old accounts are a common way in.
Backups, downtime and breach response
The Security Rule requires a contingency plan: data backups, disaster recovery and a way to keep operating in an emergency. For a practice, this is where ransomware gets decided.
Backups that survive ransomware
Follow the 3-2-1 approach: three copies of your data, on two types of media, with one copy offsite and ideally immutable or offline. Then test restores on a schedule. A backup you've never restored is a hope, not a plan. Our post on the 3-2-1 backup rule and how to test your backups has a simple testing routine.
If your EHR is cloud-hosted, ask the vendor what they back up, how long they keep it, and what you're responsible for. Local files, scanned documents and email are often on you.
A downtime plan your front desk can follow
Write a one-page downtime procedure: how to check patients in, where paper forms are kept, who to call, and how to record visits for later entry. Keep a printed copy at the front desk, because you won't be able to open the file share during an outage.
Know your breach notification clock
Under the HIPAA Breach Notification Rule, affected individuals must generally be notified without unreasonable delay and no later than 60 days after a breach is discovered. Breaches affecting 500 or more people also require notice to HHS within that window and to prominent media in the affected area. Smaller breaches are logged and reported to HHS annually. Virginia has its own breach notification requirements as well, including for medical information, so involve your attorney early to confirm which rules apply to your situation.
Keep an incident contact list ready: your IT provider, your cyber insurer's hotline, your attorney and your EHR vendor. Call your insurer early, since many policies require their approved responders.
What's changing: the proposed Security Rule update
In January 2025, HHS published a proposed rule that would significantly update the HIPAA Security Rule. Among other things, it would remove the distinction between "required" and "addressable" specifications and would require:
- Multi-factor authentication
- Encryption of ePHI at rest and in transit
- A written technology asset inventory and network map
- Regular vulnerability scanning and annual penetration testing
- The ability to restore critical systems within 72 hours
As of this writing, that rule has not been finalized. HHS's most recent regulatory agenda moved it to its long-term list with a target date in 2027, and legal commentators expect that some proposals may change or be dropped in the final version. Please check with your attorney or compliance advisor for the current status before you plan around specific deadlines.
My advice: don't wait for the final rule. Nearly everything on that list is already a good idea, and much of it is already expected by cyber insurance carriers. If you're filling out a renewal soon, our guide on how to answer your cyber insurance security questionnaire will look familiar.
A 30-day HIPAA security plan for Roanoke practices
If you're a practice manager staring at all this and wondering where to start, here's a realistic first month.
Week 1: Find out where you stand
- List every system, device and vendor that touches ePHI
- Pull a list of all user accounts and disable any that belong to former staff
- Confirm you have a signed BAA with each vendor
- Name your security official if you haven't
Week 2: Close the biggest doors
- Turn on MFA for email, EHR, remote access and admin accounts
- Confirm every laptop is encrypted
- Check that Windows and key software are on supported, patched versions
- Separate guest Wi-Fi from your clinical network
Week 3: Make sure you can recover
- Verify your backups are running and at least one copy is offsite or immutable
- Do a test restore of a real file and a real system
- Write a one-page downtime procedure and print it
Week 4: Document and train
- Complete or update your security risk analysis using what you learned
- Run a short phishing and social engineering training session
- Write down your incident contact list, including your insurer's breach hotline
- Schedule your next review, so this doesn't fade after the first month
You won't finish everything in 30 days. The goal is to fix the highest risks first and document a plan for the rest.
Frequently asked questions
Does HIPAA require a small medical practice to do a risk assessment every year?
The Security Rule requires an accurate and thorough risk analysis and ongoing review, but it doesn't spell out a fixed annual schedule. In practice, most advisors recommend reviewing it at least once a year and whenever something significant changes, such as a new EHR, a move or a security incident. Ask your compliance advisor what cadence makes sense for you.
Is Microsoft 365 or Google Workspace HIPAA compliant?
Both Microsoft and Google will sign a BAA for eligible business plans, but signing the BAA doesn't make your setup compliant on its own. You still need to configure it properly: MFA, appropriate sharing settings, audit logging and encryption options for sending ePHI. The responsibility for how it's used stays with you.
Do we have to encrypt our laptops under HIPAA?
Under the current rule, encryption is an "addressable" specification, which means you must implement it or document why an equivalent alternative is reasonable. For laptops, it's hard to justify not encrypting, and a lost encrypted device is generally treated far more favorably under the breach rules. The proposed Security Rule update would make encryption a firm requirement.
What happens if a small practice has a HIPAA breach?
You'll need to investigate, contain the incident, and follow the notification rules for patients, HHS and possibly the media and state regulators. OCR may open an investigation, and penalties or settlements are more likely when the practice can't show a risk analysis or reasonable safeguards. Call your attorney and cyber insurance carrier early.
How much does HIPAA security cost for a small practice?
It varies widely with the number of users, locations and systems. Many of the most important controls, like MFA, encryption and separate guest Wi-Fi, cost little beyond setup time, while things like EDR, managed backups and ongoing monitoring are commonly priced per user or per device each month. A risk analysis helps you spend money on the gaps that matter instead of guessing.
Get a clear picture of your practice's security
Most practices we talk to are doing some things well and have a few gaps they didn't know about. The hard part is knowing which is which.
If you run a healthcare practice in Roanoke or anywhere in Virginia and want a second opinion, we offer a free cybersecurity assessment. We'll look at your network, accounts, backups and endpoint protection, then give you a plain-English list of what to fix first. There's no pressure and no obligation. You can request your free assessment here.
Related reading
- The 3-2-1 Backup Rule Explained (and How to Test Your Backups)
- Network Segmentation for Small Businesses: A Practical Guide
- Cybersecurity for Roanoke Small Businesses: 10 Steps to Protect Your Company




