Industry

Healthcare cybersecurity: patients, data, devices

In a hospital, it is not only computers that are connected to the network, but also infusion pumps, CT scanners and vaccine fridges. CUBRA hides the devices from outsiders and keeps patient data between doctors.

What can happen

Here an attack costs lives, not money

Hospitals pay ransoms because they cannot wait.

Ransomware

Shuts down admissions, records and imaging – patients are taken to other hospitals.

Dose tampering

An infusion pump receives an outside command and changes the dose.

Vaccines warming up

A fridge quietly warms up – the batch is ruined.

Patient data leak

Diagnoses and test results in the wrong hands.

!
A real case – 2017

Ransomware brought part of the UK’s hospitals to a halt: operations were cancelled and ambulances took patients to other hospitals.

Where CUBRA Node goes

CUBRA Node Rack in the hospital server room

The CUBRA Node security gateway divides the network: devices, records, laboratory, building systems and patient Wi-Fi are kept apart. The manufacturer’s service access goes only over our channel.

  • Devices see only their own server
  • Your equipment stays as it is
  • Patient data stays between doctors
Internetno access to equipmentService companyonly via our channelCUBRA Nodehospital server roomMedical devicesown server onlyPatient recordsDoctors’ PCsLaboratoryanalysers, refrigerationBuildinglifts, ventilationPatient Wi-Fiinternet onlySegments cannot see each other: a hacked PC cannot reach the devices
What the gateway does

Six levels of protection

Hides it from the internet

There is no way to reach your devices, laboratory and building systems from outside: they cannot be seen from the internet, whatever vulnerabilities they may have.

Splits it into segments

Each group of devices works in its own segment (a separate part of the network): a hacked PC cannot reach the devices.

Lets service in only via our channel

The service company gets in through our secure channel. Every login is logged, and access opens for the duration of the work and closes by itself.

Understands the “language of equipment”

CUBRA Node examines the commands equipment receives over the network: each segment gets only the commands it needs, and the gateway holds back the rest (equipment command filter — after release).

Holds back dangerous commands (after release)

A dose change on every pump in a ward will not get through silently – the person responsible gets an alarm at once.

Knows every device

CUBRA Node finds all devices, their firmware and known vulnerabilities by itself – and suggests what to do.

Who exactly it is for

Where we help

What is connected and how we handle it
Medical devices

Infusion pumps, monitors and ventilators should see only their own server. We put them in a separate segment: there is no path to them from staff computers, patient Wi-Fi or the internet. CUBRA Node lets through only the commands the device needs, and holds back anything unusual – for example, a dose change on every pump in a ward – and raises an alarm.

CT scanners and X-ray

These machines send images to the archive, and the manufacturer maintains them remotely. We put them in a separate segment from which images go only to the archive. The manufacturer services the machine only through our secure channel: every login is recorded in the log, and access opens only for the duration of the work.

Lifts

The lift is connected to the network so that the service company can see faults. We put it in a separate segment: only the service company can reach it, and only over our channel. There is no path to the lift from doctors’ computers or patient Wi-Fi. CUBRA Node will hold back an outside command to the lift, and the duty officer will get an alarm at once.

Ventilation and heating

A contractor sets up and maintains ventilation and heating over the network. We put these systems in a separate segment; the contractor connects only over our channel. A command to switch off ventilation in an operating theatre will not go through silently: CUBRA Node will hold it back and raise an alarm.

Doctors’ computers and patient records

Doctors’ computers and patient records sit in a separate segment. If a computer is infected, the malware cannot reach the medical devices or building systems. Messages about patients go through CUBRA Messenger, only between doctors.

Patient and visitor Wi-Fi

Guests connect to a separate network that offers internet access only. No device on the site is visible from it, so even a guest’s infected phone finds nothing.

What it protects against
  • Ransomware
  • Admissions halted
  • Dose tampering
  • Patient data leak
  • Ventilation switched off
  • Lifts stopped
How we connect it
  1. CUBRA Node finds every device on the hospital network by itself
  2. We install CUBRA Node in the server room and place the devices in segments
  3. We connect service companies over our channel
  4. We switch on alarms for the duty officer – and the hospital is protected
What is connected and how we handle it
Analysers

Analysers send results to the laboratory system. We put them in a separate segment from which results go only there; the manufacturer services the instrument only over our channel. There is no path to the analysers from the office network or the internet, so results cannot be altered from outside.

Freezers and blood fridges

Temperature sensors send readings to the duty officer. We put them in a separate segment. CUBRA Node will hold back a command to change the temperature, and a sudden rise in temperature immediately raises an alarm for the duty officer.

Laboratory system and PCs

The laboratory system and staff PCs sit in their own segment. If a computer is infected through email, the malware cannot reach the analysers and fridges.

What it protects against
  • Tampered results
  • Blood thawing
  • Ransomware
How we connect it
  1. CUBRA Node finds every device on the network by itself
  2. We place devices, records, building systems and guests in separate segments
  3. We connect service companies over our channel
  4. We switch on alarms for the duty officer

Vaccine storage

A vaccine fridge must stay within +2…+8 °C around the clock. Unnoticed warming – and the batch has to be destroyed.

What we offer
What is connected and how we handle it
Fridges and sensors

