From National Review.com (Dec. 2):
The American health-care system is under siege. Not only by a deadly novel coronavirus, unleashed by the evil and inept Chinese Communist Party, but also by cyberterrorists whose acts of aggression are just as condemnable and deadly as those of a suicide bomber or hijacker.
On October 28, the University of Vermont (UV) Health Center in Burlington was crippled by an attack on its systems. At the time, the nation’s eyes were set — solely and squarely — on the upcoming election. Thankfully, Ellen Barry and Nicole Perlroth at the New York Times have done yeoman’s work reporting on the attack and its aftermath. So now that the election is behind us, we can identify, name, and address this new kind of national-security threat.
“We expect panic,” declared one hacker in the run-up to the attack. To be sure, for staff working the day the attack came, panic set in when workstations were suddenly rendered inoperable, as were the backup computers. So were the pneumatic tubes used for transporting blood samples and test results, and — worst of all — the electronic medical-record system, which was only restored on November 22, nearly a month after the attack.
The attack on the UV Health Center is not the first act of cyber terror on U.S. health-care infrastructure. The Russian group believed to be responsible for the Burlington attack has, per the FBI, made somewhere around $61 million in ransoms over a 21-month period in 2018 and 2019. In early October, eResearchTechnology, a Philadelphia firm that sells software used in clinical trials — including for certain coronavirus vaccines — was locked out of its data by ransomware — a kind of malware that remains in place until the hackers who have sicced it on you are paid. Hospitals in California, Oregon, Montana, Tennessee, and upstate New York have been similarly afflicted by hackers, who have even gone so far as to release patient data — Social Security numbers, dates of birth, ages, hiring dates, and contact details — on the dark web. [read more]
No comments:
Post a Comment