Every change to information systems and processing facilities is to pass through the change management procedures. Purpose: keep information secure while changes are carried out. Guidance: introducing new systems or making major changes follows agreed rules and a formal path that documents, specifies, tests and quality-checks the change and manages its roll-out, with management responsibilities and procedures giving adequate control over every change. Change control procedures are documented and enforced so information stays confidential, intact and available from the first design work through every later round of maintenance, and procedures for ICT infrastructure and software are integrated wherever practical. They should cover planning and assessing the impact of changes, taking all dependencies into account; authorizing changes; informing relevant interested parties; testing changes and accepting the test results (8.29); implementing changes with deployment plans; emergency and contingency arrangements including fallback; keeping records of changes covering all of these; updating operating documentation (5.37) and user procedures as needed; and revising ICT continuity plans and the associated response and recovery steps (5.30) where required. Other information: poorly controlled change is a frequent cause of system and security failures, and moving software from development into operation can affect application integrity and availability; software changes affect production and the reverse; good practice is to test ICT components, including patches, service packs and other updates, in an environment separate from both production and development (8.31); production includes operating systems, databases and middleware, and the control covers application and infrastructure changes alike.
This control maps to 157 controls across 50 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of ISO 27002:2022 have you already done?
ISO 27002:2022 8.32 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.