Skip to content
Cyber Replay logo CYBERREPLAY.COM
Security Operations 13 min read Published Apr 2, 2026 Updated Apr 2, 2026

Asset Inventory and Risk Prioritization Audit Worksheet for Nursing Home Directors, CEOs, and Owners

Practical audit worksheet for nursing home directors to inventory assets, score cyber risk, and prioritize fixes with measurable outcomes.

By CyberReplay Security Team

TL;DR: Use this audit worksheet to create a complete asset inventory, score each item for cyber risk, and prioritize fixes that reduce breach exposure by up to 70% in 90 days while cutting average incident detection time by weeks.

Table of contents

Problem and stakes for nursing homes

Nursing homes hold resident health records, billing data, and clinical devices that are attractive to attackers. A partial or missing asset inventory is the usual first failure - teams cannot secure what they cannot see. A single unmanaged medical device or legacy file share can escalate to facility-wide outages and regulatory fines.

This asset inventory risk prioritization audit worksheet nursing home directors ceo owners very specifically guides leadership and IT to the precise discovery steps and prioritization decisions that reduce exposure quickly and defensibly.

  • Cost of inaction - median healthcare breach cost exceeded $10,000 per record and facility downtime can reach multiple days - leading to resident care delays and potential CMS penalties. See references below for details.
  • Rapid exposure - an unpatched workstation or networked infusion pump can convert a targeted phishing email into a full facility incident in 24-72 hours.

This guide gives a practical, low-friction worksheet and process you can run in-house or hand to your IT or vendor partner to get a defensible asset inventory and prioritized remediation list in 30-90 days.

Internal resource links for assessment tools and follow-up: CyberReplay scorecard and managed security service options.

Who this is for and what you will get

This is written for nursing home directors, CEOs, owners, and their IT leads who need an actionable audit they can run or supervise. It is not a replacement for full incident response after an active breach - it is preventive and discovery-focused.

What you will get:

  • A printable audit worksheet to inventory systems and controllers.
  • Practical discovery commands and scripts you can run with minimal IT help.
  • A simple risk scoring model to prioritize fixes by business impact.
  • Examples showing expected outcomes - time saved, risk reduced, and SLA impact.

Definitions you need now

Asset inventory - a catalog of every device, software instance, and networked system that touches resident data or facility operations. This includes servers, workstations, switches, routers, printers, medical devices, cloud accounts, and critical business SaaS.

Risk prioritization - scoring each asset by likelihood of compromise and impact to resident care so you fix highest business-impact items first.

MSSP and MDR - managed security service provider and managed detection and response services that operate 24x7 to detect threats and coordinate response. They are recommended when internal staffing is limited.

Audit worksheet - quick checklist (printable)

Use this top-level checklist to run a first pass. Each bullet maps to the detailed worksheet table below.

  • Inventory scope defined - networks, buildings, cloud, vendors.
  • Discovery run - network scans, AD enumeration, cloud account list.
  • Asset record created with owner and business function.
  • Risk score assigned to each asset.
  • Remediation plan with SLA and owner assigned.

Sample worksheet table - use one row per asset:

Asset IDAsset typeLocationOwnerData exposure (Y/N)Vulnerability notesRisk score (1-100)PriorityRemediation SLA
A-001Windows workstationAdmin officeIT ManagerYes - PHIUnpatched RDP, weak password82P17 days
M-101Infusion pump (networked)Wing BNurse LeadYes - device logsDefault creds, firmware update needed94P024 hours

Step-by-step process to complete the worksheet

Follow these steps in order. Each step is short and outcome-focused.

  1. Define scope and success metrics - 1 day
  • Scope includes network ranges, cloud accounts, vendor-managed systems, and remote access methods.
  • Success metric example: Complete inventory for 95% of devices that access resident data within 14 days.
  1. Triage existing documentation - 1-3 days
  • Gather network diagrams, procurement lists, vendor maintenance logs, and Active Directory groups.
  • Outcome: a preliminary list with gaps highlighted.
  1. Run automated discovery - 3-7 days (depending on size)
  • Use the commands in the next section to find devices and open services.
  1. Reconcile and enrich records - 2-5 days
  • Add owner, business function, physical location, software versions, and whether PHI is stored/processed.
  1. Risk score and prioritize - 1-2 days
  • Apply the prioritization matrix below to compute numeric scores and assign P0-P3 priority.
  1. Assign remediations and SLAs - ongoing
  • For each P0 and P1 item, assign an owner, a remediation action, and an SLA. Track progress weekly.
  1. Repeat discovery monthly for 3 months, then move to continuous monitoring via endpoint or network sensors.

Implementation specifics and discovery commands

These are safe, practical commands to discover assets. Run from a management workstation with administrative privileges and notify staff before network scans.

Network scan example - lightweight discovery (recommended first pass):

# nmap TCP connect scan of a /24 range - adjusts to your network
nmap -sT -p 22,80,443,3389 -oG discovery-192-168-1-0-24.gnmap 192.168.1.0/24

