Nursing Home Cybersecurity Checklist: 12 Checks for Administrators

A per-diem nurse resigns on a Friday. HR emails IT: “Please disable her access to everything.” By lunch her laptop login and email are shut off. But her PointClickCare account is managed by someone in the building, the therapy documentation system by someone else, her phone extension sits in the phone system, and her key card lives in the door access software. Each piece has a different owner, and nobody’s list covers all of them.

That is what most nursing home cybersecurity gaps look like up close. They are rarely exotic. They sit in the seams between systems that different people own: the EHR vendor, the pharmacy, the phone company, HR, and IT. A useful checklist has to follow those seams, not just restate HIPAA.

The short answer: what a nursing home cybersecurity checklist should cover

Start with the floor HHS has already published. The HHS Healthcare and Public Health Cybersecurity Performance Goals are voluntary, and their ten “Essential” goals are a sensible minimum for any skilled nursing facility:

  1. Mitigate known vulnerabilities
  2. Email security
  3. Multifactor authentication
  4. Basic cybersecurity training
  5. Strong encryption
  6. Revoke credentials for departing workforce members, including contractors, affiliates and volunteers
  7. Basic incident planning and preparedness
  8. Unique credentials
  9. Separate user and privileged accounts
  10. Vendor/supplier cybersecurity requirements

Then apply each one to how a nursing home actually runs: shared nurse-station workstations, a large per-diem and agency workforce, a cloud EHR you don’t administer, vendor-owned devices on your network, and a building that never closes. The checks below do that.

1. Offboarding: one list, every system, a named owner

Check: When someone leaves, does one checklist name every system they could reach and the person responsible for each one?

In the support requests we handle for skilled nursing buildings, a single departure routinely touches the laptop login, email, email distribution groups, shared files, the phone extension, the key card, and clinical applications such as the EHR and therapy software. The clinical apps are often administered by facility staff, not the IT provider. So IT can close email and Windows the same day while EHR access stays open until someone else gets to it.

Fix it with a written offboarding list that names an owner for each system, a same-day target for per-diem and agency staff, and a confirmation back to HR when every line is done. HHS’s goal on departing workforce members explicitly covers contractors, affiliates and volunteers, not just employees.

Add a quarterly review of accounts with no recent sign-in. Accounts that should have been closed months ago do turn up.

2. Unique logins at the nurses’ station

Check: Does every person who charts sign in as themselves, everywhere?

Shared “nurse station” Windows logins feel efficient during a med pass, and they make two things impossible: knowing who did what, and cutting off one person without locking out the whole unit. HHS lists unique credentials as an essential goal for exactly this reason.

The tradeoff is real. Fast sign-in matters on a busy floor. The answer is short auto-lock timers plus quick user switching on station computers, not a shared account. Pair it with the screen-lock and automatic logoff controls covered in our guide to HIPAA technical safeguards.

3. MFA, with a reset path that works at 2 a.m.

Check: Is MFA on for email, remote access and the EHR, and can a locked-out nurse get back in during a night shift?

PointClickCare told customers it would enforce multifactor authentication for all remote users starting in September 2025, with POC, eMAR, mobile apps and SSO logins left for a later phase. That was the right move. It also created a new failure point.

Since then, many of the PointClickCare tickets we see are MFA problems: a nurse gets a new phone and the authenticator no longer matches, codes are rejected until the account locks, or a first sign-in forces MFA setup at the start of a shift. In one case the lockout stopped a medication pass until access was restored.

So the checklist item isn’t just “turn on MFA.” It is:

  • Know who in your building holds PointClickCare security admin rights and can reset MFA.
  • Make sure that reset is reachable on nights and weekends, not only by the day-shift administrator.
  • Tell staff to re-enroll MFA before they trade in a phone.
  • Keep email MFA on too. The mailbox is where phishing lands first.

4. Separate admin accounts

Check: Does anyone browse the web or read email while signed in with administrator rights?

The administrator’s or DON’s everyday account should not be a domain or Microsoft 365 admin. Admin work goes through a separate account used only for that. If a phishing email takes over a normal account, the attacker doesn’t get the keys to everything. This is another HHS essential goal, and it costs almost nothing.

5. Email security and a habit of verifying

Check: Are spoofing protections and filtering in place, and do staff know how to check a message before acting on it?

Healthcare email is full of real vendor notices that look like phishing, and phishing that looks like vendor notices. Even the PointClickCare MFA announcement arrived as an external email with “Action Required” in the subject and a stack of links. The right reflex was the one the administrator used: forward it to IT, which confirmed from the message headers that it was legitimate.

Make that the standing rule. Anything asking for credentials, payment changes or urgent action gets verified through a known phone number or by IT before anyone clicks. Our posts on digital social engineering and baiting attacks cover the lures staff actually see.

6. Vendor-owned devices on your network

Check: Do you have a list of every device on your network that you don’t control, and who patches each one?

Pharmacy-supplied med cart laptops are the clearest example. We have seen an eMAR cart laptop where administrator access sat behind the pharmacy’s own account, so the facility’s IT provider could not install endpoint protection or manage updates without the pharmacy’s credentials. The same pattern shows up with phone system equipment, ECG workstations and other vendor-installed systems.

