Changes to information systems such as replacing a network device, creating a new database instance, or upgrading software are often necessary for improved performance, reduced costs, and higher efficiencies.
However, those changes to information processing facilities and systems, if not implemented properly, may lead to the compromise of information assets stored in or processed by these facilities.
Control 8.32 addresses how organisations can establish and apply change management procedures to monitor, review and control changes made to the information processing facilities and systems.
Control 8.32 enables organisations to maintain the security of information assets when executing changes on the information processing facilities and systems by establishing, implementing and managing change management rules and procedures.
Control 8.32 is preventive in nature. It requires organisations to define, document, specify, and enforce change control processes that govern the entire life cycle of information systems, from the initial design to the deployment and use.
| Control Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
|---|---|---|---|---|
| #Preventive | #Confidentiality #Integrity #Availability | #Protect | #Application Security #System and Network Security | #Protection |
Considering that compliance with Control 8.32 entails the establishment and enforcement of change control procedures that apply to all stages in the life cycle of information systems, chief information security officers, with the support of domain experts, should be responsible to design and enforce these procedures.
All major changes to information systems and the introduction of new systems should be subject to an agreed set of rules and procedures. These changes should be formally specified and documented. Furthermore, they should go through the testing and quality control processes.
To ensure that all changes comply with the change control rules and standards, organisations should assign management responsibilities to appropriate management and should set out the necessary procedures.
Control 8.32 lists nine elements that should be included in the change management procedure:
Lastly, it is noted that organisations should integrate change control procedures for software and ICT infrastructure to the maximum extent possible.
Changes to the production environments such as operating systems, and databases may compromise the integrity and availability of applications, particularly the transfer of software from development to production environment.
Another risk that organisations should be cautious against is changing software in the production environment may have unintended consequences.
To prevent these risks, organisations should perform tests on ICT components in an environment isolated from the development and production environments.
This will enable organisations to have greater control over new software and will provide an extra layer of protection for real-world data used for testing purposes. This extra protection can be achieved via patches and service packs.
27002:2022/8.32 replaces 27002:2013/(12.1.2, 14.2.2, 14.2.3, 14.2.4)
Overall, the 2013 version was more prescriptive compared to the 2022 version in terms of the requirements for change control procedures.
There are three key differences to be highlighted between the two versions.
Both the 27002:2022 and 27002:2013 version lists what a ‘change procedure’ should include in a non-exhaustive manner.
However, the 2013 version contained the following elements that were not referred to in the 2022 version:
Control 14.2.3 in version 27002:2013 dealt with how organisations can minimise the adverse effects on and disruptions to the business operations when changes are made to operating systems.
The 27002:2022 version, in contrast, does not include requirements for such changes.
Control 14.2.4 in 27002:2013 version addressed ‘Changes to Software Packages’. On the contrary, the 27002:2022 version does not contain requirements for such changes.
Our cloud-based platform provides you with a robust framework of information security controls so that you can checklist your ISMS process as you go to ensure that it meets the requirements for ISO 27000k.
Used properly, ISMS. online can assist you in achieving certification with the bare minimum of time and resources.
Get in touch today to book a demo.
| 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 |
