OWASP Secure Medical Device Deployment Standard

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

The OWASP Secure Medical Device Deployment Standard
With the growth of electronic medical records systems and the increasing use of network enabled medical devices, hospitals and other healthcare related facilities are becoming more interconnected than ever. While this increasing level of interconnectedness often results in improvements to both the quality and efficiency of patient care, it is not without some potential security drawbacks. Many medical devices are extremely costly to upgrade or replace and such legacy systems within healthcare facilities are often commonplace. Moreover, many medical devices were engineered with patient safety and life saving as the sole functions of the device and little attention was traditionally paid to the security of these devices. These trends are evidenced by recent FDA recommendations as well as numerous security studies that find many medical devices rife with security vulnerabilities. Additionally, such networked enabled medical devices within hospitals are often not deployed with security in mind, which can further add to the ease of compromise. With the explosion of botnets and other malware that now target IoT devices (of which medical devices can be considered a subtype) the need for security minded deployments of medical devices is now more essential than ever. This guide is intended to serve as comprehensive guide to the secure deployment of medical devices within a healthcare facility.

Project Description
A guide and checklist organizations can use as the basis for securely deploying network enabled medical devices

Licensing
'''The OWASP Secure Medical Device Deployment Standard is free to use. In fact it is encouraged!!! '' Additionally, we also encourage you to contribute back to the project.

The OWASP Secure Medical Device Deployment Standard is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

Project Leaders

 * Christopher M Frenz
 * Bev Corwin

Project Contributors

 * Erdal Yildiz

Download

 * Standard Version 1.0
 * Purchasing Assessment v1.0

Translations

 * Turkish

Presentation

 * Defcon 2017 Biohacking Village

News and Events

 * CSO Article
 * IAPP Privacy Perspectives Article
 * HelpNet Security Article
 * HealthTech Magazine Article

Classifications

 * }

=FAQs=

How can I participate in your project?
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a security expert can I participate in your project?
Yes, you can certainly participate in the project if you are not a security expert or technical. The project needs different skills and expertise and different times during its development.

= Acknowledgements =

Contributors
The OWASP Secure Medical Device Deployment Standard is developed by a worldwide team of volunteers.

The first contributors to the project were:


 * Christopher M Frenz
 * Bev Corwin

= Road Map and Getting Involved =

Road Map

Use the feedback received from version 1 of the document and use it to create an even more robust and comprehensive version 2 of the guide.

Get Involved

Involvement in the development and promotion of OWASP Secure Medical Device Deployment Standard is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

Suggest Additional Security Controls Proof Reading Graphic Design Educate local communities

=Project About=