Keystone Security: Connecting Medical Devices Without Adding Risk

Connected medical devices on a hospital network

Just as arches need a keystone to keep them upright, so medical device networks can fail due to a single weak device.

Hospitals and clinics rely heavily on connected devices to deliver patient care. Infusion pumps, monitors, imaging and lab analysers all connect to the network. This is essential to give the Care Team the right information. But we must make sure these devices are secure. Securing enterprise networks in healthcare means looking at every one of them.

How Medical Devices Are Vulnerable

Medical devices are designed to last. Often they last between 10 and 20 years. This means security often isn't considered during the initial design.

Issues commonly found include:

  • Out of date operating systems.
  • Default passwords that can't be changed.
  • Out of date protocols (data not encrypted).
  • Little to no logging.

Devices aren't always visible. Monitors and scanners can sit in the background for years. These are exactly what attackers will target.

Like the fences in Jurassic Park, if no one is monitoring them, they will be compromised. Likewise, if a device is not making any noise, it can still be compromised.

We can't just treat them like computers in an office. If we force a reboot on a pump, it becomes a patient safety incident. We have to consider the clinical requirements.

Create an Inventory of Your Devices

This needs to start with creating an inventory. Keep track of:

  • Manufacturer, model and type.
  • OS and firmware version.
  • IP address and room.
  • Department owner.
  • Vendor supported.

Use passive discovery tools to identify devices on your network. This means you can listen in on the traffic without causing any issues. Avoid actively scanning, as this may break fragile devices.

Perform this task regularly. Devices may move between rooms, and new devices often come in. An inventory done once will quickly become out of date.

Segment Before Patching

Many teams will want to patch devices first. For medical devices, it should be done the other way round.

Segment your network. This will help protect devices that can't be patched. It also reduces the impact if they do have an issue.

Put your medical devices into their own zones. This will separate them from office computers, guest wifi and general devices.

If there is a malware attack on your front desk computer, it will be caught at the segment and will never reach the ventilator.

Zones are usually based on what the device is used for. Patient monitors and telemetry can be in the same zone. Imaging devices (CT, MRI and X-ray) can be in their own zone. Lab analysers and smart infusion pumps can have their own zones. All the devices in a zone will only communicate with the correct servers (monitoring server, imaging archive or drug library).

When creating your zones, try to follow these rules:

  • Group by function and risk.
  • Only allow required traffic.
  • No direct internet access if not required.
  • Always test rules with clinicians.

Clean, structured cabling will make it easier to know where each device should go.

Consider Vendor and Patching Restrictions

Medical devices can take a long time to patch. Often the manufacturer will have to approve each update. Some only allow their technicians to apply the updates. There may also be restrictions due to certification.

Try to plan for this. Ask your vendors for a software bill of materials. This will tell you what components are in each device. It can then be cross referenced to known issues.

Ensure your purchase contracts include:

  • Support timelines.
  • Patch windows.
  • Ability to segment.
  • Clear end of life dates.

If there is no patch available, implement compensating controls. Turn off any unused ports. Only allow certain systems to access the device. Also set an end of life date for older units.

Document all exceptions. A documented risk is much better than an unknown gap.

Continuously Monitor

Whilst segmenting will reduce risk, you also need to monitor your network.

Medical devices follow a predictable pattern. A pump will always talk to the same server on the same port. This means any unusual activity can be easily identified.

Set up alerts for:

  • Talking to an external IP that isn't recognised.
  • A large increase in data.
  • Appearing in the wrong zone.
  • Multiple failed login attempts.

Send these alerts to a team who can act on them. Alerts won't help if no one sees them.

Create an action plan to isolate the device. Ensure it explains how to isolate the device without affecting patient care. Practice your action plan.

Attackers won't work to your shift patterns. 24/7 IT support services let you respond quickly at nights and weekends. Smaller clinics without a night team can use managed IT services for business to cover the gap.

Future

Regulators and insurance companies are becoming more aware of device security. You're likely to get more questions about your inventory, segmentation and vendor contracts during your next audit.

Teams who plan ahead will have fewer surprises and spend less on urgent fixes.

Start simple. Complete your inventory this quarter. Then create zones for your highest risk devices. Finally, add monitoring. All of these will complement each other.

Ready to Transform Your IT Infrastructure?

Contact Arch Enterprise, Inc. today for expert consultation and professional installation services tailored to your business needs.

Trusted by businesses nationwide24/7 SupportCertified Technicians