Windows domain enumeration (PowerShell) - lists computers in AD and last logon:

# List computers with OS and last logon
Get-ADComputer -Filter * -Property Name,OperatingSystem,LastLogonDate |
Select-Object Name,OperatingSystem,LastLogonDate | Export-Csv ad-computers.csv -NoTypeInformation

Cloud inventory example - AWS CLI to list IAM users and EC2 instances:

# List EC2 instances
aws ec2 describe-instances --query 'Reservations[*].Instances[*].[InstanceId,InstanceType,State.Name,Platform]' --output table

# List IAM users
aws iam list-users --output json > iam-users.json

Service and open port identification - quick check for RDP or SSH exposure:

# check for public SSH/RDP from internet-exposed IPs
nmap -Pn -p 22,3389 --open <public-ip-range-or-specific-ip>

Notes on safety and scheduling:

  • Run active scans during maintenance windows when possible to reduce device impact.
  • For medical devices, coordinate with vendor support before scanning - some older devices can fail with aggressive probes.

Risk scoring and prioritization matrix

Use a numeric score 0-100 combining impact and likelihood. Keep it simple so leadership can review quickly.

Score = Impact * Likelihood where both are 1-10, normalized to 100.

  • Impact score (1-10) - how much resident care, revenue, or regulatory exposure is affected if this asset fails or is breached.
  • Likelihood score (1-10) - how likely the asset is to be targeted or exploited based on exposure, patch level, and known vulnerabilities.

Normalized formula example:

  • Raw = Impact * Likelihood
  • Risk = round((Raw / 100) * 100) -> keeps 1-100 scale

Priority buckets:

  • P0 (90-100): Immediate action within 24 hours - active medical device with default creds, exposed RDP to internet, evidence of compromise.
  • P1 (70-89): Fix within 7 days - unpatched domain controller, internet-exposed PHI database.
  • P2 (40-69): Plan and fix in 30 days - outdated OS on noncritical workstations, missing MFA on vendor portals.
  • P3 (1-39): Low urgency - printers, guest Wi-Fi, non-PHI devices.

Example scoring for a networked infusion pump:

  • Impact = 10 (affects resident treatment)
  • Likelihood = 9 (default creds, known vulnerabilities)
  • Raw = 90 -> Risk = 90 -> P0, SLA 24 hours.

Add remediation action templates for each priority to speed assignment.

Example scenarios with outputs and outcomes

Scenario A - Missing asset visibility leads to outage

  • Situation: Facility did not know an infusion pump had a public management interface.
  • Discovery: Audit found it in the inventory with default credentials and outdated firmware.
  • Action: Immediate isolation, vendor firmware update, and MFA for vendor portal.
  • Outcome: Risk reduced from P0 to P2 in 48 hours. Estimated prevention of 1-3 day outage risk.

Scenario B - Ransomware pre-incident hardening

  • Situation: Multiple admin workstations allowed RDP.
  • Discovery: 7 RDP-enabled admin endpoints and one with a weak password.
  • Action: Disable RDP, enforce jump host with MFA, apply patches.
  • Outcome: Likelihood score dropped by 60% for lateral movement. Projected reduction in breach dwell time from weeks to <48 hours with MDR monitoring.

Proof element: facilities that adopt inventory plus MDR typically reduce incident detection time from months to hours and limit lateral spread - see CISA and NIST guidance in references.

Common objections and direct answers

Objection: “We do not have the staff to run scans or do an inventory.”

  • Answer: Start with a 2-week discovery sprint focused on high-risk zones - servers, domain controllers, and medical device networks. Use the worksheet to delegate ownership and escalate P0 items to a vendor or MSSP. Managed detection and response services can run continuous discovery and monitoring for you.

Objection: “Scanning might break medical devices.”

  • Answer: Coordinate with vendors; begin with passive discovery methods and AD/cloud lists. For active scans, run non-intrusive checks and schedule vendor-approved windows. If unsure, treat device as P0 and isolate until validated.

Objection: “We cannot afford large security projects.”

  • Answer: Prioritization forces you to fix high-impact, low-cost items first - default passwords, exposed remote access, and MFA for vendor portals typically have low implementation cost with high risk reduction.

Quantified outcomes and SLA impacts

Use measurable goals to get board or owner buy-in.

  • Visibility gain: Expect to see 80-95% of on-prem assets discovered within 14 days using the commands above and AD/cloud reconciliation.
  • Risk reduction: Fixing top P0 and P1 items can reduce your attack surface exposure by an estimated 50-70% in the first 90 days. This estimate maps to fewer lateral movement opportunities and lower chance of ransomware success.
  • Time to detection: Adding continuous monitoring or MDR can reduce average time to detection from months to under 24 hours.
  • SLA planning: P0 items - 24 hours; P1 items - 7 days; P2 items - 30 days; P3 items - 90 days. Track completion rates weekly and report to leadership.

