January 20, 2016 By Larry Loeb 2 min read

On Jan. 15, the U.S. Food and Drug Administration (FDA) issued draft guidelines regarding the cybersecurity of medical devices. These guidelines cover both the design of a medical device as well as their maintenance.

Security Concerns

In its recent announcement, the FDA detailed its recommendations for monitoring, identifying and addressing cybersecurity vulnerabilities in a medical device once it has entered the market.

“The draft guidance is part of the FDA’s ongoing efforts to ensure the safety and effectiveness of medical devices, at all stages in their life cycle, in the face of potential cyberthreats,” the release said. Including the phrase “all stages” means that the FDA is not going to ignore necessary updates and maintenance of these devices — it is dedicated to securing equipment no matter what.

The guidelines outlined recommendations for medical device manufacturers, including the need to proactively plan for and assess cybersecurity vulnerabilities, which is consistent with the FDA’s Quality System Regulation. The draft also suggested manufacturers implement a “structured and systematic comprehensive cybersecurity risk management program and respond in a timely fashion to identified vulnerabilities.”

The 25-page draft is for comment only, according to the FDA. The agency plans to hear public comment at its upcoming workshop “Moving Forward: Collaborative Approaches to Medical Device Cybersecurity,” held Jan. 20–21 at the agency’s headquarters in Silver Spring, Maryland. This will be followed by a 90-day comment period.

The FDA stressed the value of information sharing via participation in an Information Sharing Analysis Organization (ISAO). This is a collaborative group in which public- and private-sector members share cybersecurity information.

Getting Specific

The specific recommendations include applying the Framework for Improving Critical Infrastructure Cybersecurity from the National Institute of Standards and Technology (NIST). This included the five core principles: identify, protect, detect, respond and recover. Under that broad umbrella, the NIST placed actions such as monitoring cybersecurity information sources for vulnerabilities and risks, understanding the impact of a vulnerability and establishing processes to handle these issues.

Just how organizations go about completing those tasks is left vague, however. Similarly, distinguishing how advancements such as mobile apps fit into this framework is not clear. This is likely something the FDA will address in the future, but for now, the focus is on medical devices themselves.

Just the Beginning

The draft is just that — a draft. Now, the FDA must start to persuade industry players to do things the proper way. This is sort of new territory for the agency, and simply issuing regulations without accepting feedback will lead to intransigence. If the FDA wants this conversational approach to work, it will have to give players some functional grease to allow them to fit into the framework.

More from

FYSA — VMware Critical Vulnerabilities Patched

< 1 min read - SummaryBroadcom has released a security bulletin, VMSA-2025-0004, addressing and remediating three vulnerabilities that, if exploited, could lead to system compromise. Products affected include vCenter Server, vRealize Operations Manager, and vCloud Director.Threat TopographyThreat Type: Critical VulnerabilitiesIndustry: VirtualizationGeolocation: GlobalOverviewX-Force Incident Command is monitoring activity surrounding Broadcom’s Security Bulletin (VMSA-2025-0004) for three potentially critical vulnerabilities in VMware products. These vulnerabilities, identified as CVE-2025-22224, CVE-2025-22225, and CVE-2025-22226, have reportedly been exploited in attacks. X-Force has not been able to validate those claims. The vulnerabilities…

SoaPy: Stealthy enumeration of Active Directory environments through ADWS

10 min read - Introduction Over time, both targeted and large-scale enumeration of Active Directory (AD) environments have become increasingly detected due to modern defensive solutions. During our internship at X-Force Red this past summer, we noticed FalconForce’s SOAPHound was becoming popular for enumerating Active Directory environments. This tool brought a new perspective to Active Directory enumeration by performing collection via Active Directory Web Services (ADWS) instead of directly through Lightweight Directory Access Protocol (LDAP) as other AD enumeration tools had in the past.…

Smoltalk: RCE in open source agents

26 min read - Big shoutout to Hugging Face and the smolagents team for their cooperation and quick turnaround for a fix! Introduction Recently, I have been working on a side project to automate some pentest reconnaissance with AI agents. Just after I started this project, Hugging Face announced the release of smolagents, a lightweight framework for building AI agents that implements the methodology described in the ReAct paper, emphasizing reasoning through iterative decision-making. Interestingly, smolagents enables agents to reason and act by generating…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today