Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Respect intellectual property – especially software licences – and protect your own IP.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Teams should control intellectual property risks without confusing legal ownership with everyday access rights. Useful practice distinguishes inbound licence obligations, outbound protection of proprietary material, and employment or contractor terms, then ties them to procurement, onboarding, software installation, and exit activities so breaches can be detected before they become contractual or legal disputes.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Software inventories do not match licence entitlements, so installations may exceed purchased use rights or miss required attribution and notice conditions.
Employment or contractor agreements omit IP and confidentiality clauses, leaving ownership of code, documents, or designs unclear after termination or project handover.
Protected source materials are shared through uncontrolled channels, so teams cannot show who approved disclosure or whether third-party rights were respected.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Maintain a licence and IP inventory alongside the legal register, listing product name, licence metric, seat count, renewal date, redistribution limits, and evidence of purchase. Assign procurement or IT asset management ownership, with legal review for non-standard terms, open-source exceptions, and any use that affects customer deliverables or internal development.
Embed IP checks into onboarding, procurement, and installation workflows. Before software is deployed, verify entitlement and approved use; before contractors start, confirm agreement language covering ownership, reuse, and disclosure; before files leave the organisation, confirm classification, recipient need, and any third-party restrictions.
Define a simple review cadence for installed software, cloud subscriptions, and reuse of external content. Compare discovered assets against approvals, flags, and invoices; when mismatches appear, record whether removal, purchase, relicensing, or permission was obtained, and keep the decision trail for follow-up and legal review.
Protect the organisation’s own IP through access restriction, marked repositories, and exit checks. Use role-based access to design files and source repositories, require return of materials on termination, and retain evidence such as signed clauses, exception approvals, software reconciliation reports, and withdrawal records for former users.
What an auditor will ask to see
Software entitlement reconciliation showing installations, licences held, discrepancies, and remediation.
Signed employment or contractor agreement with IP assignment and confidentiality language.
Repository access review or export approval showing restricted sharing of protected material.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.32. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.