Those devices touch resident data and sit on your network, but their security depends on someone else. For each one, get answers in writing: who patches it, who protects it, how the vendor connects remotely, and how you’ll know if it’s compromised. If the vendor can’t answer, isolate the device on its own network segment and push for a replacement. HHS lists vendor and supplier cybersecurity requirements as an essential goal and asset inventory as an enhanced one.

7. Network segmentation: residents, staff, clinical, vendors

Check: If a resident’s laptop or a guest phone is infected, can it reach a nurse-station PC?

Resident and guest Wi-Fi should never share a network with clinical workstations. Nurse call, door access, cameras and vendor devices each belong on their own segment, with only the traffic they need allowed through. HHS’s enhanced goal on segmentation exists to limit how far an attacker can move after getting in.

Our free nursing home Wi-Fi check walks through the resident and staff side, and our post on how nurse call systems work covers why nurse call traffic needs its own lane.

8. Patching what faces the internet

Check: Are your firewall, VPN and remote access tools on current firmware and software?

HHS’s first essential goal is mitigating known vulnerabilities, with emphasis on assets directly reachable from the internet. In a nursing home that usually means the firewall, any VPN, remote support tools, and the phone system. These are what attackers scan for. Workstations matter too, but an unpatched firewall is a front door.

9. Backups you have actually restored, and downtime you have practiced

Check: When did you last restore something from backup, and when did staff last chart on paper during a drill?

Your EHR is probably hosted by the vendor, so the chart itself doesn’t live on your servers. An attack on your building can still take out the workstations, printers, scanned documents, shared drives and sometimes the phones that staff use to reach the chart. Backups of local data need to be offline or immutable, and restores need to be tested, not assumed.

Equally important is what happens when the EHR is unreachable for any reason. Our PointClickCare outage checklist and the free downtime readiness check cover the paper forms, MAR printouts and communication plan. This overlaps with what surveyors look at under the CMS emergency preparedness rule.

10. An incident plan with names and phone numbers

Check: If screens lock up with a ransom note at 11 p.m. on a Saturday, does the charge nurse know exactly who to call?

A plan that lives in a binder in the administrator’s office doesn’t help the night shift. The plan needs names and phone numbers for the administrator, the IT provider, the EHR vendor, the cyber insurance carrier and legal counsel, plus the first steps: disconnect affected machines from the network, leave them powered on, and start downtime procedures. Run a tabletop at least once a year. Our post on how ransomware hits a nursing home walks through the first hour and the first week.

11. The HIPAA risk analysis that ties it together

Check: Does a current, written security risk analysis cover all of the above, with a plan for each gap?

Every item on this list should appear in your HIPAA security risk analysis, with an owner and a date. Without that document, a facility can be doing good work and still be unable to prove it after an incident. Our page on the HIPAA risk assessment for nursing homes explains what a complete one includes.

12. The physical side

Check: Is the network closet locked, and does anyone know who has the key?

A switch in an unlocked closet next to the laundry is a cybersecurity problem. Treat it like the medication room: limited keys, a log, and no storage clutter. More in our post on physical security in nursing homes.

What’s coming: the proposed HIPAA Security Rule

HHS proposed a major rewrite of the HIPAA Security Rule in a notice published January 6, 2025. As of HIPAA Journal’s October 2026 update, no final rule has been issued, the final rule has been pushed to at least July 2027, and the administration had not yet decided whether to finalize it.

The proposal would require, among other things:

  • MFA for access to ePHI, with limited exceptions
  • Encryption of ePHI at rest and in transit, with limited exceptions
  • An asset inventory and network map, reviewed at least every 12 months
  • Written procedures to restore data within 72 hours
  • Vulnerability scans at least every 6 months and penetration tests at least every 12 months
  • Written verification of business associates’ technical safeguards, at least every 12 months

Our view: don’t wait for it. Nearly everything on that list is already on the HHS performance goals and this checklist. If the rule is finalized, facilities that already work this way will have far less to do. If it isn’t, they are still safer.

Who owns each check

Most checklist failures are ownership failures. Before you call any item done, write down who owns it and what proof you keep.

Check Usually owned by Proof to keep
Offboarding across all systems HR, IT, EHR admin Completed offboarding list per departure
Unique logins and auto-lock IT, DON Workstation settings, account list
MFA and after-hours reset IT, EHR admin Who can reset, and how to reach them
Separate admin accounts IT List of admin accounts and their users
Email security and verification IT, all staff Filtering settings, training records
Vendor-owned devices Administrator, IT, vendors Device list with patch and access owner
Network segmentation IT Current network map
Internet-facing patching IT Firmware and patch records
Backups and downtime drills IT, DON Restore test results, drill sign-in sheets
Incident plan Administrator Contact list, tabletop notes
Risk analysis Administrator, IT Dated risk analysis and remediation plan
Network closet security Maintenance, administrator Key log

Where to start

If you can only do three things this month, do these: confirm that offboarding closes every system the same day, make sure an MFA reset is reachable on the night shift, and list every vendor-owned device on your network. Those three cover the seams described above.

If you’d like a second set of eyes on this list for your building, RDE Technologies works with skilled nursing facilities on exactly these problems. See how we approach IT for skilled nursing facilities, or contact us to talk it through.

Share this article

Share on Facebook
Share on Twitter
Share on Linkdin
Share on Pinterest

Leave a comment

Find out what your IT really needs.

A free assessment of your network, backups and security, with a written report of what we found. No obligation.