ISO 27001 Control A.5.32: Intellectual Property Rights

· 7 min read · Lyudmil Arkov

Intellectual property rarely appears in a security conversation until something goes wrong: a software vendor asks for a license audit, a customer discovers that a contractor copied code from another project, or a departing employee walks away with a product design. A.5.32 brings the topic into the management system. It is the 32nd of 37 organizational controls in our walk through Annex A, and it works in both directions - respecting other people’s rights and protecting your own.

For many organizations the practical core is simple and unglamorous: knowing what software you use, making sure you are entitled to use it, and being careful with content and code that belongs to someone else. The rest is about making sure your own valuable material stays yours.

What the control requires

Annex A control 5.32 of ISO 27001:2022 states that the organization shall implement appropriate procedures to protect intellectual property rights.

The key elements:

  • Appropriate procedures - proportionate, written ways of working rather than a general intention to behave
  • Protect - avoid infringing the rights of others and defend your own
  • Intellectual property rights - copyright, software licenses, design rights, trademarks, patents and source code licenses, among others

A.5.32 is a preventive control in the attributes of ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including publishing a policy on legal and compliant use of software and information products, acquiring software only through known and reputable sources, maintaining an asset register, keeping proof of ownership of licenses, and ensuring that license limits such as the maximum number of users are not exceeded. Rules on intellectual property differ between countries and we are not giving legal advice here. If a specific situation matters, such as ownership of code written by a contractor, take advice from a qualified lawyer.

How to implement intellectual property protection

Know what you use and what you are entitled to

Start with an inventory of software, subscriptions, fonts, stock images, data sets, libraries and any other third-party content your teams use. Link it to your inventory of information and other associated assets so there is one place to look. For each item, record the license type, the number of users or devices allowed, the renewal date, the owner and where the proof of purchase is stored.

Then compare reality with entitlement. Count installed copies and active users and see whether they match what you hold. Over-use is the classic finding, often caused by a team that grew faster than the license count, or a trial that quietly turned into production use. Under-use costs money too, so the exercise is not only about risk.

Set clear rules for staff and teams

Write a short rule set that fits in your acceptable use of information and other associated assets policy. It should say that software and content may only be obtained through approved channels, that copying or installing unlicensed material is prohibited, and that people should check before using third-party material in client work. Cover the following situations explicitly:

  • Open source. Open source software still has licenses with conditions, some of which affect how you may distribute your own product. Keep a list of the components you ship and their licenses, and ask a lawyer if a copyleft license appears where you did not expect it.
  • Generated or sourced content. Images, text, code snippets and data from the web or from generative tools carry their own terms and uncertainties. Decide what is acceptable for client work and document it.
  • Client and partner material. Treat what customers give you as theirs. Do not reuse it for another client without permission.
  • Personal software. Staff should not install personal or pirated copies on company devices.

Make the rule easy to follow by providing legitimate tools through a simple request route. People turn to unapproved copies when the approved route is slow.

Protect your own intellectual property

Your own material has value too. Identify what makes your business distinctive: source code, designs, methodologies, client lists, training material, brand names. Then decide how each is protected. Practical measures include:

  • Ownership terms. Make sure employment and contractor agreements say who owns what is created for you. Check your terms and conditions of employment and contractor templates with legal advice.
  • Confidentiality. Use confidentiality or non-disclosure agreements when sharing valuable know-how, and mark sensitive material using your classification scheme.
  • Access restriction. Limit who can see and copy crown-jewel material, and log access. Source code in particular deserves tight control, a topic we return to in the technological controls on access to source code.
  • Trademarks and registrations. Decide whether names and logos should be registered, and track renewals. A lapsed registration is an expensive mistake.
  • Departures. Include IP in leaver checks, so that material is returned and access removed, in line with return of assets.

Cover suppliers and contracts

When suppliers or contractors create material for you, or handle yours, the contract must make ownership and permitted use clear. Likewise, check the terms of tools you rely on. Some platforms claim broad rights over content uploaded to them, and some licenses restrict commercial use or use by contractors. Build these checks into your supplier onboarding, as described in information security in supplier relationships and addressing information security within supplier agreements. Add the relevant obligations to your register of legal and contractual obligations under legal, statutory, regulatory and contractual requirements.

Finally, keep the evidence simple and findable. A single spreadsheet or asset tool entry per license, with the invoice or order confirmation attached, answers most questions in seconds. Review it when renewals come due and when teams change, since both are moments when entitlements drift. Assign one person to own the register, even in a small company, and make sure that person is told when a new tool is bought. Procurement, finance and team leads all see purchases that the security team does not, so a short note to the register owner for every new subscription is a cheap and effective habit. If you build software, add the same discipline for the components you ship: a list of dependencies and their licenses, refreshed when you release, makes customer due diligence questions much easier to answer.

A.5.31 connection. Legal, statutory, regulatory and contractual requirements is where IP obligations are first identified and recorded.

A.5.9 connection. The inventory of information and other associated assets is the natural home for the software and content register.

A.5.10 connection. Acceptable use of information and other associated assets states the rules staff follow.

A.6.2 and A.6.6 connection. Terms and conditions of employment and confidentiality or non-disclosure agreements protect your own rights and those of your clients.

Clause 7.5.3 connection. Control of documented information helps protect ISMS documents and their versions.

Forward reference. Installation of software on operational systems (A.8.19) and access to source code (A.8.4) in the technological section provide technical controls that support IP compliance. We cover them later in the series.

What auditors check

A policy or rule. Auditors look for a documented position on legal use of software and information products.

A software and license register. They compare licenses held with software installed, sometimes by sampling a few machines.

Approved sources. They ask how software is obtained and whether staff can install unauthorized applications.

Contract terms. For contractors and suppliers who create material, they look for ownership and confidentiality clauses.

Open source management. For software businesses, they ask how third-party components and their licenses are tracked.

Awareness. Interviews show whether staff know the rules and how to ask for software.

Common mistakes to avoid

No record of licenses. Without proof of entitlement, you cannot defend a vendor audit.

Trial software that stays. Evaluations quietly become permanent use with no payment or approval.

Ignoring open source obligations. Using a component without checking its license can create obligations or conflicts later.

Vague contractor terms. If a contract does not say who owns the work, you may have to negotiate after the fact.

Over-reliance on policy. A rule that bans unlicensed software achieves little when the approved tools are hard to get.

Forgetting the exit. Departing staff and ended contracts are when valuable material most often leaves unnoticed.

How 27kay can help

We help organizations build practical IP procedures that people actually follow, from a software and license register to clear contractor terms. As part of ISO 27001 implementation, we work with your legal advisers where needed and prepare the evidence an auditor will request. For the full picture, see our ISO 27001 knowledge hub.

If a software vendor asked for a license audit next month, would you know where you stand? Get in touch - we will help you find out calmly and fix what needs fixing.