In secured IP deals, the scope is defined by the contract itself. Derivative works—like adaptations or improvements—aren’t automatically covered by securing the base works. The security agreement must name derivatives to grant a secured interest, with the rest of the rights remaining outside the collateral.

Multiple Choice

In C Tek Software, Inc. v. New York State Business Venture Partnership, what must a security agreement expressly include for derivative works to be covered?

In secured IP transactions, the scope of what the security agreement covers must be defined in the contract itself. Derivative works are not automatically included simply because the base copyrighted works are secured. The debtor’s rights in derivative works—such as adaptations, improvements, or new versions—are considered separate rights that can be created or licensed independently, so the security interest does not reach them unless the agreement explicitly names them. That’s why the best answer is that derivative works must be expressly included in the security agreement to be covered. If the agreement only references the base works, derivative rights remain outside the secured collateral. The other options misstate how protection is extended: coverage isn’t automatic through the base works alone, nor is it guaranteed by copyright law regardless of contract, and a separate license is not what creates a secured interest in derivatives.

When the contract is king: securing IP, derivatives, and the fine print

Imagine you’re lending someone money but insisting on a tight guarantee: the collateral isn’t just the thing you can see, but every possible twist of it that could come from the thing you’re financing. In the world of intellectual property, that “twist” is a derivative work—an adaptation, improvement, or new version built on top of a base work. In secured IP transactions, the reach of a security interest isn’t automatic. It’s defined, moment by moment, by what the contract actually says. And that’s where the C Tek Software, Inc. v. New York State Business Venture Partnership case gives us a crisp, practical reminder: derivative works must be expressly included in the security agreement to be covered.

A quick map of the terrain: base works, derivative works, and the security net

Think of a software company that licenses a core program. The base copyright protects the original software as written, the user interface, the code, the assets—the whole package. If a lender takes a security interest in that software, there’s a natural question: does that security interest extend to anything built on top of it? What about updates, forks, compatible plugins, or localized adaptations? The legal answer isn’t a blanket default. It hinges on the terms of the security agreement.

In many secured IP arrangements, the contract is the landscape’s boundaries. It tells us what assets are included, what “collateral” means, and how far the lender’s rights reach. Without explicit language, derivative works aren’t automatically swept in just because the base works are covered. Why not? Because derivative rights—think adaptations, improvements, or new versions—are themselves distinct rights. They can be created, licensed, or assigned separately. If the agreement doesn’t name them, they sit outside the secured collateral, like a room you forgot to lock.

Let’s parse that idea with a practical lens. A base copyright gives its holder exclusive rights to reproduce, distribute, display, perform, and prepare derivative works in a general sense. But if a lender wants those derivative rights as part of the collateral, the security agreement has to say so. Otherwise, the debtor keeps control over derivatives, even if the base work sits under a secured claim.

Derivatives aren’t automatic; they’re optional, negotiable, and often fluid

Derivatives aren’t mere byproducts. They can be core to a business model—comprehensive software suites that evolve, mobile apps that extend a core platform, or enterprise tools that build on a foundation with new modules. Each derivative creates potentially new revenue streams, new licensing opportunities, and new value for both the borrower and the lender. That makes the decision to include them in a security agreement a high-stakes drafting exercise.

Here’s the practical takeaway: if you want the lender to have a security interest in derivative works, you must spell it out. The contract should name the derivative rights, define what constitutes a derivative, and specify the scope—whether it includes all future derivatives, specific categories (like adaptations or enhancements), or particular projects. Without that specificity, those derivative rights remain the debtor’s property, open to licensing or disposition outside the secured framework.

A short tour of the legal logic behind the express inclusion

Why is express inclusion required? Because IP rights, including derivatives, resemble a moving target. When a creator produces a derivative, they’re creating a new asset, often with its own value, market, and licensing dynamics. The security interest attached to the original base work doesn’t automatically travel along with every new asset derived from it. The risk for lenders is clear: if derivatives are treated as outside the secured collateral, they can be leveraged by the debtor in ways not anticipated by the lender.

On the flip side, the borrower isn’t inherently opposed to a broad grant. Many borrowers would prefer to minimize friction—let the secured interest extend to derivatives to reduce the need for future amendments. But that’s a policy decision that must be negotiated and documented. The sticking point is control: who owns, who licenses, and who profits from derivatives? If you want to keep those rights within the security net, you must write that down.

What the case teaches across industries

In technology start-ups, software publishers, game developers, and even some content platforms, the principle shows up in various guises. Lenders want predictability, risk management, and a clear path to recovery in the event of default. Borrowers want flexibility, especially in fast-moving markets where derivatives can become the lifeblood of product strategy.

  • Software as a service and platform ecosystems: A platform might depend on a core codebase, plus plugins, add-ons, and localization efforts. If a lender holds a security interest in the core platform but not in the derivatives, the platform could be vulnerable to a derivate-driven pivot that leaves the secured creditor with a diminished claim.

  • Media and publishing tech: Base works like core scripts or templates are valuable, but derivatives—updated editions, translations, or enhanced formats—can become the main revenue stream. An express derivative clause helps lock in the creditor’s stake across product line expansions.

  • Manufacturing software and tooling: When hardware or firmware relies on a proprietary algorithm, derivative versions may be essential for future interoperability and upgrades. A security agreement that names these derivatives ensures the creditor isn’t left in the dark as products evolve.

