3 ms·
There's two problems with airgapping. First, how does the machine get updates? Do you mail a DVD to the anesthesia techs? Do they know how to install such a
by AnimalMuppet 7y ago
There's two problems with airgapping. First, how does the machine get updates? Do you mail a DVD to the anesthesia techs? Do they know how to install such a thing, or are they going to mess up the machine in the attempt? Or do you roll a service tech in a truck - to all the machines installed worldwide? (Yes, I know, if the alternative to rolling trucks is letting J Random Hacker play with your machine while it's keeping a patient alive, you'd better roll trucks. But updates are one reason why stuff winds up connected to the net rather than airgapped.)
The second reason why stuff is not airgapped is that it almost certainly connects to the hospital's patient records system. They have to keep a record of everything that happened until all potential lawsuits time out. Just in case there are complications from the surgery, they need all the records from the anesthesia machine uploaded after every use. So the anesthesia machine has to be on the same network as the patient records system - and so does every other medical device in the entire hospital. That network should be completely isolated from outside, but to do so, you have to airgap the network, not just one machine. Yes, it should be done, but that's harder to do, and harder to maintain.
For that matter, I've wondered, when you visit someone in the hospital, if you plug your laptop into the ethernet jack in their room and start looking around, what do you see?
- seiferteric 7y agoHospitals have IT people.
- idbehold 7y agoBoth those problems are not my problem. I am perfectly fine with putting those problems on the hospitals and medical device manufacturers.
- Kalium 7y agoTheir solution has been connectivity. What now?
- snlnspc 7y agoThe hospital's IT staff downloading and preparing update media, which would be the same process for every other device up until connectivity became their solution..
- Kalium 7y agoIt may be worth bearing in mind that historically, this often meant updates not going out at all.
- adrianN 7y agoWhich is not that big of a deal if the updates aren't there to fix wormable holes. And in the area of safety, you can encourage people to update their machines by imposing dramatic fines for non-compliance.
- idbehold 7y agoI think I've been pretty clear that it isn't my problem.
- est31 7y agoThe record keeping can be done via data diodes. As for the updates, they can be done by trained hospital staff, doesn't even have to be medical. Remote updates give the manufacturer remote killing abilities. Don't think that such power concentration is a good idea. For governments you kinda need it, but outside of them there is no need.
- kazinator 7y ago> First, how does the machine get updates? Like every non-networked digital camera I've ever owned: put some fwupdate.bin file on a SD-card, plug it in and run some procedure on the device. If a DVD are used, the techs can locally burn an .iso image onto a blank as an alternative to getting it in the mail. Logs can also be gathered from the machine on removable media. Medical records can be available via some non-airgapped laptop. Maybe something can be integrated into the machine, but the control of actual dangerous parameters for therapy or anaesthesia should be air-gapped. Manual entry only. Operators can still be duped into entering malicious values manually, but at least there is a fighting chance for some oversight.
- gruez 7y ago>[...] put some fwupdate.bin file on a SD-card, [...] >[...] the techs can locally burn an .iso image onto a blank [...] >Operators can still be duped into entering malicious values manually, but at least there is a fighting chance for some oversight. or something like stuxnet.
- Spooky23 7y agoSo, by removing visibility, monitoring and discovery, you would improve oversight by having nurses transcribe data into machines and techs service them with manual USB keys? Unless the IT team consists of Santa’s elves, that’s just not going to happen.
- sdinsn 7y ago> Do you mail a DVD to the anesthesia techs? Do they know how to install such a thing That sounds like an easy solution to me. God forbid people need to learn something new for their job.
- wl 7y ago> They have to keep a record of everything that happened until all potential lawsuits time out. More importantly, these records often have clinical significance.
- craigsmansion 7y ago> First, how does the machine get updates? By eliminating updates. Why isn't software that runs on such machines proven correct? Yes, it's expensive, but medical equipment commands a premium price since it's supposed to meet stringent standards regardless. There's no reason to not up the standards for the software they run.
- AnimalMuppet 7y agoProven correct? No. It's extensively verified and validated, but that's not the same thing. First, what are you going to prove? That it does what it's supposed to? No, because you have to have some formal definition of "what it's supposed to", and that can actually be wrong (see MCAS for an example - the software worked, the problem is that the spec was insane). Second, as somebody (Donald Knuth?) said, it's amazing how many bugs there can be in proven-correct (or formally verified) software. Does your proof prove against all possible bugs? No. Against all possible security issues? Still no. Third, even with those limitations, proven correct software is much harder (slower, and more expensive) to write, because the proof is really long. You want medical devices to have proven correct software? That would be nice. But we'd have maybe 2% of the medical devices that we have now, just because the proofs are so hard. That would be less nice. In particular, more people would die in that scenario from the absence of medical devices, than die in the existing scenario from bugs in them. That's less than helpful.
- craigsmansion 7y ago> That it does what it's supposed to? and that is doesn't do what is not supposed to do. As for your second point, if you could provide some background reading for that, I would appreciate it. I know of Knuth jokingly stating "Beware of bugs in the above code; I have only proved it correct, not tried it", but if he or someone else wrote a more serious paper on the occurrence of software errors in proved software, I would appreciate a link. A proof should prove against all software errors--if it doesn't I'm eager to learn more. As for your third point: software errors are a solved problem, but as you noted, it's a hard (expensive) solution. The solutions also currently may limit functionality, so it's unfortunately not applicable everywhere, but some classes of software should warrant it. In my view medical devices that can directly interact with a patient's physiology is one of them.
- etimberg 7y agoSend a field engineer around. These machines cost a lot of money, surely the cost of having someone come and perform updates wouldn't be crazy