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

What’s in the MITRE/FDA Playbook?

What’s in the MITREFDA Playbook
Written by SPK Blog Post
Published on December 17, 2018

On October 2018, the MITRE Corporation and the Food and Drug Administration released their joint document, Medical Device Cybersecurity Regional Incident Preparedness and Response Playbook. This is the new Bible for organizations designing and manufacturing connected medical devices.

The document is the product of a four-year partnership between MITRE and the FDA. The document was developed in response to real-world cybersecurity breaches such as WannaCry and Petya/NotPetya. It focuses primarily on these types of potential large-scale threats.

MITRE and the FDA recommend regional collaboration. Individual organizations have necessarily limited resources that might not be up to the task of addressing emergent cybersecurity vulnerabilities. Trusted partnerships, however, established on a regional basis, can pool resources and become greater than the sum of their parts. These pooled resources can assist not only preparedness for existing threats, but fast response to zero day and other emerging threats.

MITRE and the FDA provide a number of concrete suggestions for collaboration in the document including:

  • Joint exercises and simulations
  • Sharing policies, plans and best practices
  • Development of mutual aid response plans
  • Sharing advisories and alerts
  • Ensuring access to shared advisories and alerts
  • Formal and informal methods of real-time information sharing
  • Secondary channels of communication
  • Creation of regional command centers
  • Incident tracking procedures
  • Mutual aid agreements such as diverting patients or sharing devices
  • Mutual technical assistance

Regional groups need not be limited to manufacturers and designers. Stakeholders from the initial design team all the way to patient advocacy groups can and should come together. Cybersecurity for connected medical devices is decidedly an area where there is strength in numbers.

Once regional groups of organizations are established and follow these guidelines, it’s only a logical next step that these regional organizations will begin communicating with one another. This opens the opportunity for unified response across regions as appropriate. Even when cybersecurity breaches occur they can be dealt with swiftly. Contingency plans mean less inconvenience for end users, which in turn provides another layer of safety.

None of this will eliminate cybersecurity threats. What it will do, however, is make organizations more resilient when it comes to vulnerabilities to connected devices. What’s more, the guidelines are very open. This allows organizations and groups of organizations to adapt them in ways that make sense for their specific situation rather than a one-size-fits-all template that might not actually fit all.

Next Steps

Latest White Papers

Costs and Benefits of Moving a .NET Application to the Cloud

Costs and Benefits of Moving a .NET Application to the Cloud

Do you know the full cost and benefits of moving your .NET application to the cloud? In this guide we’ll cover everything you need to know about your .NET cloud migration. Is this guide for you? If you’re faced with outdated legacy systems and the pressures of digital...

Related Resources

Best Practices for Successful eQMS Implementation

Best Practices for Successful eQMS Implementation

Are you a medical device manufacturer seeking to overcome the challenges of your current quality management? Let me help you show you the light. In this blog, we will show you the advantages of adopting an Enterprise Quality Management System (eQMS). Better yet, one...

Product Lifecycle Management (PLM) Automated Metrics

Product Lifecycle Management (PLM) Automated Metrics

  Our client is a leading medtech company with 46k employees. Earlier this year, they faced the challenge of improving the efficiency of their Product Lifecycle Management (PLM) process. To stay competitive, they needed to identify bottlenecks within their...