Conficker worm may signal new era for healthcare networking
Comments
Forgive my ignorance but did a rash of MRI's get hit by this worm? We do security work for dozens of hospitals and all the MRI devices and modalities I run into are Sun/Unix. I have never seen one allowed out to the Internet... not good practice to run "updates" on a machine that is running a 10k study on someone. These devices are maintained by private networks or VPN tunnel access and maintenance is Scheduled!
If radiology systems did get hit, I would imagine it would have been windows based PACS. For some reason vendors started dropping MAC/Unix and started using Windows.
If anyone knows of medical equipment being hit.. I mean real equipment, like MRI,PET, CT not PC's that process the end results. please post some info.
I am working for a startup medical device company as an electrical engineer that is developing an X-ray device. We just finished our 60601 compliance testing. From the engineering side, “networking” a medical device is a nightmare that I would never want to approach in reference to IEC compliance standpoint (again from a start up angle).
We had considered making our device network compatible for the reason of ease of retrieving data and software upgrades but on further review, we found it more advantageous to send a clinician to the site or have the clinician load\download any data from a company issued “thumb drive”. They are clean, controllable (password enabled) and are traceable. Traceability is the ultimate desire for any medical company.





So, you tell me: Why would an MRI machine need to be connected to the Internet in the first place? My guess is that you'll tell me that there's some sort of firmware or operating system upgrades that get performed automatically--that the devices can be monitored or inventoried remotely--or that you're performing some other routine network function.