informa
Slideshow

6 Best Practices for Using Open Source Software Safely

Open source software is critical yet potentially dangerous. Here are ways to minimize the risk.
Have a Policy
Track and Update Components on Purpose
Use Automation
Pay Attention to Dependencies
Pay Attention to Project Size
Repositories Matter
1/6

It's no longer a question of whether enterprise software is developed using open source code, but just how much open source code makes up each application. And as DevOps becomes the default development discipline for more organizations, the pressure to reach out and grab reusable modules and libraries is almost guaranteed to make open source code a greater percentage of enterprise software.

Even with commercial software, questions about third-party risk and supply chain security loom large. When those questions extend to open source software, they can become absolutely overwhelming.

Research bears that out. In reviewing enterprise codebases submitted for audit, Synopsis found 70% of the code was open source. While not in any way an indictment in and of itself, 73% of codebases they found had at least one licensing issue and 82% included 4-year-old code. Combined, the security and reliability of applications containing open source software becomes a legitimate concern.

As with so many facets of cybersecurity, attention to detail carries a great deal of weight when it comes to keeping open source containing projects safe and secure. What else do you need to know? Dark Reading combed the Internet and reviewed numerous conversations we've had in recent months to put together this collection of best practices. Let us know whether you have any of your own in the Comments section, below.

(Image: duncanandison VIA Adobe Stock)

 
Next slide
Recommended Reading: