[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"framework:iso-27001\u002Fa-5-32":3},{"item":4,"lessons":16,"controls":18,"related":19},{"family":5,"item":6,"code":7,"title":8,"citations":9,"publisher":10,"summary_md":11,"official_text":12,"official_attribution":12,"official_url":13,"link_label":14,"note":12,"updated_at":15},"iso-27001","a-5-32","Annex A 5.32","Intellectual property rights",0,"International Organization for Standardization (ISO) and IEC","**What it asks for.** Implement suitable procedures to protect intellectual property rights, both the organisation's own and those of others whose material it uses.\n\n**In practice.** Software is acquired from legitimate sources, licences are recorded and usage is checked against entitlements through software asset management. Rules cover the use of open source components and their licence obligations, copyrighted documents, images and data sets, and staff are told what they may and may not copy. The organisation's own intellectual property is identified and protected through classification and contracts. Evidence includes licence records, reconciliation results, an open source policy and awareness material.\n\n**Common gaps.** Licence compliance is often tracked for big vendors only, while cloud subscriptions, open source licences and material used to train or prompt AI systems are overlooked. Reconciliations are rarely done until a vendor audit forces one.",null,"https:\u002F\u002Fwww.iso.org\u002Fstandard\u002F27001","See the standard at ISO","2026-10-18T15:18:43.664+00:00",{"total":9,"list":17},[],[],[]]