Policy Register

Change management procedure

How changes to systems are requested, assessed, approved, tested, deployed and rolled back, and who may approve an emergency change.

How the register reads it

Also calledchange control, release management
FamilyOperations and technology
Document typeProcedure. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted.
Expected ownerThe head of IT operations.
Review cadenceAnnual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period).
On the gap list whenISO 27001 is ticked and no line resolves to it (DORA requires it too, inside a parent document, so it does not list it separately).
TemplateChange management policy.

Which standards require it, and what each expects it to contain

2 requiring clauses, 2 regimes

Shown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.

ISO/IEC 27001:2022

ISO 27001 8.32 Change management

Put changes to facilities and systems through change management procedures.

What the ISO 27002 guidance expects the document to say: Requires change management procedures to govern changes made to information systems and to the facilities that process information. Older source material adds that changes should be controlled by formal, documented and enforced procedures, with risk assessed as part of the process.

Evidence an auditor accepts: The change management procedure covering the types of change, the authorisation required and the route for emergency change; change records for the period, showing risk and security impact assessment, testing evidence, approval and implementation record; evidence of segregation between the person requesting, approving and implementing a change
Common gap: missing formal approval
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022

DORA (Regulation (EU) 2022/2554)

DORA Art. 9 Protection and prevention

Financial entities keep the security and operation of ICT systems and tools under continuous monitoring and control and limit ICT risk with security policies, procedures, protocols and tooling designed to keep ICT systems (above all those supporting critical or important functions) resilient and available, and protect data at rest, in use and in transit. The chosen solutions must be appropriate under Article 4 and cover secure data transfer, data loss and corruption, unauthorised access and data management risk. Within the ICT risk management framework they keep an information security policy (covering customer data where applicable), a risk-based network and infrastructure management structure that can cut or segment connections at once, least-privilege access controls, strong authentication and cryptographic key protection, a risk-based ICT change management process approved by management, and documented patch and update policies. Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Evidence an auditor accepts: Information security policy, including its scope for customer data where the entity holds such data; network architecture and segmentation records showing connections can be severed or isolated quickly; access rights reviews, authentication standards and cryptographic key management procedures
Common gap: Network cannot be segmented quickly to contain an attack
Source: DORA (Regulation (EU) 2022/2554)

Customizable template

8 sections, 2 cited to requiring clauses

With every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.

  1. Purpose
  2. Scope
  3. Roles and responsibilities
  4. Change management ISO 27001 A.8.32
  5. Protection and prevention DORA Art. 9
  6. Exceptions
  7. Related documents
  8. Review and approval

Customise this template The template document on the compliance platform

Do this for every document on your list

Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.

Build a register

Certificate management policy · Cloud security policy