Skip to main content
Legia

IT Support & Consulting

Open Source Software for Companies: Licenses, Support, and Security Risks

Open source software is common in companies, but open code does not mean no obligations. There are decisions about licensing, support, and security updates to make before and after adopting it.

SEO and Content Specialist

7 min read

A product roadmap on a whiteboard

Short answer: companies can use open source software, including for commercial purposes, but open code does not mean no obligations. Three decisions need to be made: the license type and its obligations (permissive or copyleft), who provides support and security updates, and how the components in use are recorded so security flaws can be traced quickly. License obligations are best reviewed with the legal team.

Many companies already use open source software, often without realizing it: server operating systems, databases, web servers, and the libraries inside applications built by vendors. The question is rarely “is it allowed”, but rather “who is responsible when something goes wrong” and “what obligations come with it”. This article covers the governance decisions, not a comparison between open source and paid software.

What open source means for a company

Open source is not just code you can read. The Open Source Initiative (OSI), which maintains the Open Source Definition, makes that point in the first sentence of the definition, then sets out ten criteria. The two most relevant for companies:

  • Free redistribution: the license may not prohibit anyone from selling or giving away the software.
  • No restriction on fields of endeavor: the license may not prohibit the program from being used in a particular field, including business.

This means software whose license prohibits commercial use does not meet the definition of open source, even if its code can be downloaded. Check whether the license is among the OSI-approved licenses before treating it as open source.

The license itself costs nothing, but using the software still has costs: the team’s time to install and update it, a support contract if needed, and migration work when a version is no longer maintained.

Illustration: IT support

Permissive and copyleft licenses: different obligations

Open source licenses are generally grouped into two kinds. Permissive licenses only ask for light conditions, such as including a copyright notice. Copyleft licenses require modified versions that are distributed to give their recipients the same freedoms, as explained by the Free Software Foundation.

LicenseGroupMain obligations according to the license text
MITPermissiveThe copyright and permission notice must be included in all copies or substantial portions of the software
Apache 2.0PermissiveInclude a copy of the license, mark changed files, keep the notices and the contents of the NOTICE file. It grants a patent license that ends if you bring a patent claim over the work
GNU GPLCopyleftIf distributed, modified versions must give the same freedoms, including access to their source code
GNU AGPLCopyleftModified versions used by people over a network must offer their source code to those users

For a company, the key word is distributed. According to the GNU licenses FAQ, the GPL does not require modified versions to be released to the public, and copies made and used within one organization do not count as distribution. The situation is different if the software is handed to another party, for example an application that is sold or installed at a client’s site. The AGPL goes further, because use over a network, such as a web application, also triggers obligations.

How a license applies can depend on how components are combined and distributed. The table above is a summary, not legal advice: involve the legal team before using copyleft components in a product that will be handed to other parties.

Support: who fixes it when something goes wrong

Open source software does not come with a guarantee. The MIT license, for example, states that the software is provided “as is” without warranty of any kind. A company therefore needs to decide its source of support:

  1. The project community: forums and issue trackers. No guaranteed response time.
  2. A subscription from the company behind the project: many large projects have a commercial provider that sells support and extended security updates.
  3. An internal team or IT partner: support is set out in a contract, including who installs updates.

The support period should also be recorded from the start. Ubuntu, for example, gives LTS releases five years of standard security maintenance, and Canonical offers extended security updates through Ubuntu Pro. As a counterexample, CentOS Linux 7 reached end of life on June 30, 2024. Since then, servers still running it no longer receive security updates from that project. The CIS Controls v8 framework asks that only currently supported software be designated as authorized, with a written exception when unavoidable, and that the support list be reviewed at least monthly.

Security risks and how to manage them

The biggest open source risk in a company is rarely that the code is open, but rather components that are used without anyone knowing and are never updated. The Log4Shell case (CVE-2021-44228) showed this. CISA classed it as a critical flaw allowing remote code execution, recorded widespread exploitation, and said Log4j is very broadly used across enterprise services, websites, and applications. Organizations that did not know which systems had the library installed had to find it first before they could patch it.

Management steps you can start now:

  • Record components and their versions. CISA defines an SBOM (software bill of materials) as a nested inventory, a list of the ingredients that make up software. For applications built by a vendor, ask for such a component list at handover.
  • Assess a project’s health before using it. OpenSSF Scorecard automatically assesses open source projects, including whether the project is still maintained, whether code changes are reviewed before being merged, whether there are unfixed vulnerabilities, and whether there is a security policy.
  • Monitor and install security updates with a clear schedule and owner.

A company open source policy: five decisions

A company does not need a thick document. These five decisions are enough to start:

  1. License list: licenses that can be used straight away, those that need legal review, and those not used for certain products.
  2. Project selection criteria: still actively maintained, has a security policy, and has a clear support period.
  3. Inventory: name, version, license, the systems that use it, and its owner. The method is the same as recording paid licenses, as covered in the article IT Asset and Software License Inventory.
  4. Updates and vulnerability monitoring: who monitors security announcements, and how long critical updates may be postponed.
  5. End-of-support plan: when the version in use stops being supported, and when its migration is scheduled.

If an application is built by a vendor, put the same decisions in the contract: the list of open source components and their licenses, who updates them, and what happens if a component stops being maintained.

How Legia helps

In the IT Consulting service, Legia maps the systems you use today, what they are for, what they cost, and which ones overlap or carry risk, then prepares phased recommendations with cost and time estimates. The recommendations always include options that do not involve Legia, including using off-the-shelf software or continuing with existing systems. A second opinion on a vendor proposal usually takes 1-2 weeks, while a system review and technology plan takes 3-6 weeks. The document is yours and can be taken to other parties. For license obligations, the final decision still rests with your legal team. When a consultant is needed is covered in the article When Does a Company Need an IT Consultant.

Frequently asked questions

Can open source software be used for commercial purposes?

Yes. The Open Source Definition prohibits licenses from restricting fields of endeavor, so OSI-approved licenses allow business use. The license obligations, such as including the copyright notice, still apply.

Does using a GPL component in an internal application require opening the code?

According to the GNU licenses FAQ, not as long as the application is only used within the organization. Obligations arise when the software is handed to another party. For the AGPL, use over a network also triggers obligations. Confirm the interpretation with the legal team.

Is open source software riskier than paid software?

The risk depends more on maintenance than on the licensing model. An active project that patches flaws quickly can be safer than a paid product that is not updated, and vice versa.

Who is responsible if there is a security flaw?

Open source licenses generally state that the software is provided without warranty. Responsibility for installing updates lies with the company that uses it, or with the party appointed through a support contract.

Sources

Other support services, including subscription IT support and dedicated teams, are on the IT Support & Consulting page.

Category IT Support & Consulting

Keep reading

Related articles

All Articles