A.8 Technological controls

A.8.32 Change management

Not mandatory by default – decided in your SoA

What it means in plain language

Control changes to systems and facilities through a change management process.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Controlled change prevents unexpected service disruption, security regression, and unapproved alterations to systems and facilities. Effective change control links the procedure, the register, and operational roles so teams can show how routine, standard, and emergency changes are handled differently. In practice, the process is not only about approvals; it is about impact analysis, backout planning, post-implementation validation, and learning from failed changes.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Changes are implemented directly in production without a recorded assessment of impact, testing status, or approval from the appropriate authority.
  • Emergency changes are used as a shortcut, but the organization does not complete retrospective review, causing recurring risk and weak accountability.
  • The change register is incomplete, so release evidence, rollback steps, and verification results cannot be traced to the deployed system version.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Document a change model that distinguishes standard, normal, and emergency changes, with approval authority, minimum evidence, and timing expectations for each. The change manager should maintain the register, while system owners approve riskier changes affecting availability, security settings, or regulated data processing.
  • Require every change request to include business reason, affected services, security impact, test results, implementation window, rollback plan, and validation method. Use a practical ticket template so engineers cannot close a change without the fields completed. For infrastructure and code releases, reference the commit, build number, and deployment target.
  • For emergency changes, allow accelerated approval but require immediate logging, service-owner notification, and a retrospective review within a defined interval. Record the root cause, whether the change was successful, what monitoring detected, and any corrective actions that prevent repeat incidents. This supports improvement and corrective action under Clause 10.
  • Perform post-change verification for high-risk changes: service checks, control checks, and user acceptance where relevant. Keep evidence in the change register, monitoring dashboard screenshots, and incident links. Where changes affect security tooling or privileges, coordinate with A.8.2, A.8.9, and A.8.15 so the change record shows both operational and security review.

What an auditor will ask to see

  • A completed change ticket with risk assessment, approver, test evidence, implementation window, and rollback steps.
  • A change register entry showing status, deployment date, affected assets, and post-change verification outcome.
  • An emergency change record with retrospective review notes and actions assigned after implementation.
  • A release note or deployment log matching the approved change identifier to the production version.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.32. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.31 — Separation of development, test and production environments and A.8.29 — Security testing in development and acceptance. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.