fbpx
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Four Steps to Securing Your Company’s Medical Devices

windchill features best plm software
Written by Mike Solinap
Published on November 7, 2018

Connected medical devices offer enormous opportunity for manufacturers and consumers alike. They also carry the burden of increased risk due to cybersecurity flaws. Think about the dangers of having your email or bank account hacked. Now consider the damage hacking a connected medical device or the information stored from it can do.

Medical information is some of the most sensitive information most people have. However, it’s not just the potential consequences of a database hack users of connected devices need to worry about. It’s also the spectre of an attack on the device itself — an attack that could easily be deadly.

Current FDA Guidelines

There’s already FDA guidelines for connected medical devices, most recently updated in October 2018 with its Medical Device Cybersecurity Playbook developed with Mitre. The guidance seeks to prevent both unauthorized access to data and protect the security of the device itself. There are a number of steps to protect end users, as well as company reputation:

  • Identification: Threats and vulnerabilities to assets should be identified prior to manufacturing a device.
  • Assessment: Both the impact of a threat and the likelihood of a threat must be assessed.
  • Design: Balancing risk against mitigation, you must design a device meeting FDA standards to protect your end users.
  • Monitoring: Your company must also monitor potential threats after the device goes to market to ensure the continued safety of the device.

Medical device security isn’t an abstract problem. In October 2018, Medtronic Plc disabled all downloadable updates to connected pacemakers citing security issues. On a wider scale, the British National Health Service was effectively crippled by the WannaCry ransomware in April of the same year. Former Vice President Dick Cheney had his pacemaker disabled for fear of a hack.

It’s worth noting that every point of connectivity in a medical device is a potential place for hackers to access a device. This is why the FDA has stringent standards for connected devices. In our next blog post we will discuss what to expect when going through your 510k approval process.

Next Steps

Latest White Papers

Model-Based Definition Capabilities in Creo

Model-Based Definition Capabilities in Creo

Model-based definition (MBD) is a design approach that revolves around creating, organizing, and managing a 3D Model. Explore how PTC Creo utilizes MBD to help you achieve an efficient design.  What You Will Learn In this eBook,...

Related Resources

Mastering Tool Modernization Challenges with OpsHub

Mastering Tool Modernization Challenges with OpsHub

As software complexity increases, companies are looking for new ways to innovate.  Keeping up with new technology requires new tools and systems to handle this complexity.  Migrating from on-prem and legacy systems to modern, scalable, cloud offerings is commonly...

5 Steps to Standardize Security in DevOps

5 Steps to Standardize Security in DevOps

Although security has always been a priority for developers, new technologies have made it one of the most prominent aspects of DevOps.  This has resulted in the coined term “DevSecOps”, with many companies offering new “DevSecOps platforms.”  With hackers developing...