
How the FDA Pushes Medical Device Cybersecurity
An agency leader says the process should continue “throughout the total product life cycle.”
A phony myth might be fun on Halloween, but spooky is no good in the medical device industry. Still, quite a few legends
Suzanne B. Schwartz, MD, MBA, associate director for science and strategic partnerships at the FDA’s Center for Devices and Radiological Health,
“With so many devices dependent on software and internet access today, having a plan in place to address cybersecurity risks is as essential to the device development process as coming up with a novel new product,” Schwartz wrote. “Working with the medical device industry and other federal agencies, FDA will continue its work to ensure the safety and effectiveness of medical devices at all stages of their lifecycles against potential cyber threats.”
For one, the regulator has published guidances encouraging device manufacturers to track cybersecurity risks throughout a product’s life, she noted. The agency “incentivizes industry” to update marketed and distributed devices to reduce cyberattack risks, she said.
The recommendations are meant to help companies navigate the complex nature of “critical safety systems,” requiring a “collaborative approach to finding solutions,” Schwartz wrote.
Released in late 2016,
The FDA also aims to work with manufacturers and the public to
- The FDA is the only federal body responsible for medical device cybersecurity. (It’s not.)
- Cybersecurity for medical devices is optional. (Federal regulations require risks to be addressed.)
- Medical manufacturers can’t update devices for security. (They always can.)
- Healthcare organizations can’t patch devices to beef up their cyber defenses. (The FDA recommends they “work closely” with manufacturers.)
- The FDA validates security software changes. (That’s up to the manufacturer.)
- The FDA tests the cybersecurity of medical devices. (Again, that task falls on the company.)
- Developers of off-the-shelf software used in medical devices must ensure the code is secure for healthcare uses. (Yet another responsibility of the device maker.)
The regulator considers cybersecurity efforts in this area important not just due to the potential loss or theft of patient medical data, but also because the health implications, Schwartz wrote. “A breach that potentially impacts the safety and effectiveness of a medical device can threaten the health and safety of an individual or patients using the device,” she explained.
She pointed to cyberattacks, like
Photo credits: Thumbnail: U.S. Air Force photo/Kemberly Groue; Article: FDA








































