Q-Cyber Magazine

Healthcare · 23 July 2026 · 3 min read

Connected medical devices belong on the security inventory

Networked clinical devices are industrial systems in a hospital: they need an inventory, a software bill of materials, a place in the network architecture, and the same reporting duties that apply to other hospital ICT.

Abstract graphic of a grid of circuit traces in Knowlcom blue

A connected imaging device, infusion pump or monitoring station is not a consumer gadget that happens to sit in a ward. It is a clinical system with software, a network path and, often, a store of personal data. If it is missing from the inventory, it is missing from every control that follows.

Treat the device as a system

62443's value here is not that every hospital must certify every pump to a particular part of the series. It is the shared-responsibility model. The device supplier has a development-lifecycle and component duty. The integrator who connects the device to the clinical network has a design duty. The hospital, as asset owner, has a programme duty: inventory, access, patching in a clinical window, and an incident path. When those roles are unnamed, a vulnerability disclosure has nowhere to land.

A software bill of materials makes the inventory specific. Many clinical incidents begin with a library or an operating system the hospital did not know was there. A signed SBOM that meets the July 2026 minimum elements, updated when firmware changes, is the document that allows the hospital to answer a simple question: are we running the affected version?

Network architecture is the third leg. A device should not be reachable merely because it is on the hospital LAN. Implicit trust of that kind is what NIST's zero-trust guidance rejects, and what ransomware prevention tries to close. Segmentation, attributable access for service accounts, and offline backups of device configurations are ordinary controls, applied to an estate that happens to be clinical.

Exhibit 1

A minimum programme for connected clinical devices

ControlWhy it is requiredPublic hook
Named owner and inventoryA device that is not listed cannot be patched, isolated or reported onAsset-owner responsibility in the 62443 model
Signed SBOM, including firmwareAdvisories can be matched to running versions; unknowns are visibleCISA 2026 SBOM minimum elements, 29 July 2026
Network path controlA clinical device should not be trusted solely because it is 'inside'Least-privilege, resource-centred access; CISA ransomware guidance on narrowing paths
Logs and six-hour reportingA compromised device is an ICT incidentCERT-In directions, 28 April 2022
Personal-data dutiesDevice stores and feeds are often identifiable health recordsDPDP Act and Rules: purpose, safeguards, breach notice, 90-day rights

Source: ISA, ISA/IEC 62443 series page (medical devices among listed sectors); CISA and partners, 29 July 2026; CISA #StopRansomware Guide; CERT-In, 28 April 2022; PIB, 14 November 2025.

Implications

  1. Put every networked clinical device on the inventory, with an owner and a software record.
  2. Require SBOMs in device procurement, and refresh them at firmware updates.
  3. Segment clinical networks so that implicit trust is not the access model.
  4. Include devices in incident and DPDP rehearsals, not only the electronic medical record.

What this means for healthcare

Connected care will grow. The hospitals that will absorb that growth safely are those that can name their devices, their software and their network paths, and that can report an incident on the statutory clock. A device that cannot be listed cannot be defended.

Sources

  1. ISA/IEC 62443 Series of Standards
  2. 2026 Minimum Elements for a Software Bill of Materials
  3. CISA #StopRansomware Guide
  4. CERT-In Directions, 28 April 2022
  5. PIB notification of the DPDP Rules, 2025