Software Licensing Concepts for CompTIA Tech+ (FC0-U71): Open Source vs. Proprietary, EULAs, and Subscription Models

Software licensing rarely gets the attention that hardware or networking topics do, but CompTIA puts it squarely inside the Security domain of the Tech+ (FC0-U71) exam, which carries a hefty 19% weight — the second-largest domain on the test. Objective 6.1 expects candidates to explain basic software licensing concepts, including open source versus proprietary models, end user license agreements (EULAs), product keys, and the difference between a one-time purchase and a recurring subscription. These concepts come up constantly in real IT work too: every time you install an application, renegotiate a renewal, or onboard a new employee's laptop, a licensing decision is sitting underneath it.

This guide builds on the ideas introduced in our Security Fundamentals for CompTIA Tech+ article, which covers the CIA triad and AAA, and pairs naturally with our breakdown of Virtualization and Cloud Computing Fundamentals, since cloud services are almost always sold under subscription licensing.

Open Source vs. Proprietary Software

The first distinction Tech+ wants you to know is open source versus proprietary software.

• Open source software ships with publicly available source code that anyone can inspect, modify, and redistribute, usually under a license like the GNU General Public License (GPL), MIT License, or Apache License. Examples include Linux, LibreOffice, and the Apache web server. "Open source" does not automatically mean "free of restrictions" — many open source licenses still require attribution or require that derivative works remain open source (a concept called "copyleft").
• Proprietary (closed source) software keeps its source code private and restricts how the software can be copied, modified, or redistributed. Microsoft Windows, Adobe Photoshop, and most commercial business applications fall into this category. The vendor retains ownership and tightly controls distribution through licensing terms.

Neither model is inherently more secure or more reliable — the exam wants you to recognize the distinction and the licensing obligations that come with each, not to rank them.

End User License Agreements (EULAs)

A EULA is the contract between the software publisher and the person installing the software. It is almost always presented during installation as a scrollable block of text with an "I Agree" checkbox, and clicking through it constitutes a legally binding acceptance of its terms, whether or not the user actually reads it.

A typical EULA defines:

• How many devices or users the license covers
• Whether the software can be copied, modified, reverse-engineered, or resold
• Limitations of liability if the software causes damage or data loss
• Terms for license termination, such as violating usage restrictions

For the exam, remember that a EULA governs usage rights, not ownership — when you buy software, in almost every case you are buying a license to use it under specific conditions, not the software itself.

Product Keys and Activation

A product key (sometimes called a license key or serial number) is a unique alphanumeric code used to prove that a copy of software was legitimately purchased. During or after installation, the software "phones home" to an activation server to validate the key, which helps publishers prevent casual piracy and track how many active installations exist under a given license.

Product keys tie directly into our earlier discussion of Operating Systems Fundamentals for CompTIA Tech+, since Windows activation is one of the most familiar real-world examples: an unactivated copy of Windows will nag the user and may restrict personalization features until a valid key is entered.

Licensing Models: Perpetual, Subscription, Volume, and Concurrent

Beyond open source versus proprietary, Tech+ candidates need to recognize how licenses are packaged and sold:

• Perpetual license — a one-time purchase that grants indefinite use of a specific software version. Upgrades to newer versions typically cost extra.
• Subscription license — a recurring fee (monthly or annually) that grants continued access to the software, and usually includes updates and new features automatically. Microsoft 365 and Adobe Creative Cloud are classic examples. Stop paying, and access typically ends.
• Volume license — a bulk agreement that lets an organization deploy the same software across many devices under a single negotiated contract, instead of buying individual retail copies.
• Concurrent license — allows a fixed number of simultaneous users to run the software at any one time, regardless of how many total employees could potentially use it. If a company owns 10 concurrent licenses for a design tool, the 11th person who tries to open it gets denied until a seat frees up.
• Single-use license — tied to one specific device or one specific user, and not legally transferable to another machine without the publisher's permission.

This is also where software licensing overlaps with the delivery models covered in our guide to Software as a Service (SaaS): SaaS products are almost always sold as subscriptions rather than perpetual licenses, which shifts both the cost structure and the compliance responsibility toward the vendor.

Why This Sits in the Security Domain

It might seem odd that licensing lives under Tech+'s Security objectives rather than under Applications and Software, but there's a practical reason: unlicensed or mismanaged software is a genuine security and compliance risk. Pirated software frequently ships with bundled malware, counterfeit product keys can disable critical security updates, and organizations that fail to track their license counts can face legal liability during a software audit. Keeping an accurate software inventory is part of the same hygiene discussed in our Software Development Concepts for CompTIA Tech+ article, where documentation and organized processes reduce risk across the board.

Browser-delivered software adds its own licensing wrinkle too — free browser add-ons and extensions, which we cover in Web Browser Features for CompTIA Tech+, are often licensed under permissive open source terms specifically because low-friction distribution benefits the publisher more than per-install revenue would.

Exam Tips for FC0-U71

• Expect scenario questions that describe a situation ("a company needs 50 employees to share 10 simultaneous seats of a design app") and ask you to name the licensing model (concurrent).
• Know that clicking "I Agree" on an installer is accepting a EULA, even if the question never uses the word "contract."
• Don't confuse open source with "no license required" — open source software still carries a license (GPL, MIT, Apache, etc.) with its own obligations.
• Subscription licensing is the default assumption for cloud and SaaS products; perpetual licensing is more associated with traditional, installed desktop software.

Key Takeaways

• Open source licenses allow inspection and modification of source code; proprietary licenses keep it closed and tightly controlled.
• A EULA is the binding agreement a user accepts during installation, governing usage rights rather than ownership.
• Product keys validate legitimate purchases and tie an installation back to a specific license.
• Common licensing models include perpetual, subscription, volume, concurrent, and single-use — each distributes cost and access differently.
• Software licensing sits in Tech+'s Security domain because unlicensed or poorly tracked software is a real compliance and security risk, not just a legal technicality.