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...
Most Recent Articles
Open Source Licenses in 2020: Trends and Predictions
Top 20 Developer Advocates to Follow in 2020
Top 5 New Open Source Security Vulnerabilities in December 2019
How To Secure Your SDLC
9 Great DevSecOps Tools for Dev Teams to Integrate Throughout the DevOps Pipeline
3 Steps Developers Should Take To Use npm Securely
Top 5 New Open Source Security Vulnerabilities in November 2019
5 Free Developer Tools We're Grateful For
Key Take-aways from Gartner's Technology Insight for Software Composition Analysis Report
Understanding CVSS v3.1
Welcome to WhiteSource, Renovate!
Top 5 New Open Source Security Vulnerabilities in October 2019
Fitting Continuous Testing Into Your DevOps Pipeline
Open Source Copyleft Licenses: All You Need to Know
Sudo Vulnerability Cheat Sheet: Learn All About CVE-2019-14287
Top 5 Container Security Tools You Should Already Be Using
WhiteSource for Developers: New Integrations for GitLab Core and Eclipse IDE
Top 5 New Open Source Security Vulnerabilities in September 2019
Top 5 Git Security Mistakes
Security Advisories Play a Critical Role in Keeping Our Software Safe