Corporate Legal Services

Emergency Security Patches: Is Additional Copyright Registration Needed?

Software is registered, then an emergency security patch ships overnight — and the FDI company’s engineers ask legal: must we file a supplementary registration for this patch, and is the patch protected if we do not? The answer sits in copyright’s most basic principle: registration does not create the right.

Why a patch needs no supplementary registration to be protected

  • Automatic protection — Article 6 of the IP Law: copyright in a computer program (Article 22) arises when the program is created and fixed, regardless of registration or publication.
  • Registration is evidence only — Article 49: a copyright registration certificate records information about the registered work; skipping supplementary registration does not strip rights in the patch’s new code.
  • What a patch is as a work — a purely technical bug fix may create no new work; a patch adding creative features or modules makes that new part additionally protected, owned under Article 39 when written by staff within their duties.
  • No statutory re-registration cycle — Vietnamese law sets no deadline to re-register when software releases a new version; registering major versions is an evidence strategy, not an obligation.

Managing registration across a real software lifecycle

  1. Register (or refresh the evidence file) for major versions with significant creative change — the main commercial releases — rather than for every small patch.
  2. Archive source code by version with changelogs and contributor records: in a dispute, this is effective evidence in place of registration.
  3. For outsourced development, ensure the assignment clause covers patches and upgrades the vendor creates during the support term.

An emergency security patch needs speed, not registration paperwork. What an FDI software company needs is evidence discipline: register major versions, archive versioned source code, and make development contracts cover every update — then rights in each new line of code stay traceable without delaying a single patch by an hour.

Frequently asked questions

Our software is registered — must a security patch be registered again?

No. Copyright arises automatically under Article 6 of the IP Law; registration under Article 49 is evidence, not a condition of protection.

How often must registration be updated?

The law sets no cycle; sound practice is registering major versions with significant creative change, while minor patches need only archived source code and changelogs.

What happens if we never file supplementary registrations?

Rights in new code are not lost; the only cost is harder proof in a dispute, which versioned source archives can offset.

This article has been quality-reviewed by the FLAW AI Legal Council