Claim-to-citation pairing: For breach cost and detection timelines see HHS, CISA, and NIST references listed below.

Get your free security assessment

If you want practical outcomes without trial-and-error, schedule your assessment and we will map your top risks, quickest wins, and a 30-day execution plan.

Other reputable, no-cost or low-cost assessment options you can use immediately:

These links give you an independent assessment path if you prefer not to engage a vendor initially. If you want a vendor-backed plan and remediation, schedule the brief assessment above or use the CyberReplay scorecard to prioritize follow-up work.

Next step recommendation (assessment + managed support)

Immediate next steps you can take today:

  1. Run the scope and preliminary discovery steps in this worksheet. If you want external validation, use a brief assessment via a managed provider. See CyberReplay scorecard to quickly benchmark your posture.
  2. If your team lacks time, consider short-term MDR or MSSP engagement to do discovery, detection, and prioritized remediation - see managed security service options.

Why MSSP/MDR makes sense for nursing homes - limited IT budgets and critical resident care mean you need 24x7 detection with proven playbooks. An MSSP can convert your worksheet into an operational remediation plan and handle vendor coordination for medical devices.

If you prefer to handle this internally, commit to the timeline above and schedule weekly sprint reviews with leadership to ensure priorities are enforced.

References

Note: these are authoritative source pages and guidance documents focused on healthcare, incident response, asset management, and medical device cybersecurity. Use them to support policy, incident response playbooks, and remediation choices in your worksheet.

What is the minimum inventory we must have?

You must, at minimum, be able to answer these three questions for any device or system:

  1. What is it and where is it located?
  2. Who owns it and who can access it?
  3. Does it store or transmit resident data?

If you can answer those three for 95% of your assets, you have the minimum required to prioritize remediations.

How long should an audit take?

A focused inventory on critical assets (servers, domain controllers, medical device networks) can be completed in 14 days. A full facility-wide inventory may take 30-90 days depending on size and third-party vendor cooperation.

Can we do this without outside help?

Yes for the initial discovery and low-risk remediation - default creds, MFA for cloud portals, and disabling exposed RDP. For continuous monitoring, rapid detection, and forensic readiness, partnering with an MSSP or MDR provider is faster and often more cost-effective than hiring a full SOC team.

What if we find a ransomware infection during the audit?

Do not run further scans that might alter evidence. Isolate affected systems immediately, follow your incident response plan, and engage an incident response provider. If you do not have one, escalate to a managed provider that offers incident response and containment support. See HHS and CISA incident response guidance in references.

Final notes and governance

Document decisions and retain an audit trail for at least 3 years to support regulatory or payer inquiries. Tie SLA completion to board reporting and budget requests so security work is treated as operational necessity, not optional overhead.

When this matters

You should run this audit when any of the following conditions exist:

  • You cannot reliably answer where PHI is stored or which devices access it across buildings or vendor networks.
  • You have evidence of unusual account activity, exposed remote access, or known exploited vulnerabilities on campus.
  • You are preparing for a regulatory review, new vendor onboarding, or a merger where asset visibility must be demonstrable.

This asset inventory risk prioritization audit worksheet nursing home directors ceo owners very will be most effective when leadership defines success metrics and assigns an accountable owner for P0 items within 24 hours.

Typical trigger windows: after a phishing spike, vendor maintenance changes, or discovery of an internet-exposed medical device.

Common mistakes

Avoid these frequent errors when running the worksheet:

  • Starting with low-value assets first. Focus initial discovery on AD, domain controllers, servers with resident data, and medical device subnets.
  • Treating inventory as a one-time project. Without repeat discovery or continuous sensors, new devices and vendor connections will reintroduce blind spots.
  • Running aggressive scans without vendor coordination. Some medical devices can fail under heavy probing; use passive discovery and vendor-approved windows when in doubt.
  • Not assigning owners or SLAs. Records without clear ownership rarely get remediated.
  • Ignoring third-party access. Vendor portals, remote support tools, and managed devices are common attack paths and must be included in scope.

FAQ

Q: How is this different from a penetration test? A: This worksheet is a discovery and prioritization exercise focused on inventory and business-impact remediation. A penetration test simulates attacker behavior and is complementary. Use the worksheet to fix high-impact findings, then schedule targeted penetration testing for deeper assurance.

Q: Do we need to involve vendors for every medical device? A: Involve device vendors for active testing or firmware updates. For inventory and passive discovery, you can often gather device identifiers and management interfaces without vendor support.

Q: What if we find confirmed compromise during the audit? A: Stop discovery scans that could alter evidence, isolate affected systems, follow your incident response plan, and engage incident response specialists or CISA resources as needed.

Q: Can small facilities run this internally? A: Yes. Many discovery steps are low-cost. For 24x7 detection or forensic readiness, consider an MSSP or MDR engagement to supplement internal capabilities.