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
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
Securing Your Software Supply Chain with Software Composition Analysis
Top 5 New Open Source Security Vulnerabilities in August 2019
Top 5 Back to School AppSec Tips for Developers
Open Source License Comparison: Connecting — and Contrasting — the Dots
Serverless Security Explained
Top 5 New Open Source Security Vulnerabilities in July 2019
Application Security Best Practices Top 10 Checklist
5 Vulnerability Assessment Common Misperceptions
Security Automation: Where Does It Fit In Your Secure SDLC?
WhiteSource achieved Amazon Web Services DevOps Competency Status
Introducing WhiteSource Advise for IntelliJ IDEA
Top 5 Open Source Security Vulnerabilities in June 2019
Top 5 Go Vulnerabilities That You Should Know
8 Patch Management Best Practices to Implement in 2019 to Close the Door on Attackers
Secure Coding: A Practical Guide