Chapter 37. Understanding Open Source Licensing and Security
Jeff Luszcz
The explosion of open source software has changed every company into a software company.
The impact of this change in how software is procured has caused many organizations to struggle with managing the sheer quantities of components and packages that they now depend on.
As an information security professional, it is important to understand the impacts on security that open source may have as it is selected, downloaded, and updated while at the same time being aware of legal or business risks that may also be introduced into the company.
Software packages and libraries are controlled by licenses. These licenses may be commercial or open source (OSS). Open source (or quasi-open source) licenses typically fall into three styles:
Permissive (allows use with few obligations, often simply just passing along a copyright notice)
Copyleft/viral (requires source code to be shared with users and the community if the code is used)
Restrictive (restricts certain actions or use cases)
The last style is not technically open source but is often mixed in and confused as an open source project.
The heart of a successful OSS management program is keeping a current and continuous inventory of OSS packages. This inventory, often called the software bill of materials (SBOM), allows you to keep on top of software updates and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access