Drafting tips: how to thread the needle

If you’re drafting or negotiating a security agreement in a tech-forward IP transaction, here are a few practical pointers to keep your contract airtight without suffocating flexibility:

  • Define derivatives clearly. Specify what constitutes a derivative (e.g., adaptations, improvements, translations, adaptations, new versions) and identify which derivative rights are included in the collateral.

  • Include future derivatives. Consider language that captures derivatives created in the future, so the security interest isn’t stranded as the product evolves.

  • Align licenses and assignments. If derivatives require separate licenses or assignments, spell out how those relate to the security interest. You want a coherent, integrated framework, not a tangle of separate agreements.

  • Clarify ownership and enforcement. State who holds the derivative rights, who can grant licenses, and how enforcement would work if the loan default triggers a creditor’s remedies.

  • Use schedules and defined terms. Attach schedules listing anticipated derivative families or product lines, and define terms like “improvements,” “modifications,” and “derivative works” to reduce ambiguity.

  • Balance flexibility with risk. It’s smart to draw a line around what derivatives are included now and what will be covered later, so both sides know where they stand as the product road map expands.

A note on licensing, collateral, and practical realities

One common concern in secured IP deals is licensing complexity. Even when derivatives are included in the security agreement, operational realities matter. A lender isn’t trying to micromanage every minor update; they want assurance that the core value remains attachable to the collateral. From a borrower’s standpoint, this often means coordinating with licensing teams, product managers, and corporate attorneys to ensure derivative licensing doesn’t accidentally sever the link between the secured asset and its value.

Think of it as a dance: the security interest provides a safety net, but the derivative rights can fuel growth if managed well. The better the contract articulates the rights and responsibilities on both sides, the smoother the relationship—especially when a company pivots, expands, or refactors its offerings.

Real-world sensibilities: what this means for teams on the ground

For in-house counsel, negotiating teams, and dealmakers, the emphasis is on clarity. You don’t want to end up in the thicket of a dispute about whether a certain derivative falls inside or outside the collateral. The simplest way to avoid that is to anticipate what derivatives your product line will produce over time and spell it out in the security agreement.

For developers and product leaders, this isn’t just legal boilerplate. It’s a framework that can influence architecture decisions. If derivatives are covered, you might be freer to iterate rapidly, knowing the secured creditor has a stake in your evolving portfolio. If derivatives aren’t covered, you may need to plan separate licensing strategies or negotiate amendments as your product strategy evolves.

A nuanced caveat: language matters more than vibes

There’s a difference between “derivative works” and “derivative rights.” The former refers to the created objects themselves; the latter speaks to the legal authority to create, distribute, or license those objects. In secured transactions, it’s the derivative rights that a security agreement must reach if you want broader protection. Vague language invites gaps, and gaps invite risk. So the drafting work isn’t just pedantic; it’s practical insurance against future disagreements or misaligned expectations.

The broader takeaway: protection through precise scaffolding

At its core, the lesson from this line of IP finance is straightforward: cover what you intend to cover. If you want derivatives to ride along with the base works in a secured transaction, you’ve got to name them explicitly in the security agreement. It’s not a given, not automatic, and not something the law will supply by default. The contract is the map; the derivations are the terrain. If you want a sure path, chart it in the document and keep revisiting it as products, markets, and partnerships evolve.

The art of negotiating balanced, future-ready security agreements

In the end, it’s about balancing risk with opportunity. Your contract should feel firm yet flexible—firm enough to protect the lender’s interest, flexible enough to accommodate growth without constant renegotiation. Derivative works aren’t decorative extras in the IP world; they’re often the engines of expansion. By naming them—and by defining how they’re created, licensed, and integrated into the collateral—you give both sides a clear, practical framework to move forward with confidence.

If you’re curious about how these concepts play out in real deals, you’ll notice the theme across industries: the security line is drawn where the agreement says it is. Derivatives stay in or stay out based on explicit stipulations, not instinct or hope. And that distinction changes everything—from how a company plans its platform roadmap to how a lender measures risk and opportunity.

A closing thought: the value of precise contracts isn’t just legal risk management; it’s strategic clarity

When teams lock down derivative inclusion in the security agreement, they aren’t merely ticking a compliance box. They’re creating a shared understanding of value, ownership, and potential. That clarity can smooth negotiations, accelerate product development, and foster healthier business relationships with lenders who want to see a clear, sustainable plan for protecting the assets that power growth.

So next time you’re reviewing or drafting a secured IP arrangement, bring the derivatives into the room with a crisp, explicit description. Let the contract do the heavy lifting—defining what’s covered, who can do what with it, and how future derivatives fit into the security net. It’s not just legal precision; it’s practical strategy in motion. And that kind of foresight often makes all the difference when a company scales up, pivots its product line, or forges a new partnership in a fast-moving tech landscape.