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

Four Steps to Securing Your Company’s Medical Devices

Four Steps to Securing Your Company’s Medical Devices
Published by Mike Solinap
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

Atlassian Cloud: Understanding Zero Trust Security

Atlassian Cloud: Understanding Zero Trust Security

Where To Start & Why It Matters What is the Atlassian Cloud Zero Trust Security model? Well, for decades, enterprise security controls were built to protect a large, single perimeter around a corporation. Often described as castle-and-moat security, This approach...

Related Resources

Top 6 Ways To Improve Your DevOps Journey

Top 6 Ways To Improve Your DevOps Journey

Knowing how to improve DevOps can be challenging. But, creating an integrated DevOps toolchain can set organizations apart from the rest. This is because having a well-defined business DevOps journey can reduce errors, improve collaboration and drastically increase...

Use Nessus To Harden Your Cybersecurity

Use Nessus To Harden Your Cybersecurity

Cybersecurity should be baked into the onset of IT and product development processes. Additionally, treating cybersecurity as an afterthought opens your organization up to vulnerabilities and risk. Therefore hardening your IT product cybersecurity with a tool like...

2022: The Year So Far Tech Review

2022: The Year So Far Tech Review

There’s been a lot of innovation, software and product releases in the past six months alone. So, we are rounding up the best tech review and engineering releases for the first half of 2022. The tech forecast for 2022 was heavily influenced by how the world adjusted...