Sensors are connected so that the temperature can be seen around the clock. We put the fridges and sensors in a separate segment from which data goes only to the temperature log. Only the responsible person can change the settings, and only over our channel.

Temperature log

The log proves that the vaccines were stored correctly. It is kept apart from the office network, so malware on a PC cannot erase or alter it.

Alarms

Going outside +2…+8 °C or a sensor going missing – a notification to the responsible person in CUBRA Messenger.

What it protects against
  • Unnoticed warming
  • Tampered readings
  • Batch loss
How we connect it
  1. CUBRA Node finds every device on the network by itself
  2. We place devices, records, building systems and guests in separate segments
  3. We connect service companies over our channel
  4. We switch on alarms for the duty officer

Pharmacies

A pharmacy has a till, a medicine fridge, prescription records and customer Wi-Fi on one small network.

What we offer
What is connected and how we handle it
Payments

A till should talk only to the bank and the accounting system. We put it in a separate segment: there is no path to it from Wi-Fi, cameras or office PCs, and CUBRA Node blocks any other connection the till tries to make.

Medicine fridge

The fridge with its temperature sensor sits in its own segment. Settings can be changed only from the pharmacy manager’s PC; warming above the norm sends an alarm to the responsible person’s phone.

Prescription records

Prescription records sit in a separate segment from which data goes only to the pharmacy chain’s central system over our channel. The prescriptions cannot be reached from the till or customer Wi-Fi.

Customer Wi-Fi

Guests connect to a separate network that offers internet access only. No device on the site is visible from it, so even a guest’s infected phone finds nothing.

What it protects against
  • Card theft
  • Prescription leak
  • Spoiled medicines
How we connect it
  1. We install CUBRA Node Edge in place of the router
  2. We place the till, refrigeration, records and guests in separate segments
  3. We connect the pharmacy to the chain’s central office over our channel
  4. We switch on alarms

Dental and veterinary clinics

The X-ray machine, the computer with the images and the patient appointment system are the most common ransomware targets in small clinics.

What we offer
What is connected and how we handle it
X-ray and images

The X-ray machine sends images to the archive, and the manufacturer maintains it remotely. We put the X-ray machine and the archive in a separate segment; the manufacturer connects only over our channel, so ransomware on the reception PC cannot reach the images.

PCs and patient appointments

Computers and patient appointments sit in their own segment. An infected email can encrypt at most one PC, while the X-ray machine and the image archive stay untouched.

Patient Wi-Fi

Guests connect to a separate network that offers internet access only. No device on the site is visible from it, so even a guest’s infected phone finds nothing.

What it protects against
  • Images encrypted by ransomware
  • Patient data leak
How we connect it
  1. We install CUBRA Node Edge in place of the router
  2. We place the X-ray machine, PCs and guests in separate segments
  3. We connect the X-ray manufacturer over our channel
  4. Done – we handle the setup

Care homes

Call buttons, fall sensors and doors must always work – residents’ lives depend on them.

What we offer
What is connected and how we handle it
Call buttons and sensors

Buttons and fall sensors send calls to the duty officer. We put them in a closed segment, so a call reaches the duty officer even when the office network is infected.

Doors and access control

Door controllers sit in their own segment and accept commands only from the duty officer’s desk. Opening many doors at once or a command from another part of the network raises an alarm.

Cameras

A camera should send video only to the recorder. We put cameras in a separate segment and hide them from the internet; if a camera tries to scan the network or send data outside, it is isolated and the duty officer gets an alarm.

Resident and guest Wi-Fi

Guests connect to a separate network that offers internet access only. No device on the site is visible from it, so even a guest’s infected phone finds nothing.

What it protects against
  • A silent call button
  • Doors open to strangers
How we connect it
  1. CUBRA Node finds every device on the network by itself
  2. We place devices, records, building systems and guests in separate segments
  3. We connect service companies over our channel
  4. We switch on alarms for the duty officer
Several sites

Your whole network of clinics in one dashboard

The medical director or IT department sees every clinic, every device and every alarm.

  • The same rules for all sites in one go
  • Alarms sent to the duty officer’s phone
  • Log of service company logins
And people too

Secure communication for staff

Doctors discuss patients and send scans and test results in CUBRA Messenger – only among themselves.

  • Messages, calls, mail, files
  • Works on inexpensive phones

FAQ – Healthcare

How do I protect patient data if doctors message each other in messengers?

Move work messages to CUBRA Messenger: patient data is encrypted on the doctor’s device and opened only by the recipient. Test results can be sent to a patient with a secure CUBRA Share link.

Can medical devices that can’t be updated be protected?

Yes. CT scanners, infusion pumps and vaccine fridges go into a separate segment hidden from the internet. A dose change on a ward’s pumps won’t go unnoticed – the person in charge gets an alert. The device itself stays unchanged.

What happens to vaccine fridges if the internet goes down?

Segments and monitoring inside the facility work without internet too: CUBRA Node sits in your server room. When the connection is back, the events reach the dashboard.

Is CUBRA suitable for a small clinic or pharmacy?

Yes. For a small facility, a compact CUBRA Node Edge and the messenger for staff are enough. We’ll put together the exact configuration and price at the demo, based on the number of your sites and people.

See also: How to send a file or document securely.