1. Why these devices are a sensitive point
Many medical devices and diagnostic instruments are now connected to the network: ultrasound machines, monitors, pumps, laboratory equipment, imaging systems. They are used to provide care, but they often run on outdated operating systems, cannot be updated like a computer and remain in service for many years. A vulnerable device connected to the general network can become an entry point to the other systems in the facility. The problem grows with the number of devices and with their age.
The problem is not the device itself, but the fact that often nobody knows that it is on the network, who manages it and who can access it from outside. Before any technical work, a precise understanding of what is there is therefore required, and this step matters more than any tool purchased. An incomplete inventory makes every other measure pointless, because you cannot protect what you do not know.
2. Prerequisites: who needs to be involved
The work involves several roles: the clinical management or whoever stands in for them, the head of department, clinical engineering if present, the IT supplier and the device manufacturers. Each has a different role and information the others do not have. Defining this framework at the outset prevents security from becoming nobody's responsibility. It must also be clear who approves network changes and who may authorise work on a device in use on a ward.
Before you start, gather the documentation the manufacturer has provided for each device, including instructions for network connection and guidance on updates. If it is missing, ask the supplier or the manufacturer directly. Do not work on a device without knowing what the manufacturer allows you to change. Keep the answers in a file per device, as they will be needed for the first review and for every future replacement.
3. The steps to build and secure the inventory
Work in this order, because each step depends on the previous one: without a reliable inventory you cannot decide which devices to isolate or which access to close. Record the outcome of each step in a shared document, updated by the head of department and checked by the IT supplier. Do not leave the list in one person's memory, because it changes every time a device is moved, replaced or retired.
If a device cannot be identified, record it as an exception to be resolved and do not drop it from the list. Unidentified devices are often the ones causing the most serious problems, because nobody knows what communications they generate on the network. Set a deadline for closing each exception and assign an owner to each, so the work does not stall. A well-built inventory is worth more than an expensive tool applied without knowing the device estate.
- Build the inventory: for each device record model, manufacturer, department, serial number, network address and the system that uses it.
- Identify which devices are actually connected to the network and which only have a port fitted but not active.
- Assign an internal owner and a supplier contact to each device.
- Group the devices by function and criticality, distinguishing those that support real-time care from supporting equipment.
- Create a dedicated network zone for the devices, separated from ward computers and the administrative network.
- Define the permitted communications: allow only the necessary flows between the devices and the systems that use them, and block everything else.
- Close permanent remote access and enable it only for the duration of a job, with logging and revocation at the end of the work.
- Assess updates proposed by the manufacturer with the clinical lead before applying them, and record the decision.
4. Common mistakes to avoid
The first mistake is believing that an isolated device is automatically secure. If it is connected to the network and nobody knows its configuration, isolation remains an unverified assumption. The second is updating a device's operating system without the manufacturer's consent, as this can invalidate its certification and technical support. Even an apparently harmless update can change the clinical behaviour of the device, and nobody notices straight away.
The third is leaving remote access switched on for the supplier's convenience, without knowing who uses it and when. The fourth is separating the network only on paper: if devices can reach ward computers without restriction, segmentation achieves little. A fifth, and common, mistake is considering the work finished after the first connection, without subsequent periodic checks.
5. How to check that the protection works
Test the isolation by attempting, from the general network, to reach the devices: if the connection succeeds without an explicit rule, there is a problem to fix. Also check that remote access is closed when nobody is working on the device, and that the logs show only authorised interventions. If an access attempt succeeds, note the path that allowed it and close it immediately.
Repeat the check after every network change, after adding a device and at a periodic interval set by the owner. Keep the results of the checks in a dated document: it will be the evidence that the measure works, not a mere statement. If something fails, the document also shows when the problem appeared, valuable information for understanding its cause. Record the date and outcome of checks that found no problems as well.
6. How to get started
This week choose a single ward and build the inventory of its connected devices, with the fields listed in the first step of the previous section. A complete ward is a realistic goal and immediately produces a model to replicate on the others. Also note the difficulties encountered, as they become the starting point for the meeting with the supplier. This first result gives management concrete data on which to decide.
Then ask the IT supplier and clinical engineering, if present, to check together which devices are actually on the network and who supports them. Bring the manufacturers' documentation and a written list of questions, so the meeting produces decisions rather than just discussion. Agree a date for the next check before closing the meeting. If the ward is small the work is quicker and can already provide useful guidance for the others.
Frequently Asked Questions
Can I update the operating system of a medical device?
Not without checking with the manufacturer. Many devices are certified in a precise configuration, and unapproved changes can compromise clinical safety, the warranty and support. Ask in writing which updates are permitted and which alternative measures, such as network controls, are recommended.
Does an old device that cannot be updated need to be replaced?
Not automatically. The decision depends on clinical risk, the possibility of isolating it, the support the manufacturer still provides and the cost of replacement. A device no longer supported on an isolated network may remain in use for a period, provided the risk is documented and accepted by the clinical management.
Should I close unused network ports?
Yes, where possible. An active but unused port is one more opportunity for someone trying to get in. Check with the manufacturer which services are needed for the device to function and which can be disabled without affecting care. Document every change and repeat the check after any intervention.
Who must approve a manufacturer's remote access?
As a rule, the device's or the ward's internal owner, with support from the IT supplier. The request must be recorded with date, reason, duration and the name of the person intervening. At the end of the work the access must be closed, and the closure must be verified, not assumed.
Do the devices need a separate project?
Not necessarily. Many activities start with an inventory and well-written network rules, which can be handled within normal maintenance work. A formal project becomes useful when the number of devices is high or when investment in segmentation is needed. Decide based on the real complexity of the facility.