Purpose of Control 5.32
Control 5.32 outlines the steps that organisations need to take to ensure that they remain compliant with intellectual property (IP) rights, including the use of proprietary software that is purchased, subscribed to or otherwise leased.
ISO defines intellectual property rights as belonging to one or more of the following categories:
- Software copyright
- Document copyright
- Design rights
- Trademark rights
- Patents
- Source code licences
“Legal, statutory, regulatory or contractual” agreements often place restrictions on how proprietary software is able to be used, including blanket restrictions on the copying, extraction or reverse-engineering of source code, among other measures.
For clarity, Control 5.32 does not deal with situations where the organisation is the IP holder, and instead focuses on their obligation towards third party intellectual property rights that are stated within a licence agreement, a data sharing agreement, or any other comparable legal mechanism.
It’s important to note that copyright and/or IP infringement often carries severe financial and legal consequences for any organisation that wilfully or unwittingly breaks the terms of an agreement. As such, Control 5.32 should be given adequate consideration, in order to avoid any unnecessary business disruption or information security events.
Attributes Table of Control 5.32
Control 5.32 is a preventive control that maintains risk by implementing procedures to ensure that the organisation remains compliant with any prevailing IP or copyright requirements, including mitigating the risk of the organisation’s own personnel failing to uphold their individual obligations.
| Control Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
|---|---|---|---|---|
| #Preventive | #Confidentiality | #Identify | #Legal and Compliance | #Governance and Ecosystem |
| #Integrity | ||||
| #Availability |
ISO 27001 made easy
An 81% Headstart from day one
We’ve done the hard work for you, giving you an 81% Headstart from the moment you log on. All you have to do is fill in the blanks.
General Guidance on Control 5.32
Control 5.32 asks organisations to consider the following guidelines, in order to safeguard any data, software or assets that could be deemed IP:
- Implementing a “topic-specific” policy on the protection of IP rights, on a case-by-case basis, in line with their unique operational requirements.
- Publishing and communicating clear procedures that categorically define how software and ICT products should be operated, to remain compliant with IP standards.
- Using respected and reputable sources to acquire software, in order to avoid any inadvertent copyright breaches at source.
- Using an organisational asset register to pinpoint any ICT assets that carry IP requirements as standard.
- Ensuring that the organisation is able to produce proof of ownership at any given time, including physical and electronic licensing documents, communications and files.
- Remaining compliant with agreed software usage limits, including concurrent users, virtual resources etc.
- Plan and implement periodic reviews to ensure that the organisation’s ICT estate doesn’t contain any unauthorised or unlicensed software products.
- Create operational and financial procedures that ensure licences are kept up to date.
- Create procedures that cater for the safe, responsible and legally compliant transfer or disposal of software assets.
- Ensure compliance with the terms and conditions, and fair use guidelines, of any software acquired from the public domain.
- If the organisation has cause to utilise any commercial recordings, no part of that recording may be extracted, copied or converted by any means that aren’t contained within the software’s terms and conditions (including licensing), or by any prevailing copyright laws.
- Respecting and adhering to the copyright laws or licensing terms of textual data, including standards, books, articles, reports etc.
Free yourself from a mountain of spreadsheets
Embed, expand and scale your compliance, without the mess. IO gives you the resilience and confidence to grow securely.
Changes and Differences from ISO 27002:2013
27002:2022-5.32 replaces 27002:2013-18.1.2 (Intellectual property rights).
27002:2022-5.31 contains broadly the same set of guidelines as its 2013 counterpart, with two minor additions:
- 27002:2022-5.31 contains advice on how to manage IP-related matters under the terms of a data sharing agreement.
- 27002:2013-18.1.2 contains no mention of the residual benefits to an organisation seeking to manage the behaviour of individual staff, towards IP agreements and software use.
New ISO 27002 Controls
| ISO/IEC 27002:2022 Control Identifier | ISO/IEC 27002:2013 Control Identifier | Control Name |
|---|---|---|
| 5.7 | NEW | Threat intelligence |
| 5.23 | NEW | Information security for use of cloud services |
| 5.30 | NEW | ICT readiness for business continuity |
| 7.4 | NEW | Physical security monitoring |
| 8.9 | NEW | Configuration management |
| 8.10 | NEW | Information deletion |
| 8.11 | NEW | Data masking |
| 8.12 | NEW | Data leakage prevention |
| 8.16 | NEW | Monitoring activities |
| 8.23 | NEW | Web filtering |
| 8.28 | NEW | Secure coding |
| ISO/IEC 27002:2022 Control Identifier | ISO/IEC 27002:2013 Control Identifier | Control Name |
|---|---|---|
| 6.1 | 07.1.1 | Screening |
| 6.2 | 07.1.2 | Terms and conditions of employment |
| 6.3 | 07.2.2 | Information security awareness, education and training |
| 6.4 | 07.2.3 | Disciplinary process |
| 6.5 | 07.3.1 | Responsibilities after termination or change of employment |
| 6.6 | 13.2.4 | Confidentiality or non-disclosure agreements |
| 6.7 | 06.2.2 | Remote working |
| 6.8 | 16.1.2, 16.1.3 | Information security event reporting |
| ISO/IEC 27002:2022 Control Identifier | ISO/IEC 27002:2013 Control Identifier | Control Name |
|---|---|---|
| 7.1 | 11.1.1 | Physical security perimeters |
| 7.2 | 11.1.2, 11.1.6 | Physical entry |
| 7.3 | 11.1.3 | Securing offices, rooms and facilities |
| 7.4 | NEW | Physical security monitoring |
| 7.5 | 11.1.4 | Protecting against physical and environmental threats |
| 7.6 | 11.1.5 | Working in secure areas |
| 7.7 | 11.2.9 | Clear desk and clear screen |
| 7.8 | 11.2.1 | Equipment siting and protection |
| 7.9 | 11.2.6 | Security of assets off-premises |
| 7.10 | 08.3.1, 08.3.2, 08.3.3, 11.2.5 | Storage media |
| 7.11 | 11.2.2 | Supporting utilities |
| 7.12 | 11.2.3 | Cabling security |
| 7.13 | 11.2.4 | Equipment maintenance |
| 7.14 | 11.2.7 | Secure disposal or re-use of equipment |
How ISMS.online Helps
ISMS.online streamlines the ISO 27002 implementation process by providing a sophisticated cloud-based framework for documenting information security management system procedures and checklists to assure compliance with recognised standards.
Get in touch today to book a demo.
