10 Steps To Overcome Your Fear Of Using Open Source Software

October 9, 2014 Patricia Johnson

Share this Article
Facebook
Twitter
Email
LinkedIn

A great article by Shahid Shah "...If you ask some regulatory affairs folks in medical device companies, they think OSS is too “dangerous” for use in safety critical systems. The most common excuse given by engineers is that the regulatory compliance folks will not allow OSS or that the FDA will disapprove. There is plenty of evidence to the contrary, however, because the FDA hasn’t really rejected devices due solely to the use of OSS. The lack of OSS use in medical devices and healthcare IT circles in most cases likely stems from a lack of experience with OSS at the senior executive and regulatory compliance ranks within companies. This is a summary of a quick 10 step process that R&D groups can use to properly experiment with and include OSS in safety-critical systems."

R&D Executive – Why Shellshock and Heartbleed Should Matter to You

So, you’ve heard of Shellshock, of course. And if you use Unix, you made sure someone installed the right p...

Discovered Shellshock Bug Can Now Be Immediately Detected by WhiteSource’s Solution

The WhiteSource solution is now available for the immediate detection of the newly discovered Shellshock to...

Stay up to date, subscribe to our newsletter today!

Country

I agree to receive email updates from WhiteSource

Thank you!

Error - something went wrong!

Most Recent Articles

API Security in a Digitally Transformed World

10 Steps To Overcome Your Fear Of Using Open Source Software

Previous Article

Next Article

Most Recent Articles

API security is an essential part of application security in a digitally transformed world.

How to set up and implement an open source strategy that will ensure open source security and compliance.

Find the top security conferences to visit in 2021, virtually or in-person

To help you stay on top of your open source security, here is our list of top 10 open source security vulnerabilities in 2020.

What is application security testing orchestration and why it is crucial in helping organizations make sure all potential risks are tracked and addressed.

Kubernetes security should be a primary concern and not an afterthought. Learn how to avoid risks by applying security best practices.

Why is microservices security important? Key principles and best practices to ensure your microservices architecture is secure.

In this article we explain what Software Composition Analysis tool is and why it should be part of your application security portfolio.

Learn all about white box testing: how it’s done, its techniques, types, and tools, its advantages and disadvantages, and more.

All about application security - why is the application layer the weakest link, and how to get application security right.

Top tips for getting started with WhiteSource Software Composition Analysis to ensure your implementation is successful.

Secure your organization's software by adopting these top 10 application security best practices and integrating them into your software development life cycle.

How prioritization can help development and security teams minimize security debt and fix the most important security issues first.

All about Eclipse SW360 - an application that helps manage the bill of materials — and its main features.

Why you shouldn't track open source components usage manually and what is the correct way to do it.

What are the different types of black box testing, how is it different from while box testing, and how can black box testing help you boost security?

Software Composition Analysis software helps manage your open source components. Here are 7 questions you should ask before buying an SCA solution.

How to make sure you have a solid patch management policy in place, check all of the boxes in the process, and use the right tools.