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

OSS, Heartbleed, and the Impact on Medical Device Design

windchill features best plm software
Written by Mike Solinap
Published on June 17, 2014

The use of open source software (OSS) within the medical device industry is a double edged sword. On one end of the spectrum, you have freely available code that is available for the world to scrutinize. In the process, one would hope that bugs are more easily identified. OSS also allows medical device design engineers the ability to quickly bring their product to market. By being able to modify existing code, integration into the product is much more feasible.

On the other end of the spectrum, OSS can be analyzed for vulnerabilities, which could be used for malicious purposes. This was the case with the Heartbleed bug – a recently discovered vulnerability affecting a large fraction of OpenSSL based servers.  Should medical device manufacturers give OSS a second thought?Patient data and safety is what’s at risk, and it’s a big risk most manufacturers may not want to take.

SPK Engineers work closely with product development groups. In the process, our expertise in infrastructure systems and application lifecycle management (ALM) often times leads to contributions towards a customer’s product directly. Here are a couple of suggestions I would make whether or not a customer decides to incorporate OSS into their own product, or is concerned about the Hearbleed bug or potential future vulnerabilities.

Use a traditional, tiered application architecture. By having a separate set of nodes with separate roles, it is possible to compartmentalize the data that is processed or stored on each of them. For instance, the Heartbleed bug allowed hackers to request arbitrary segments of memory from an OpenSSL based server. If perhaps a database server was running on the same machine, it’s possible that memory resident portions of the database could be read. With a proxy node in place, it could terminate the SSL session and simply relay back to the main application node. With nothing else running on the node, the risk for data leakage would be mitigated.

Use diverse vendors where possible. Imagine an all-Microsoft shop. Proxy servers, web servers, firewalls, operating systems all come from the same vendor. In the case of the Heartbleed bug, this actually would have been a good thing to have. But let’s not forget about all of the vulnerabilities that have come from this vendor historically. Having multiple vendors in your stack could provide yet another ingredient in your multi-layer security approach.

Next Steps:

Mike Solinap
Professional Services Manager
SPK & Associates

Latest White Papers

A Field Guide to Threat Vectors in the Software Supply Chain

A Field Guide to Threat Vectors in the Software Supply Chain

The software supply chain is made up of many integrated parts, people, and processes. The components range from tools and configurations to code libraries and systems. These components’ goals are developing and delivering software. Unfortunately, risks are high due to...

Related Resources

How Electronic Logbooks Revolutionize Manufacturing Efficiency

How Electronic Logbooks Revolutionize Manufacturing Efficiency

Paper logbooks have been used for years to store important business information. In the digital age, many businesses are switching over to electronic logbooks. Electronic logbooks are digital systems designed to record, store, and manage log entries. These log entries...

Creo Composites Design & Manufacturing Capabilities

Creo Composites Design & Manufacturing Capabilities

Engineers typically have a few distinct materials to work with when designing and manufacturing parts. Composite design allows them to combine two or more varying materials to create a new one. This new material is often sustainable and used to design structures. This...

The Future of Data Engineering in 2024

The Future of Data Engineering in 2024

“Data engineering is the unsung hero of data science, the foundation upon which great data analysis is built.”Everyone in the computer science field is familiar with the phrase, “garbage in, garbage out.” This phrase encapsulates the importance of what goes on behind...